GNU bug report logs - #20741
24.4; flyspell doesn't work with abbreviations ending in a period

Previous Next

Full log

View this message in rfc822 format

From: Reuben Thomas <rrt <at> sc3d.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 20741 <at> debbugs.gnu.org
Subject: bug#20741: 24.4; flyspell doesn't work with abbreviations ending in a period
Date: Mon, 14 Feb 2022 15:28:42 +0000

[Message part 1 (text/plain, inline)]

On Mon, 14 Feb 2022 at 10:45, Lars Ingebrigtsen <larsi <at> gnus.org> wrote:

> Reuben Thomas <rrt <at> sc3d.org> writes:
>
> > To be honest, I'm not sure Emacs can do much here. As far as I can
> > tell, hunspell doesn't cope well with characters like "." that
> > normally are non-word characters, but *can* occur in a word.
> >
> > Relatedly, see: https://github.com/hunspell/hunspell/issues/361
>
> So it's a problem on the hunspell side, and not because Emacs is
> considering the "." to be a non-word character?  (I haven't tried to
> debug what's going on.)


For natural language, yes.

There's also a problem in common abbreviations like "i.e.", which is
> considered as the words "i" and "e", apparently...
>

This is indeed the case, and it's not normally a problem because Emacs does
not spellcheck words so short.

I was wondering whether Emacs could query the backend speller whether it
> had the word "foo." in the dictionary before squiggly-lining "foo", but
> I'm very unfamiliar with how these functions work.
>

It could!

-- 
https://rrt.sc3d.org

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.