From: Eli Zaretskii <eliz@gnu.org>
To: Leo Liu <sdl.web@gmail.com>
Cc: 17890@debbugs.gnu.org, agustin.martin@hispalinux.es
Subject: bug#17890: 24.4.50; flyspell highlights ``doesn't'' incorrect
Date: Tue, 01 Jul 2014 18:43:23 +0300 [thread overview]
Message-ID: <83ionh3x0k.fsf@gnu.org> (raw)
In-Reply-To: <m361jh19y2.fsf@gmail.com>
> From: Leo Liu <sdl.web@gmail.com>
> Date: Tue, 01 Jul 2014 21:32:21 +0800
> Cc: 17890@debbugs.gnu.org
>
> On 2014-07-01 15:03 +0200, Agustin Martin wrote:
> > There is a known problem with the typographically correct apostrophe
> > (“right single quotation mark” U+2019) (bug#17437). Does the problem
> > happen with the single quote or with that U+2019 apostrophe?
>
> They both give me the highlight. I am using emacs -Q and there is no
> settings for dictionary unless it is based on locale. Mine is
> en_GB.UTF-8.
>
> CentOS with /usr/bin/hunspell
> - 24.3.1 compiled on 2013-12-09 doesn't have this bug
> - 24.3.92 compiled on 2014-06-30 and 24.4.50 (2014-06-29) both have this
> bug.
I don't see this problem with Hunspell and today's trunk and emacs-24
branch.
If you invoke Hunspell outside of Emacs, does it accept "doesn't" as
correct spelling? Here's what I get when I type "doesn't" into
Hunspell and hit RET:
hunspell -a
@(#) International Ispell Version 3.2.06 (but really Hunspell 1.3.2)
doesn't
*
The asterisk response means the word is correct.
next prev parent reply other threads:[~2014-07-01 15:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 4:16 bug#17890: 24.4.50; flyspell highlights ``doesn't'' incorrect Leo Liu
2014-07-01 6:25 ` Glenn Morris
2014-07-01 11:13 ` Leo Liu
2014-07-01 13:03 ` Agustin Martin
2014-07-01 13:32 ` Leo Liu
2014-07-01 15:43 ` Eli Zaretskii [this message]
2014-07-01 16:23 ` Leo Liu
2014-07-01 16:49 ` Agustin Martin
2014-07-02 7:33 ` Leo Liu
2014-07-02 14:45 ` Eli Zaretskii
2014-07-02 15:23 ` Leo Liu
2014-07-02 15:36 ` Stefan Monnier
2014-07-02 16:20 ` Eli Zaretskii
2014-07-02 16:39 ` Leo Liu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ionh3x0k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17890@debbugs.gnu.org \
--cc=agustin.martin@hispalinux.es \
--cc=sdl.web@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.