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
Describe the problem
Hello,
*unixoid system using the locales system do have a file
/usr/share/i18n/SUPPORTEDwith 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 localeson 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@Latinis 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/SUPPORTEDDescribe 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