From: Jorge P. de Morais Neto <jorge+list@disroot.org>
To: Julien Lepiller <julien@lepiller.eu>, help-guix@gnu.org
Subject: Re: Guix's enchant misreports numerals on Debian---both buster and bullseye
Date: Sat, 22 Aug 2020 17:31:57 -0300 [thread overview]
Message-ID: <878se62zia.fsf@disroot.org> (raw)
In-Reply-To: <BFC787C6-24D9-43F1-826E-DB8E90B564D6@lepiller.eu>
> Maybe you could use hunspell directly as your enchant? Not sure if
> that works, I'm not an emacs user.
Emacs does support several other spell checkers, but I want to use
enchant in order to share the user dictionary with other applications
that use enchant.
> With these, on Guix System, I was able to reproduce the behavior of
> debian's enchant. Numerals are not marked as incorrect anymore.
Yes, same here. Thank you!
> 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.
The command-line tool enchant-2 misreports "doesn't", but Gedit, which
very probably uses Enchant, correctly accepts "doesn't and four other
contractions I tested. It seems Gedit calls the enchant library in a
different way than Enchant's own command-line tool.
The reason to believe that Gedit uses Enchant are:
1. Wikipedia says so
2. Gedit's spell checker correctly accepts every word I have in the
Enchant user dictionary.
Best regards
--
- <https://jorgemorais.gitlab.io/justice-for-rms/>
- I am Brazilian. I hope my English is correct and I welcome feedback.
- <https://www.defectivebydesign.org/>
- <https://www.gnu.org/>
prev parent reply other threads:[~2020-08-22 20:32 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
2020-08-22 20:31 ` Jorge P. de Morais Neto [this message]
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=878se62zia.fsf@disroot.org \
--to=jorge+list@disroot.org \
--cc=help-guix@gnu.org \
--cc=julien@lepiller.eu \
/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).