Hi Piotr, all,
On sab, 2018-10-27 at 18:40 +0200, Piotr Drąg wrote:
I’m not quite
sure how to make a new language available on Fedora, but while I’m
looking into it
I've been looking into it as well. It's a rabbit hole that goes quite
deep, because the glibc maintainers did not upstream Esperanto for the
longest time. In the end Esperanto has been added without region. So
where a normal locale is "nl_NL.UTF_8", Esperanto has "eo.UTF-8".
Debian used to do "eo_EO.UTF-8" until Esperanto was upstreamed.
I did a Dutch VM install of Fedora 29 today, and started seeing what I
could do to make Esperanto available. I'll list my findings here:
- `locale -a` does not yield 'eo'.
- Esperanto is not available in GNOME.
- After installing `glibc-langpack-eo`, Esperanto is listed in `locale
-a` and becomes available in GNOME. It then becomes a simple trick of
editing /etc/locale.conf, and everything appears to work at first
glance.
- Rather strangely, however, `glibc-langpack-nl` is NOT installed, yet
Dutch is available and functional all the same.
- This appears to be because `glibc-all-langpacks` is pre-installed and
contains copies(?) of all the individual langpacks. Except,
it appears, Esperanto.
I've been reading the glibc.src.rpm cursorily, but I can't really find a
cause for this yet. Mostly because I don't know Lua so well. My
suspicion was the thing that _always_ causes problems: Esperanto is the
only locale that doesn't have a region. But in the places where it
matters, the specfile appears to specifically account for that.
I'll send a bug report to the Fedora glibc maintainers, to see if they
can figure it out maybe.
With kindness,
Carmen