From: Noam Postavsky <npostavs@gmail.com>
To: Agustin Martin <agustin.martin@hispalinux.es>
Cc: 12611@debbugs.gnu.org
Subject: bug#12611: Bugfix for broken hunspell choices
Date: Tue, 28 Aug 2018 19:00:44 -0400 [thread overview]
Message-ID: <875zzut7tv.fsf@gmail.com> (raw)
In-Reply-To: <20121011105321.GA23520@agmartin.aq.upm.es> (Agustin Martin's message of "Thu, 11 Oct 2012 12:53:21 +0200")
forwarded 12611 forwarded 12611 https://sourceforge.net/p/hunspell/bugs/211/
close 12611
quit
>> You mean "bugs". Yes, quite probably. The solution is to fix
>> Hunspell (I think I can give the OP patches, if he can build his own
>> Hunspell).
>
> Indeed. Browsing into hunspell bug tracker I noticed another report (with
> proposed change) that may be related to this problem,
>
> http://sourceforge.net/tracker/?func=detail&aid=3468022&group_id=143754&atid=756395
> No Encoding of Word for Suggestions in Piped Mode - ID: 3468022
It now redirects to https://sourceforge.net/p/hunspell/bugs/211/, the
maintainer says it's probably fixed in hunspell 1.3.4.
> A consequence of this bug seems that when communicated with in UTF-8, useful
> suggestions are not generated from an 8-bit dictionary.
>
> This in adition to report and changes proposed in
>
> http://sourceforge.net/tracker/?func=detail&aid=3178449&group_id=143754&atid=756395
> Bad UTF-8 char count in pipe mode - ID: 3178449
This one is marked fixed (https://sourceforge.net/p/hunspell/bugs/185/).
prev parent reply other threads:[~2018-08-28 23:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 12:32 bug#12611: Bugfix for broken hunspell choices Bastian Ballmann
2012-10-10 10:48 ` Agustin Martin
2012-10-10 15:57 ` Eli Zaretskii
2012-10-11 10:53 ` Agustin Martin
2018-08-28 23:00 ` Noam Postavsky [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://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=875zzut7tv.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=12611@debbugs.gnu.org \
--cc=agustin.martin@hispalinux.es \
/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).