[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#57531: 28.1; Character encoding missing for "eo"
From: |
Eli Zaretskii |
Subject: |
bug#57531: 28.1; Character encoding missing for "eo" |
Date: |
Thu, 06 Oct 2022 17:20:28 +0300 |
> Date: Thu, 06 Oct 2022 11:28:59 +0000
> From: Gregory Heytings <gregory@heytings.org>
> cc: Eli Zaretskii <eliz@gnu.org>, jonathan@jonreeve.com,
> 57531@debbugs.gnu.org,
> schwab@linux-m68k.org
>
> 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).
>
> >
> > 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.
Should we perhaps have an entry in PROBLEMS with that information?
- bug#57531: 28.1; Character encoding missing for "eo", Lars Ingebrigtsen, 2022/10/04
- bug#57531: 28.1; Character encoding missing for "eo", Eli Zaretskii, 2022/10/04
- bug#57531: 28.1; Character encoding missing for "eo", Lars Ingebrigtsen, 2022/10/04
- bug#57531: 28.1; Character encoding missing for "eo", Po Lu, 2022/10/06
- bug#57531: 28.1; Character encoding missing for "eo", Gregory Heytings, 2022/10/06
- bug#57531: 28.1; Character encoding missing for "eo", Lars Ingebrigtsen, 2022/10/06
- bug#57531: 28.1; Character encoding missing for "eo",
Eli Zaretskii <=
- bug#57531: 28.1; Character encoding missing for "eo", Gregory Heytings, 2022/10/06
- bug#57531: 28.1; Character encoding missing for "eo", Eli Zaretskii, 2022/10/06
bug#57531: 28.1; Character encoding missing for "eo", Po Lu, 2022/10/04