Bug#1103042: Status update

Hello Guillem,
thank you for the feedback.

Am 09.04.2026 18:44 schrieb Guillem Jover:
> example /usr/share/i18n/SUPPORTED. The sr_Latn language is thus 
> (AFAICS)
> invalid for gettext purposes, and it should not match any locale on the
> system, and would thus also not get used.

That po file is working fine within my application ("backintime"). It is 
Python3 using gettext in the background. Also my translation toolchain, 
incl. Weblate, does recognize that language identifier.

Didn't knew about the existence of /usr/share/i18n/SUPPORTED.
Is there any documentation about it or is it mentioned in the policy 
somewhere?
How is it created?

> As long as glibc and its locale definitions do not get updated to be
> aware of any different aliases, these .po files are not getting used
> at all (AFAICT).

As I said, gettext has no problem with that po file.

I won't ask GNU to move from one to another standard. But the question 
is if the Debian toolchain need to "guess the language". I see no value 
in it. And it is also still not clear how this "guessing" is 
implemented. I am not able to reproduce the error message on my system.

Thanks,
Christian