unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: 20741@debbugs.gnu.org
Subject: bug#20741: 24.4; flyspell doesn't work with abbreviations ending in a period
Date: Fri, 05 Jun 2015 22:23:49 +0300	[thread overview]
Message-ID: <83twumnem2.fsf@gnu.org> (raw)
In-Reply-To: <87pp5az1u7.fsf@sc3d.org>

> From: Reuben Thomas <rrt@sc3d.org>
> Date: Fri, 05 Jun 2015 15:06:40 +0100
> 
> flyspell marks as incorrect “etc.”, “i.e.”, “e.g.” &c.

I can reproduce part of this with en_GB, but not with en_US.  So I
think it's an issue with the dictionary, not with flyspell or ispell.

> flyspell is of course behaving as expected: “.” is in OTHERCHARS, and as
> it comes after the word, it is not included.

What OTHERCHARS are you looking at?  In Emacs 24.4 and later,
ispell.el takes that value from the dictionary's .aff file, not from
the internal database.  So if you customized ispell-dictionary-alist,
try without those customizations, you shouldn't need them in v24.4.

> ispell sets my default dictionary to en_GB (from my locale, I presume),

Yes.  But you can override that, if you want.

> I tried to move “.” to CASECHARS and NOT-CASECHARS in a custom
> dictionary definition:
> 
> ("en_GB" "[[:alpha:].]" "[^[:alpha:].]" "['0-9’-]" t
>   ("-d" "en_GB")
>   nil utf-8)

You shouldn't need all that in Emacs 24.4.  Try not to customize the
dictionary at all.





  parent reply	other threads:[~2015-06-05 19:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05 14:06 bug#20741: 24.4; flyspell doesn't work with abbreviations ending in a period Reuben Thomas
2015-06-05 14:08 ` bug#20741: Workaround Reuben Thomas
2015-06-05 19:23 ` Eli Zaretskii [this message]
2015-06-05 21:42   ` bug#20741: 24.4; flyspell doesn't work with abbreviations ending in a period Reuben Thomas
2015-06-06  6:49     ` Eli Zaretskii
2015-06-06  9:35       ` Reuben Thomas
2015-06-06  9:38         ` Reuben Thomas
2015-06-06 10:03           ` Eli Zaretskii
2015-06-06 10:08             ` Reuben Thomas
2015-06-06 10:11               ` Reuben Thomas
2015-06-06 10:36                 ` Eli Zaretskii
2015-06-06  9:58         ` Eli Zaretskii
2022-02-13  9:04         ` Lars Ingebrigtsen
2022-02-13 12:37           ` Eli Zaretskii
2022-02-13 21:33             ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-14 10:44               ` Lars Ingebrigtsen
2022-02-14 13:08                 ` martin rudalics
2022-02-14 15:28                 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-14 13:34               ` Eli Zaretskii
2022-02-14 13:43                 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-14 15:07                   ` Stephen Berman
2022-02-14 15:21                   ` Eli Zaretskii
2022-02-14 15:27                     ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-14 16:42                       ` Eli Zaretskii
2022-02-14 17:01                         ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-14 18:08                           ` martin rudalics

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=83twumnem2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=20741@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).