unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Jorge P. de Morais Neto" <jorge@disroot.org>
To: help-guix@gnu.org
Subject: Enchant from Guix misreports numerals on both Debian buster and bullseye
Date: Thu, 20 Aug 2020 15:06:39 -0300	[thread overview]
Message-ID: <87mu2pfaz4.fsf@disroot.org> (raw)

Hello.  I reported Emacs bug#42248 and I and the Emacs developers
realized at least part of the problem is with Guix version of Enchant.

On an updated Debian bullseye, enchant 2.2.8 from Guix misreports
numerals.  The same enchant version, when installed from APT, does not
have this problem.  Guix enchant 2.2.8 on Debian buster also misreports
numerals.  See (on Debian bullseye):

$ enchant-2 -v
@(#) International Ispell Version 3.1.20 (but really Enchant 2.2.8)
$ which enchant-2
/usr/bin/enchant-2
$ enchant-2 -l -d en_US /tmp/enchant-test.txt
Doesn
Amarelou

$ guix install enchant; hash enchant-2
[...]
$ enchant-2 -v
@(#) International Ispell Version 3.1.20 (but really Enchant 2.2.8)
$ which enchant-2
/home/jorge/.guix-profile/bin/enchant-2
$ enchant-2 -l -d en_US /tmp/enchant-test.txt
2015
Casa
42
Amarelou
2018

The file /tmp/enchant-test.txt:
--8<---------------cut here---------------start------------->8---
Doesn't 2015
Casa 42
Amarelou 2018
--8<---------------cut here---------------end--------------->8---

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.

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/>


                 reply	other threads:[~2020-08-20 18:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87mu2pfaz4.fsf@disroot.org \
    --to=jorge@disroot.org \
    --cc=help-guix@gnu.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).