Support locales language codes from /usr/share/i18n/SUPPORTED

[buhtz]

Describe the problem

Hello,

*unixoid system using the locales system do have a file /usr/share/i18n/SUPPORTED with the list of supported language codes. I am not sure where it comes from but gettext/glibc/locales is somehow involved.

Setup the system language (e.g. via dpkg-reconfigure locales on Debian-based systems) that list is used to provide available languages. This is one of the reasons why my own application, using Weblate as translation platform, need to support that language identifiers.

But Weblate (using the translate.codeberg.org instance) seems not to support it. On example is "Serbian (Latin)"; the language code sr@Latin is not offered in the "Add language" dialog.

Would be nice to have this.

Regards,
Christian Buhtz

Solution brainstorm

Provide all languages from /usr/share/i18n/SUPPORTED

Describe alternatives you have considered

My current workaround would be to rename that files from Weblate everytime I sync Weblate with my upstream repo.

Screenshots

Additional context

• https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103042
• Rename language identifiers to support /usr/share/i18n/SUPPORTED bit-team/backintime#2468

[nijel]

While some languages might be missing in our language data, Weblate uses BCP language codes internally, so sr@latin will map to sr_Latn. You can choose how newly named files will be named using Language code style https://docs.weblate.org/en/latest/admin/projects.html#component-language-code-style

[buhtz]

I'll check this out next time I sync my Weblate with my upstream project.

[nijel]

Just to make it clear: this setting changes how Weblate creates new languages; it has no effect on existing ones. If you rename them in the repository, Weblate should handle that just fine thanks to alias mapping between different language code styles.

[github-actions]

The issue you have reported is now resolved. If you don’t feel it’s right, please follow its labels to get a clue for further steps.

• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.