From: Eli Zaretskii <eliz@gnu.org>
To: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
Cc: 23097@debbugs.gnu.org
Subject: bug#23097: 24.5; ispell.el: lines with both CASECHARS and NOT-CASECHARS get sent to the spell checker
Date: Wed, 23 Mar 2016 20:22:42 +0200 [thread overview]
Message-ID: <83fuvh2gwd.fsf@gnu.org> (raw)
In-Reply-To: <56F2DC47.2090600@gmail.com> (message from Nikolay Kudryavtsev on Wed, 23 Mar 2016 21:11:19 +0300)
> From: Nikolay Kudryavtsev <nikolay.kudryavtsev@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.
next prev parent reply other threads:[~2016-03-23 18:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 18:11 bug#23097: 24.5; ispell.el: lines with both CASECHARS and NOT-CASECHARS get sent to the spell checker Nikolay Kudryavtsev
2016-03-23 18:22 ` Eli Zaretskii [this message]
2016-03-23 20:12 ` Nikolay Kudryavtsev
2020-08-15 4:22 ` Stefan Kangas
2020-08-15 16:15 ` Eli Zaretskii
2020-08-15 16:40 ` Stefan Kangas
2020-08-17 9:20 ` Nikolay Kudryavtsev
2020-08-17 12:48 ` Stefan Kangas
2020-08-17 16:40 ` Eli Zaretskii
[not found] ` <08f3ac29-761c-ced7-1e2f-0f643512b986@gmail.com>
2020-10-13 17:00 ` Eli Zaretskii
[not found] ` <83mu0q132o.fsf@gnu.org>
2020-10-14 19:20 ` Nikolay Kudryavtsev
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=83fuvh2gwd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23097@debbugs.gnu.org \
--cc=nikolay.kudryavtsev@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 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).