Re: Adding an en_SE locale

[Carlos O'Donell <carlos@redhat.com>]

On 8/21/24 8:01 AM, Rickard Armiento wrote:
> My conclusion is that even if it may be possible (perhaps with some
> compromise) to deal with the remaining issues, the end mix of
> settings will be complex for end users. Hence, maybe it is more
> user-friendly with separate en_DE, en_SE, en_*, etc. alongside the
> already existing en_DK. It would also help avoiding issues caused by,
> e.g., the en_SE designation already being in some use (e.g., in
> CLDR).
> 
> I have made my en_SE available here:
> 
> https://github.com/httk/locale-en_SE/blob/main/en_SE
> 
> I would be happy to hear any thoughts or suggestions related to
> taking the steps to contribute this into glibc.

At a high level the harmonization between what CLDR offers, and glibc offers is
important since it sets users up for a smoother experience when using applications
that use system localization vs. libicu-based localization.

The fact that cldr/common/main/en_SE.xml exists, is sufficient for us to review
adding en_SE to glibc.

There are 1067 XML files in cldr/common/main/, while only 347 xx_YY locales
in glibc/localedata/locales/, so we have a long way to go for harmonization
and the topics are complicated to audit.

-- 
Cheers,
Carlos.