Comment 8 for bug 254223

Revision history for this message
Shehnaaz (asmals) wrote :

I am marking this as confirmed on jaunty, using en_ZA.UTF-8 locale, and shifting package to something more appropriate. I have the following dictionaries installed: myspell-en-au, myspell-en-za, myspell-en-gb, and aspell-en. Enchant, when running from the command-line, says:

mononoke@R2D2:~$ enchant -a
@(#) International Ispell Version 3.1.20 (but really Enchant 1.4.2)
error: duplicate REP tables used
Failure loading aff file /usr/share/myspell/dicts/en_ZA.aff

... but continues on to spell-check words anyway. I don't know whether this is normal or not.

Words which are extensions of a root word, such as "things", "cushioned", or "wanting", are detected as misspellings. "thing", "cushion", and "want" are accepted. 'enchant -a' detects all of these extensions as being misspellings:

mononoke@R2D2:~$ enchant -a
@(#) International Ispell Version 3.1.20 (but really Enchant 1.4.2)
error: duplicate REP tables used
Failure loading aff file /usr/share/myspell/dicts/en_ZA.aff
cushioned
& cushioned 4 0: cushion, fashioned, Cushitic, cautioned

... however, aspell does not:

mononoke@R2D2:~$ aspell -a
@(#) International Ispell Version 3.1.20 (but really Aspell 0.60.6)
cushioned
*

... but that makes sense, I suppose, since I also have this as the default:

mononoke@R2D2:~$ cat /usr/share/enchant/enchant.ordering
*:myspell,aspell,ispell

A second, possibly-related issue is that apostrophes found in words are, in *some* applications (such as OGMrip), detected as misspellings. In other applications, the same words are found to be correct. My working hypothesis is that UTF-8 curly-apostrophes and normal-keyboard-apostrophes are being interpreted differently, although there is very little perceptible difference to the user.