Hi! On Thu, 2026-04-09 at 05:19:23 +0000, [email protected] wrote: > Am 08.04.2026 17:33 schrieb Holger Wansing: > > Did you try, to rename this file (and the "Language:" header > > into sr@latin? > > No, because "sr@latin" is IMHO not a valid identifier regarding IETF > BCP 47 language tag standard.
I don't think that matters? The only valid Language names are the ones that match locale definitions (or their reduced variants), see for 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. > I won't mix standards. If there is a Debian policy making "old" > POSIX/gettext language identifiers > mandatory I'll think about renaming all of my language files. 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). > > My experience is, that there are in fact many problems with > > translation files > > in Debian packages, but noone cares. > > "Noone cares" is the reason why the whole translation component > should be disconnected from the tracker. I think this bug report is either misplaced or invalid, and should be closed? Thanks, Guillem
