[Bug localedata/23857] Esperanto has no country

["digitalfreak at lingonborough dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=23857

Rafal Luzynski <digitalfreak at lingonborough dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |digitalfreak@lingonborough.
                   |                            |com

--- Comment #5 from Rafal Luzynski <digitalfreak at lingonborough dot com> ---
Hello Carmen, thank you for filing this bug report.

(In reply to Carmen Bianca Bakker from comment #0)
> [...]
> I still need to file bug reports for the first two examples, and there are
> more
> examples that I haven't recorded in long-term memory.  [...]

I encourage you to file those bug reports.  Are they maybe caused by the
previous bug in glibc packaging in Fedora?

> [...]
> 1. Create "eo_NL" just like Interlingua---an auxiliary conlang similar to
>    Esperanto--- has "ia_FR".  Separate locales might need to be created for
>    different countries.

I was not aware of this case with Interlingua.  I would rather go for renaming
"ia_FR" to "ia" so that "eo" would not be alone anymore :-) but my knowledge
about Interlingua is too little to enforce it now.

> [...]
> Alternative #6 is to keep the status quo and fix all the bugs in third party
> projects that do not account for the special case of Esperanto.

This is my preferred choice and therefore I agree with Florian (comment 1) that
this is not a bug here.  Also, I think it's good if we approach other projects
and explain them how to fix the issue correctly.

(In reply to Carmen Bianca Bakker from comment #2)
> (In reply to Florian Weimer from comment #1)
> > There are other artificial languages which may face the same issue once we
> > add it to glibc.  Yiddish currently has a US locale, but isn't this a bit
> > odd?
> 
> If there's a sizeable population of Yiddish speakers in the US, then that
> probably makes sense.

As far as I know yes, there is a large population of Yiddish speakers in the
US, they are about 160,000 people and I'm not sure but likely they are the
largest Yiddish population in the world.

> It wouldn't make sense for Yiddish speakers outside of
> the US, though.  Problem is: Do you want to create a glibc locale for every
> possible country where Yiddish is spoken in some capacity? [...]

Most of the time this makes sense if two (or more) populations speaking the
same language in two countries develop their languages to the extent that they
differ little and actually make two variants of a language.  Good examples are
US English vs. British English or Brazilian Portuguese vs. European Portuguese.

A secondary reason is when we want to provide other locale-dependent settings
for multiple countries speaking the same language.

So adding a locale makes sense if there is a population needing that. 
Existence of a locale in CLDR and an official recognition of a language by the
local authorities are good argument for adding a locale variant.

> Ideally I'd like to see language and country completely separated from each
> other instead of combined in locales, because that would ultimately make the
> most sense,

Multiple environment variables (LC_MESSAGES, LC_MEASUREMENT, etc.) solve this
problem to some extent.  That means, you don't have every combination of
language/country but you can choose a separate locale for different purposes
and that should be usually sufficient.

> but that would be a super big redesign that I am not comfortable
> with proposing.

+1

> I'm currently limiting my scope to making Esperanto (more)
> usable on Fedora Workstation, and I think some of my above suggestions could
> significantly improve the status of Esperanto with relatively little effort
> (i.e., fixing all application bugs).

Thank you for your effort, please continue.

Again, I think this is not a bug but I don't mind if we discuss this here.

-- 
You are receiving this mail because:
You are on the CC list for the bug.