all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: jonathan@jonreeve.com, Eli Zaretskii <eliz@gnu.org>,
	schwab@linux-m68k.org, 57531@debbugs.gnu.org
Subject: bug#57531: 28.1; Character encoding missing for "eo"
Date: Thu, 06 Oct 2022 14:13:54 +0200	[thread overview]
Message-ID: <87r0zlywsd.fsf@gnus.org> (raw)
In-Reply-To: <c13f0f0579d6fbd6c978@heytings.org> (Gregory Heytings's message of "Thu, 06 Oct 2022 11:28:59 +0000")

Gregory Heytings <gregory@heytings.org> writes:

> Actually that problem has been debugged: it's a NixOS bug.  NixOS
> rejects the locale to "eo.UTF-8" in its configuration files, even
> though "eo.UTF-8" is a perfectly valid locale.  It rejects it because
> the "eo.UTF-8" string is not present in some text file (apparently the
> "localedata/SUPPORTED" file from glibc).

Ah, right.  Somebody should report this to the NixOS people, I guess?

>> Yes, that would be helpful.  On this Ubuntu system, I just
>> uncommented the "eo" line in locale.gen and ran locale-gen, and that
>> made both the "eo" and "eo.UTF-8" locales available.
>>
>
> Another similar example is the en_IL (English Israel) locale.  X11's
> locale.alias indicates that "en_IL" alone means "en_IL.ISO8859-1", yet
> glibc provides only one encoding for "en_IL", namely "UTF-8".
>
> To avoid such bugs, the most reasonable thing to do for users is to
> always specify the encoding.

So I think the conclusion here is that after taking all the options into
consideration, we don't want to change anything on the Emacs side here,
both because of backwards compat issues, and the X encoding issues noted
by Po Lu.

I'm therefore closing this bug report.





  reply	other threads:[~2022-10-06 12:13 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r0zlywsd.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=57531@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=gregory@heytings.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.