unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org,"Jorge P. de Morais Neto" <jorge+list@disroot.org>
Subject: Re: Guix's enchant misreports numerals on Debian---both buster and bullseye
Date: Thu, 20 Aug 2020 20:14:56 -0400	[thread overview]
Message-ID: <BFC787C6-24D9-43F1-826E-DB8E90B564D6@lepiller.eu> (raw)
In-Reply-To: <FEBD61F7-3D6A-4444-911E-1C629C10A170@lepiller.eu>

Hi,

I ended up pushing two patches: the first one installs the required .aff files along with the .dic files in hunspell-dict-en. The second adds hunspell as an input to enchant.

With these, on Guix System, I was able to reproduce the behavior of debian's enchant. Numerals are not marked as incorrect anymore.

I have two issues left: enchant ignores DICPATH and loads dictionaries from global directories, which is an issue on the Guix System (less so on foreign distros as they probably have dictionaries installed at these locations).

Hunspell itself doesn't flag "doesn" as incorrect, whereas enchant does, despite using the same dictionary. If this is also the case on Debian, we might have found a bug in enchant.

So: after you run guix pull and update enchant, you will see the same behavior from guix' and debian's enchant.

On 2020年8月20日 15:15:53 GMT-04:00, Julien Lepiller <julien@lepiller.eu> wrote:
>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+list@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?]]

  reply	other threads:[~2020-08-21  0:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-20 18:35 Guix's enchant misreports numerals on Debian---both buster and bullseye Jorge P. de Morais Neto
2020-08-20 18:45 ` Jorge P. de Morais Neto
2020-08-20 19:15   ` Julien Lepiller
2020-08-21  0:14     ` Julien Lepiller [this message]
2020-08-22 20:31       ` Jorge P. de Morais Neto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BFC787C6-24D9-43F1-826E-DB8E90B564D6@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=help-guix@gnu.org \
    --cc=jorge+list@disroot.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).