Bug#1013946: lintian: wrongly report unknown-locale-code ber
Axel Beckert <abe@debian.org> writes:
> Thanks for your effort, Russ! That was my first guess, too.
> But upon deeper inspection I found that this is likely not an issue in
> iso-codes as "ber" is correctly not in
> /usr/share/iso-codes/json/iso_639-3.json but in …/iso_639-2.json and
> …/iso_639-5.json as it is a code for a language group. (Which kinda
> makes it suspicious for me to be used in locales. But then again I'm
> not a linguist.)
Sorry, I followed up on the bug and forgot to explicitly cc Lintian and of
course that message didn't come through.
I worked out the same thing, and I'm fairly sure that means that this is
not a valid locale. It's the code for the Berber language *group*, and
the individual members of that group have their own 639-3 codes, so that
seems to imply to me that those translations were tagged with the wrong
code.
Fabio also followed up and noted that there are a few translations for ber
in Launchpad, but they're all partial and probably not usable.
Tobias probably knows more, as iso-codes maintainer, but my guess is that
this is a mistake on the Launchpad side and those translations should be
for one of the specific languages of the group rather than being coded to
the 639-5 language group code. I think Lintian should still continue to
use 639-3.
That said, I'll leave it to you to decide if you want to hang on to the
bug or not. :)
--
Russ Allbery (rra@debian.org) <https://www.eyrie.org/~eagle/>
Reply to: