From: Eli Zaretskii <eliz@gnu.org>
To: Sebastian Urban <mrsebastianurban@gmail.com>
Cc: 42602@debbugs.gnu.org
Subject: bug#42602: Wrong (not-)casechars value for "polish" in ispell-dictionary-base-alist
Date: Thu, 30 Jul 2020 16:26:07 +0300 [thread overview]
Message-ID: <831rktf828.fsf@gnu.org> (raw)
In-Reply-To: <ba87a214-8ce8-038a-864e-27c29ce38680@gmail.com> (message from Sebastian Urban on Thu, 30 Jul 2020 13:39:55 +0200)
> From: Sebastian Urban <mrsebastianurban@gmail.com>
> Cc: 42602@debbugs.gnu.org
> Date: Thu, 30 Jul 2020 13:39:55 +0200
>
> > I don't understand this change. Values above octal 377 cannot be
> > right in the above regexps, because they are supposed to be in
> > Latin-2 encoding, which is a single-byte encoding, and so can only
> > handle values below octal 400. How did you come up with those
> > values?
>
> Basically, C-x = on a char, which gave me octal values.
This gives you the Unicode codepoint, not its Latin-2 encoding. They
are different. The database in ispell.el uses Latin-2 encodings of
Polish characters.
> Well, I did some tests, e.g. switched back to the original value of
> "polish" in my "pl" dictionary, and... it works. And if I change from
> iso-8859-2 to utf-8 in my "pl" (with original value from "polish") it
> doesn't work. So, as you later wrote - wrong character encoding,
> I guess.
>
> Looking for a cause (in default settings), I think I found it in
> ispell-dictionary-base-alist and ispell-dictionary-alist. During
> "transfer" from *-base-* to ispell-dictionary-alist, the value of
> CHARACTER-SET is changed in all cases from iso-* or cp1255 to utf-8,
> then ispell uses these (from ispell-dictionary-alist) when it "talks"
> with Aspell.
>
> On the other hand, if I use Emacs 26.3 from Cygwin, everything works
> out of the box, I don't even have to set "polish" as default
> dictionary. But there, in Cygwin command line, "env | grep LANG" gives
> "LANG=pl_PL.UTF-8".
Native MinGW builds cannot use the UTF-8 encoding.
So, do we have a problem to solve, or can this issue be closed?
next prev parent reply other threads:[~2020-07-30 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 16:12 bug#42602: Wrong (not-)casechars value for "polish" in ispell-dictionary-base-alist Sebastian Urban
2020-07-29 18:43 ` Eli Zaretskii
2020-07-30 11:39 ` Sebastian Urban
2020-07-30 13:26 ` Eli Zaretskii [this message]
2020-07-31 10:52 ` Sebastian Urban
2020-08-13 0:07 ` Stefan Kangas
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=831rktf828.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=42602@debbugs.gnu.org \
--cc=mrsebastianurban@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).