From: Gregory Heytings <gregory@heytings.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jonathan@jonreeve.com, 57531@debbugs.gnu.org, schwab@linux-m68k.org
Subject: bug#57531: 28.1; Character encoding missing for "eo"
Date: Mon, 05 Sep 2022 12:00:12 +0000 [thread overview]
Message-ID: <0b2303e392221b7deeaf@heytings.org> (raw)
In-Reply-To: <83bkrukq1f.fsf@gnu.org>
>> (BTW, this also means that the OP could solve his problem by using
>> "eo.UTF-8" for his locale instead of only "eo".)
>
> That was suggested, but rejected, because the system in question (or
> maybe any GNU/Linux system?) doesn't have such a locale.
>
That was probably a misinterpretation of the OP. I'd bet that it would
work, even though, as Lars observed, the exact string "eo.UTF-8" does not
appear in /etc/locale.gen for example.
>
> But AFAIU locale.alias should have told Emacs which encoding is
> appropriate for "eo".
>
If Emacs relies on locale.alias, Latin-3 will be chosen. The "eo" locale
follows what other locales do, without ".UTF-8" the legacy encoding is
used. E.g. "en_US" is Latin-1 here but "en_US.UTF-8" is UTF-8, and
likewise "tr_TR" is Latin-9 but "tr_TR.UTF-8" is UTF-8.
>
> Andreas asked the OP what does locale.alias say about that, but I saw no
> response yet.
>
> What does "grep ^eo /usr/share/X11/locale/locale.alias" say on your
> system?
>
eo eo_XX.ISO8859-3
eo_XX eo_XX.ISO8859-3
eo: eo_XX.ISO8859-3
eo_XX: eo_XX.ISO8859-3
next prev parent reply other threads:[~2022-09-05 12:00 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 18:47 bug#57531: 28.1; Character encoding missing for "eo" Jonathan Reeve
2022-09-02 5:52 ` Eli Zaretskii
2022-09-03 1:28 ` Jonathan Reeve
2022-09-03 14:47 ` Eli Zaretskii
2022-09-03 16:54 ` Jonathan Reeve
2022-09-03 17:12 ` Eli Zaretskii
2022-09-03 17:32 ` Andreas Schwab
2022-09-03 17:58 ` Eli Zaretskii
2022-09-03 20:13 ` Andreas Schwab
2022-09-04 5:02 ` Eli Zaretskii
2022-09-04 6:32 ` Andreas Schwab
2022-09-04 6:54 ` Eli Zaretskii
2022-09-04 7:33 ` Andreas Schwab
2022-09-03 20:00 ` Jonathan Reeve
2022-09-04 5:37 ` Eli Zaretskii
2022-09-04 7:03 ` Andreas Schwab
2022-09-04 7:20 ` Eli Zaretskii
2022-09-04 7:34 ` Andreas Schwab
2022-09-04 7:46 ` Eli Zaretskii
2022-09-04 8:28 ` Eli Zaretskii
2022-10-04 11:44 ` Lars Ingebrigtsen
2022-10-04 12:39 ` Eli Zaretskii
2022-10-04 13:13 ` Lars Ingebrigtsen
2022-10-06 10:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-06 11:28 ` Gregory Heytings
2022-10-06 12:13 ` Lars Ingebrigtsen
2022-10-06 14:20 ` Eli Zaretskii
2022-10-06 15:15 ` Gregory Heytings
2022-10-06 16:05 ` Eli Zaretskii
2022-10-04 13:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-05 0:00 ` Gregory Heytings
2022-09-05 8:16 ` Gregory Heytings
2022-09-05 8:58 ` Lars Ingebrigtsen
2022-09-05 9:10 ` Gregory Heytings
2022-09-05 9:39 ` Andreas Schwab
2022-09-05 11:46 ` Gregory Heytings
2022-09-05 9:24 ` Andreas Schwab
2022-09-05 9:30 ` Gregory Heytings
2022-09-05 11:44 ` Eli Zaretskii
2022-09-05 14:15 ` Lars Ingebrigtsen
2022-09-05 11:40 ` Eli Zaretskii
2022-09-05 12:00 ` Gregory Heytings [this message]
2022-09-05 12:24 ` Eli Zaretskii
2022-09-05 12:38 ` Gregory Heytings
2022-09-05 13:04 ` Eli Zaretskii
2022-09-05 13:26 ` Gregory Heytings
2022-09-05 16:56 ` Andreas Schwab
2022-09-05 17:50 ` Jonathan Reeve
2022-09-05 18:20 ` Gregory Heytings
2022-09-05 22:41 ` Jonathan Reeve
2022-09-05 23:14 ` Gregory Heytings
[not found] ` <57ffb073-c4ea-da56-18c0-661b9d8ab929@heytings.org>
2022-09-05 23:21 ` Gregory Heytings
2022-10-04 13:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-04 13:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-04 23:35 ` Gregory Heytings
2022-09-05 11:29 ` Eli Zaretskii
2022-09-05 12:07 ` Gregory Heytings
2022-09-05 12:25 ` Eli Zaretskii
2022-09-05 12:59 ` Gregory Heytings
2022-09-05 13:11 ` Eli Zaretskii
2022-09-05 13:33 ` Gregory Heytings
2022-09-04 8:39 ` Andreas Schwab
2022-09-04 8:48 ` Eli Zaretskii
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=0b2303e392221b7deeaf@heytings.org \
--to=gregory@heytings.org \
--cc=57531@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jonathan@jonreeve.com \
--cc=schwab@linux-m68k.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).