From: Gregory Heytings <gregory@heytings.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jonathan Reeve <jonathan@jonreeve.com>, 57531@debbugs.gnu.org
Subject: bug#57531: 28.1; Character encoding missing for "eo"
Date: Sun, 04 Sep 2022 23:35:37 +0000 [thread overview]
Message-ID: <6fb0e08e80e292e6c7a0@heytings.org> (raw)
In-Reply-To: <831qsrn1im.fsf@gnu.org>
>> The problem is in this line from `locale-language-names'. Here's what
>> it says:
>>
>> `("eo" . "Esperanto")'
>>
>> Here's what it should say:
>>
>> `("eo" "Esperanto" utf-8)'
>
> That's only correct for glibc systems, though, as I already explained. I
> found no authoritative place on the Internet which would mandate that
> the Esperanto locale should use or prefer UTF-8 as its encoding.
>
I don't think it's possible to find a truly authoritative source of
information about an artificial language. One semi-authoritative source
is Bertilo Wennergren, who is (according to Wikipedia) a member of the
Esperanto Academy and "holds the post of director of the Academy's General
Dictionary section". He appears to be the expert on that matter (namely
computer encodings for Esperanto), and explains on his website that:
Latino 3 is made for Esperanto and for the Galician, Maltese and Turkish
languages. However, few computer programs support Latin 3, and some bodies
have even directly discouraged the use of Latin 3. The Turks currently
prefer the character code Latin 5 (ISO 8859-9) . Esperantists also
currently prefer and should prefer Unicode instead of Latin 3. [1,
translation from Google]
He also gives instructions on how to configure a GNU/Linux distribution
for Esperanto:
To be able to use Esperanto well in Linux, it is necessary that the system
uses a Unicode locale. Fortunately, more or less all Linux distributions
currently use Unicode locales by default. To check which character code
your system's locale uses, type the following command: "locale charmap".
If the answer appears "UTF-8" (that is the most commonly used code
representation of Unicode), then everything about character code in your
locale is already in order. [2, translation from Google]
Amusingly, at the bottom of that page one finds:
It is also possible to speak Esperanto in the powerful text editor
"Emacs", but I know nothing about "Emacs". I myself mainly use the Vim
editor. Here are instructions for installing and configuring Unicode Vim
7.
So it seems safer to assume that the coding system is UTF-8 when the
locale is "eo" (which IIUC is what the above suggested change does), and
to expect users who would not like that default to add
(prefer-coding-system 'iso-latin-3)
in their init file, than to assume ISO-8859-3 when the locale is "eo"
(which IIUC is what Emacs currently does), and to expect users who do not
like that default to add
(prefer-coding-system 'utf-8)
in their init file.
[1] https://bertilow.com/html/signokodoj/latino3.html
[2] https://bertilow.com/komputo/linukso.html
next prev parent reply other threads:[~2022-09-04 23:35 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
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 [this message]
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=6fb0e08e80e292e6c7a0@heytings.org \
--to=gregory@heytings.org \
--cc=57531@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jonathan@jonreeve.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).