#35 big bug - does not recognize apostrophes

closed
None
5
2010-04-15
2010-04-14
No

Hunspell, as it comes, is marking the word *didn't* as a misspelling and suggesting a bunch of changes to it. The problem is pervasie and affects most words that contain an apostrophe ('). Here is the simplest way to reproduce it.

[hunspell-1.2.9]$ echo "didn't" | hunspell
Hunspell 1.2.9
& didn 8 0: did, din, dido, did n, Dido, Didi, Dion, Dian
*

Paulo Ney de Souza

Discussion

    • assigned_to: nobody --> nemethl
    • status: open --> closed
     
  • Use the newest version of the English dictionary (http://extensions.services.openoffice.org/en/project/dict-en-fixed) for the default apostrophe and typographical apostrophe support in command-line:

    $ hunspell -d en_US
    Hunspell 1.2.9
    didn't
    *

    didn’t
    *

    or modify the WORDCHARS line in the file en_US.aff:

    $ grep WORDCH en_US.aff
    WORDCHARS 0123456789'.-’

     
  • The dictionaries of the en-US-fixed extension contain the following input and output encoding to recognize and suggest typographical apostrophes, too:

    grep [IO]CONV en_US.aff
    ICONV 6
    ICONV ’ '
    ICONV ffi ffi
    ICONV ffl ffl
    ICONV ff ff
    ICONV fi fi
    ICONV fl fl
    OCONV 1
    OCONV ' ’