unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jonathan Reeve <jonathan@jonreeve.com>
Cc: 57531@debbugs.gnu.org
Subject: bug#57531: 28.1; Character encoding missing for "eo"
Date: Fri, 02 Sep 2022 08:52:29 +0300	[thread overview]
Message-ID: <83h71qqq5e.fsf@gnu.org> (raw)
In-Reply-To: <87h71r0w5z.fsf@jonreeve.com> (message from Jonathan Reeve on Thu, 01 Sep 2022 18:47:10 +0000)

> Date: Thu, 01 Sep 2022 18:47:10 +0000
> From: Jonathan Reeve <jonathan@jonreeve.com>
> 
> 
> When my language and locale are set to "eo," (Esperanto), the character
> encoding in Emacs is the wrong character encoding. It should be UTF-8,
> but instead it's something else.

Thank you for your report.

Can you tell what is the default encoding in that case?

> I think the problem is in the =locale-language-names= variable,
> which has these lines:
> 
>     ("en_IN" "English" utf-8) ; glibc uses utf-8 for English in India
>     ("en" "English" iso-8859-1) ; English
>     ("eo" . "Esperanto") ; Esperanto
>     ("es" "Spanish" iso-8859-1)
> 
> The line ("eo" . "Esperanto") should probably instead be ("eo"
> "Esperanto" utf-8).

If you want the UTF-8 encoding to be the default, why is your locale
set to "eo" and not to "eo.UTF-8"?

In general, Emacs prefers taking the locale's codeset from your
system's definitions, to avoid overriding the user's system setup.  It
only applies default encoding when the locale doesn't specify the
codeset, or when a locale can support only a single codeset.

> To test this, set your LANG variable to "eo" and then notice that the
> character encooding (locale-coding-system) is not utf-8, as it should be.

Are you saying that the Esperanto locale _must_ use UTF-8?  If so,
why?  AFAIK, ISO-8859-3 covers the Esperanto characters, so UTF-8 is
not the only possible codeset for Esperanto locales.





  reply	other threads:[~2022-09-02  5:52 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 [this message]
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
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=83h71qqq5e.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=57531@debbugs.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).