GNU bug report logs - #19653
ispell misalignment with hunspell when Unicode apostrophe is used

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Joseph Mingrone <jrm <at> ftfl.ca>
Cc: 19653 <at> debbugs.gnu.org
Subject: bug#19653: ispell misalignment with hunspell when Unicode apostrophe is used
Date: Fri, 21 Oct 2016 17:52:09 +0300

> From: Joseph Mingrone <jrm <at> ftfl.ca>
> Cc: 19653 <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.