Hi Piotr,

On sab, 2018-10-27 at 18:40 +0200, Piotr Drąg wrote:

I’ve sponsored you in cvsl10n and accepted in Zanata. I’m not quite sure how to make a new language available on Fedora, but while I’m looking into it, you can start translating. I suggest starting with the packages from https://fedora.zanata.org/version-group/view/PriorityPackages/languages/eo — in particular anaconda, and maybe also system-config-language.

Thank you very much! I'll see what I can do.

Sincerely, Carmen

Hi Carmen,

Good to see one more translator. Please see my answers below:

28.10.2018 13:46 Carmen Bianca Bakker carmen@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: https://sourceware.org/bugzilla/

Debian used to do "eo_EO.UTF-8" until Esperanto was upstreamed.

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 I 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 `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.

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?

Regards,

Rafal

30.10.2018 12:53 Carmen Bianca Bakker carmen@carmenbianca.eu wrote:

[...] The problem, however, is projects depending on a country being available. Python's `locale` library behaves weirdly with Esperanto, and all sorts of downstream packages need to specially account for Esperanto because it's the odd one out---usually resulting in it being ignored entirely, because to be frank, Esperanto isn't the most common language. And that's totally understandable.

This sounds like a bug in a Python's "locale" library. Probably it is easy to fix but I don't volunteer to do it at the moment.

[...] Esperanto needs a "country" so that it's not constantly broken downstream:

• Create "eo_NL" in the spirit of "ia_FR": Just pick a country (or a lot of countries) and implement it.

• Create "eo_XX" or "eo_EO" with a fake "Esperantujo" country and currency.

• Create "eo_XX" or "eo_EO" that is identical to the current "eo" without actually adding any country information.

• Any combination of the above.

As much as possible I'd like to retain "eo" without a country. I hope it is possible to fix it as it is.

[...] https://bugzilla.redhat.com/show_bug.cgi?id=1643756

I would've also proposed a fix if I knew how to find the problem. But if you can find it, you have my thanks.

It seems that the fix has just been pushed.

I think I should also answer to your question from the previous email:

27.10.2018 11:32 Carmen Bianca Bakker carmen@carmenbianca.eu wrote:

[...] Unfortunately, from the big distributions, only Debian (and its derivatives) have Esperanto available as a choice out of the box. I want to make sure that Fedora also gets that option.

Could someone give me a few steps in the right direction to get that ball rolling? [...]

It is kinda ambiguous what it means that Fedora supports Esperanto (or any other language) because it may mean that the language is:

* supported by glibc (now done), * available in Zanata (done), * available as a choice in Anaconda, * available as a choice in system-config-language.

There may be other meanings but the list could be very long and eventually we would conclude that no language (except English) is perfectly supported by Fedora. :)

As a pattern you could review the issue tickets to add Filipino language in Fedora:

https://pagure.io/g11n/issue/43 https://pagure.io/system-config-language/issue/3

Regards,

Rafal