From: Juri Linkov <juri@jurta.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: 13109@debbugs.gnu.org
Subject: bug#13109: 24.1; flyspell highlights words containing curly quotes which ispell-buffer accepts
Date: Wed, 12 Dec 2012 01:07:22 +0200 [thread overview]
Message-ID: <87a9tkz1id.fsf@mail.jurta.org> (raw)
In-Reply-To: <CAOnWdoiXBh0b2N1_0qe0BhGWVxGcDnXG=0_jFrRMe_cVAoJ-zw@mail.gmail.com> (Reuben Thomas's message of "Tue, 11 Dec 2012 16:20:42 +0000")
>> `ispell-aspell-find-dictionary' reads the ispell data from
>> /usr/lib/aspell/en.dat that contains
>>
>> name en
>> charset iso8859-1
>> special ' -*-
>> soundslike en
>> affix en
>> #repl-table en_affix.dat
>
> Support for curly quotes in aspell appears to be partial and unreleased,
> but Debian currently packages an unreleased version with this support; see:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=533378
Thanks for the link. It refers to the diff at
http://launchpadlibrarian.net/82990151/aspell_0.60.6-6_0.60.7~20110707-1.diff.gz
that includes the following fix that implements the
support for curly quotes in aspell:
diff -Nru aspell-0.60.6/data/iso-8859-1.cmap aspell-0.60.7~20110707/data/iso-8859-1.cmap
@@ -892,6 +892,7 @@
2009 > 20 # compat
200A > 20 # compat
+2019 > 27 # compat
2024 > 2E # compat
2025 > 2E 2E # compat
This fix means that aspell developers added a mapping from
2019 (RIGHT SINGLE QUOTATION MARK) to 27 (APOSTROPHE)
in their character `compat' table. This explains why
`ispell-buffer' does work while `ispell-word' and `flyspell' don't.
`ispell-word' and `flyspell' still use the information from
/usr/lib/aspell/en.dat to parse the buffer to find the next word to check,
and fail because they don't use the `compat' mappings from iso-8859-1.cmap.
Applying a solution similar to the aspell fix above means that
`ispell-get-word' should consult a character equivalence table
(to be added in bug#13041 and bug#13131) and match curly quotes
as straight quotes while searching the next word to check.
next prev parent reply other threads:[~2012-12-11 23:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 23:59 bug#13109: 24.1; flyspell highlights words containing curly quotes which ispell-buffer accepts Reuben Thomas
2012-12-07 6:29 ` Eli Zaretskii
[not found] ` <CAOnWdoiiaW0gvHTEuunsZvkqn8a6A4tLsQC4WoF3jgy40onjMg@mail.gmail.com>
2012-12-07 13:57 ` Eli Zaretskii
2012-12-07 15:27 ` Reuben Thomas
2012-12-09 21:24 ` Reuben Thomas
2012-12-10 23:34 ` Juri Linkov
2012-12-11 16:20 ` Reuben Thomas
2012-12-11 23:07 ` Juri Linkov [this message]
2013-05-03 20:15 ` Reuben Thomas
2013-05-03 20:20 ` Reuben Thomas
2013-05-03 20:48 ` Reuben Thomas
[not found] ` <mailman.25084.1367614166.855.bug-gnu-emacs@gnu.org>
2013-05-04 19:26 ` Sebastien Vauban
2013-05-06 10:32 ` Agustin Martin
2015-06-26 11:46 ` bug#13109: Thanks Reuben Thomas
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=87a9tkz1id.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=13109@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).