Good to see one more translator. Please see my answers below:
28.10.2018 13:46 Carmen Bianca Bakker <carmen(a)carmenbianca.eu> wrote:
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".
If I understand correctly, these problems are solved now. Otherwise,
as a locale data maintainer for glibc project I'll be happy to fix
them. You can contact me directly but better file a bug report here:
Debian used to do "eo_EO.UTF-8" until Esperanto was
It's hard to speak for Debian but it looks like a temporary solution
which can be dropped now as it has been already resolved upstream.
I did a Dutch VM install of Fedora 29 today, and started seeing what
could do to make Esperanto available. I'll list my findings here:
- `locale -a` does not yield 'eo'.
I've verified and indeed, you are right. Thanks for spotting this bug.
- Esperanto is not available in GNOME.
It's likely a consequence.
- After installing `glibc-langpack-eo`, Esperanto is listed in
-a` and becomes available in GNOME. It then becomes a simple trick of
editing /etc/locale.conf, and everything appears to work at first
- 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.
Exactly as you wrote. Yes, even if glibc-langpack-nl is not installed
Dutch is available because it is included in glibc-all-langpacks.
It's a bug that Esperanto is not included in glibc-all-langpacks. Also,
it's a bug that glibc-all-langpacks installed in all systems by default
because it was meant only as a backward compatibility solution for upgrade
of old systems. We were discussing this during Flock this year. Of course,
it's good that you have Dutch available because you want it but also you
have 200 other languages which you don't want.
It's likely that Esperanto was skipped due to its symbol "eo", without
a country. In many scripts it is expected that "*_*" mask represents all
locales. With introduction of "eo" it should be changed to "eo *_*".
It is changed in many places but likely there is one or few omissions.
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.
Definitely it's a packaging bug in Fedora, not even upstream, and it seems
to be easy to fix. Have you filed your bug report?