From: Stefan Kangas <stefan@marxist.se>
To: Reuben Thomas <rrt@sc3d.org>
Cc: 7781@debbugs.gnu.org
Subject: bug#7781: 23.2.91; ispell problem with hunspell and UTF-8 file
Date: Fri, 28 Aug 2020 05:00:11 -0700 [thread overview]
Message-ID: <CADwFkmmeeaRb0KBub+Af5BkgJX1BExX0BXwzc6GoYTjAZtWBww@mail.gmail.com> (raw)
In-Reply-To: <87sjx9fula.fsf@sc3d.org> (Reuben Thomas's message of "Mon, 03 Jan 2011 23:14:41 +0000")
Reuben Thomas <rrt@sc3d.org> writes:
> With the following text, and using emacs -Q, I get the errors you can
> see in the messages log below when using hunspell to spell-check a UTF-8
> buffer with some extended characters in it.
>
> I did test this with emacs -Q, but the current session, in which I
> reproduced the problem and am now composing this bug report, was not
> started with -Q (this is so submitting the bug report works properly!).
>
> I am running a freshly bzr-pulled build of the emacs-23 branch.
>
> Text follows
I tried this but couldn't reproduce the bug using current master and
Hunspell 1.7.0. Having read the bug report, IIUC, this was a bug in
Hunspell and not in Emacs?
Are you still able to reproduce this using a recent Emacs and Hunspell?
If I don't hear back from you within a couple of weeks, I'll just
close this bug as unreproducible.
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-08-28 12:00 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 23:14 bug#7781: 23.2.91; ispell problem with hunspell and UTF-8 file Reuben Thomas
2011-01-07 13:14 ` Agustin Martin
2011-01-07 14:30 ` Reuben Thomas
2011-02-11 17:00 ` Agustin Martin
2014-10-16 13:37 ` Agustin Martin
2014-10-16 13:54 ` Eli Zaretskii
2014-10-16 14:08 ` Agustin Martin
2012-01-01 21:42 ` bug#7781: ispell problem with hunspell and UTF-8 file (and other, related hunspell problems) Richard Wordingham
2013-04-13 19:12 ` bug#7781: [PATCH] Fix ispell problem with hunspell and UTF-8 file Николай Сущенко
2013-04-14 5:42 ` Eli Zaretskii
2013-04-14 6:33 ` Николай Сущенко
2013-04-14 7:08 ` Eli Zaretskii
2013-04-20 18:43 ` Николай Сущенко
2014-04-27 21:30 ` bug#7781: hunspell and latex-mode Peter Münster
2014-04-28 15:37 ` Eli Zaretskii
2014-04-28 16:18 ` Peter Münster
2014-04-28 16:48 ` Eli Zaretskii
2014-04-28 17:17 ` Peter Münster
2014-04-28 17:32 ` Eli Zaretskii
2014-04-28 18:27 ` Peter Münster
2014-04-29 10:03 ` Agustin Martin
2014-04-29 10:13 ` Peter Münster
2014-04-29 10:21 ` Agustin Martin
2014-04-29 10:20 ` Peter Münster
2014-04-29 10:39 ` Agustin Martin
2014-04-29 11:54 ` Peter Münster
2014-04-29 12:48 ` Peter Münster
2014-04-29 13:57 ` Eli Zaretskii
2014-04-29 14:30 ` Peter Münster
2014-04-29 15:25 ` Eli Zaretskii
2014-04-29 16:34 ` Peter Münster
2014-09-25 9:54 ` bug#7781: Bug still present in hunspell 1.3.3; Eli's patch still works Reuben Thomas
2020-08-28 12:00 ` Stefan Kangas [this message]
2020-08-28 12:36 ` bug#7781: 23.2.91; ispell problem with hunspell and UTF-8 file Eli Zaretskii
2020-08-28 12:56 ` Stefan Kangas
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=CADwFkmmeeaRb0KBub+Af5BkgJX1BExX0BXwzc6GoYTjAZtWBww@mail.gmail.com \
--to=stefan@marxist.se \
--cc=7781@debbugs.gnu.org \
--cc=rrt@sc3d.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.
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).