So I've look at it quickly. It seems our enchant is built only with aspell, whereas debian is built with hunspell. In fact, our hunspell is able to detect the misspellings, and does not flag numbers nor doesn't. Maybe you could use hunspell directly as your enchant? Not sure if that works, I'm not an emacs user.
I've tried building enchant with hunspell, but although it worked, it still doesn't use the hunspell dictionnary. Looking at strace, it ignores $DICPATH which hunspell uses, and looks in various other directories. Sxmlinking one of them to $DICPATH didn't work either. Enchant was able to find hunspell's en_US.dic file, but then fails when looking for en_US.aff in the same directory. What is this aff file? On 2020年8月20日 14:45:56 GMT-04:00, "Jorge P. de Morais Neto" <jorge+l...@disroot.org> wrote: >Em [2020-08-20 qui 15:35:00-0300], Jorge P. de Morais Neto escreveu: > >> So enchant 2.2.8 (either from APT or from Guix) does not understand >> "doesn't"; and, what's worse, enchant-2.2.8 from Guix reports every >> numeral as a misspelling. > >I now reread my experiment and realized enchant from Guix does >understand "doesn't". So enchant 2.2.8 from Guix gets "doesn't" >correctly, but not numerals, and enchant 2.2.8 from APT gets numerals >correctly, but not "doesn't". Could enchant get both numerals and >"doesn't" correctly? That would be ideal. Failing that, APT's enchant >situation is much preferable than Guix's enchant. > >Regards > >-- >- <https://jorgemorais.gitlab.io/justice-for-rms/> >- If an email of mine arrives at your spam box, please notify me. >- Please adopt free/libre formats like PDF, ODF, Org, LaTeX, Opus, WebM >and 7z. >- Free/libre software for Replicant, LineageOS and Android: >https://f-droid.org >- [[https://www.gnu.org/philosophy/free-sw.html][What is free >software?]]