From: Eli Zaretskii <eliz@gnu.org>
To: Joseph Mingrone <jrm@ftfl.ca>
Cc: 19653@debbugs.gnu.org
Subject: bug#19653: ispell misalignment with hunspell when Unicode apostrophe is used
Date: Fri, 21 Oct 2016 17:52:09 +0300 [thread overview]
Message-ID: <838tthsqjq.fsf@gnu.org> (raw)
In-Reply-To: <86shrpzwky.fsf@phe.ftfl.ca> (message from Joseph Mingrone on Fri, 21 Oct 2016 09:59:57 -0300)
> From: Joseph Mingrone <jrm@ftfl.ca>
> Cc: 19653@debbugs.gnu.org
> Date: Fri, 21 Oct 2016 09:59:57 -0300
>
> > @(#) International Ispell Version 3.2.06 (but really Hunspell 1.3.2)
> > & alsdk 3 0: Alaska, elastic, Alston
> > & sdfkjdsf 2 8: artefact's, postfix
> > & sldksdfkjsfd 2 17: justification, staphylococcus
>
> > The second number after each misspelled word is the offset of that
> > word's beginning, measured in characters, from the start of the line.
> > Hunspell used to report this in bytes instead of characters; if it
> > still does, you will have to patch it to fix that bug. AFAIR, the
> > Hunspell issue tracker includes several patches for this bug. Or
> > maybe the latest Hunspell 1.4.1 already fixes this, in which case
> > please upgrade.
>
> It's still a problem with hunspell.
>
> % echo "é startingCharTwo" | hunspell -a -d en_CA -i UTF-8
> @(#) International Ispell Version 3.2.06 (but really Hunspell 1.3.3)
> & é 15 0: e, s, i, a, n, r, t, o, l, c, d, u, g, m, p
> & startingCharTwo 1 3: nonparticipating
>
> https://github.com/hunspell/hunspell/issues/418
Thanks for checking.
next prev parent reply other threads:[~2016-10-21 14:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8660om1en7.fsf@phe.ftfl.ca>
2016-10-21 5:04 ` bug#19653: ispell misalignment with hunspell when Unicode apostrophe is used Joseph Mingrone
2016-10-21 7:33 ` Eli Zaretskii
2016-10-21 12:59 ` Joseph Mingrone
2016-10-21 14:52 ` Eli Zaretskii [this message]
2015-01-22 14:40 Tobias Getzner
2015-01-22 17:41 ` Eli Zaretskii
2015-12-26 16:53 ` Lars Ingebrigtsen
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838tthsqjq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19653@debbugs.gnu.org \
--cc=jrm@ftfl.ca \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).