Bug#1013946: lintian: wrongly report unknown-locale-code ber
Hi Russ,
Russ Allbery wrote:
> So in short, I think I talked myself back around to your solution.
> :)
Same to me, I talked myself back around to your (previous) opinion.
:-) Hilarious!
So we both seem to have had good arguments. :-)
Hrm, a serious thought on this: Why not implement both variants?
What if we
* make unknown-locale-code look at ISO 639-1, 639-2, 639-3 and even
639-5 for generally valid codes, and then
* add a new, maybe pedantic-level warning which is only emitted if a
language group is used in a locale name, i.e. check locales against
ISO 639-5 and if one of these (which IIRC include the language groups
present in ISO 639-2) is used as locale, we emit a tag which might
be named locale-uses-language-group-code or similar?
This currently sounds if it would make use of all our arguments for
and against including ISO 639-2, would be backwards compatible and
more precise and helpful.
Ok, and I should really go to bed now. :-)
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: