GNU bug report logs - #23097
24.5; ispell.el: lines with both CASECHARS and NOT-CASECHARS get sent to the spell checker

Previous Next

Full log

Message #19 received at 23097 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefan <at> marxist.se>
Cc: 23097 <at> debbugs.gnu.org, nikolay.kudryavtsev <at> gmail.com
Subject: Re: bug#23097: 24.5; ispell.el: lines with both CASECHARS and
 NOT-CASECHARS get sent to the spell checker
Date: Sat, 15 Aug 2020 19:15:14 +0300

> From: Stefan Kangas <stefan <at> marxist.se>
> Date: Fri, 14 Aug 2020 21:22:24 -0700
> Cc: Nikolay Kudryavtsev <nikolay.kudryavtsev <at> gmail.com>, 23097 <at> debbugs.gnu.org
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> From: Nikolay Kudryavtsev <nikolay.kudryavtsev <at> gmail.com>
> >> Date: Wed, 23 Mar 2016 21:11:19 +0300
> >>
> >> Each entry ispell-dictionary-alist has elements called CASECHARS and
> >> NOT-CASECHARS. They are used for defining what gets sent to the spell
> >> checker and what does not.
> >>
> >> One use case for them is that, if you have two dictionaries for
> >> languages with totally different alphabets, you can spellcheck a file
> >> where both languages are mixed together. In theory.
> >
> > Don't you need to restart the spell-checker each time you switch the
> > dictionaries?  AFAIK, only Hunspell supports such mixed
> > spell-checking, and with Hunspell you don't need to break the line
> > into separate words in that case.  With any other spell-checker, you
> > need to restart it whenever you switch languages.
> 
> It seems like this is a limitation of external software then, and not in
> Emacs?  Should this therefore be closed, or is there anything more to do
> here?

Yes, I think we should close this issue.

Previous Next

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