Bug#1013946: lintian: wrongly report unknown-locale-code ber
Hi Tobias,
Dr. Tobias Quathamer wrote:
> The safest way for lintian would probably be to use ISO 639-3 as a source
> for locale checking, because those codes represent an individual language.
> The vast majority of program translations are into an individual language,
> so the check seems plausible.
>
> For bonus points, you could also check ISO 639-5 and print a warning (or
> info) that this locale code represents a language group rather than an
> individual language. :-)
>
> This is essentially Axel's latest suggestion -- except that I'd suggest to
> use ISO 639-3 instead of ISO 639-2 as authoritative source.
Thanks for this summary and especially also all the history! (And for
reading our long mails which showed bit by bit our experiences and
discoveries. :-)
> Sorry for this long e-mail, but languages and their codes are pretty
> hard ...
No need to be sorry!
Will try to implement this in lintian.
Thanks again!
Regards, Axel
--
,''`. | Axel Beckert <abe@debian.org>, https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Reply to: