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
Am 28.06.22 um 02:31 schrieb Axel Beckert:
Still would be happy about input from Toddy on this. :-)
Hi all,
thanks a lot for your research and insights ...
I'm not an ISO expert, either, but from my reading and understanding the
relationship between the standards (and the intended use) is
Axel Beckert writes:
> 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
>
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
Hi,
one more comment:
Russ Allbery wrote:
> 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
Axel Beckert writes:
> Anyway, JFTR: I just looked at how lintian in Debian Stable (i.e.
> 2.104.0 in Bullseye) does the locale code lookup. It had it's own data
> file for that (and hence now using iso-codes is good as it is no more
> duplicating these 33kB of data) and that file
>
Control: tag -1 + help
Hi Russ,
Russ Allbery wrote:
> > 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
Axel Beckert 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
Control: affects -1 - lintian
Control: reassign -1 lintian
Control: found -1 2.115.1
Hi Russ,
Russ Allbery wrote:
> Thanks for the report! Lintian gets the canonical list of locales from
> the iso-codes package, and if I'm reading the last modification times from
> its Salsa repository
user lintian-ma...@debian.org
usertag 1013946 + false-positive unknown-locale-code
tag 1013946 + confirmed
retitle 1013946 lintian: [FP] Wrongly reports unknown-locale-code "ber" (POSIX
locales: ISO 639-2 vs 639-3 vs 639-5)
kthxbye
Hi Fabio,
Fabio Fantoni wrote:
> Package: lintian
> Version:
Il 27/06/2022 23:53, Russ Allbery ha scritto:
Russ Allbery writes:
Fabio Fantoni writes:
Hi, on a lintian output I saw:
W: xapps-common: unknown-locale-code ber [usr/share/locale/ber/]
but ber locale exists:
https://www.loc.gov/standards/iso639-2/php/langcodes_name.php?code_ID=54
Thanks for
Russ Allbery writes:
> Fabio Fantoni writes:
>> Hi, on a lintian output I saw:
>> W: xapps-common: unknown-locale-code ber [usr/share/locale/ber/]
>> but ber locale exists:
>> https://www.loc.gov/standards/iso639-2/php/langcodes_name.php?code_ID=54
> Thanks for the report! Lintian gets the
Control: reassign -1 iso-codes
Control: retitle -1 ber locale missing from iso_639-3.json
Control: affects -1 lintian
Fabio Fantoni writes:
> Hi, on a lintian output I saw:
> W: xapps-common: unknown-locale-code ber [usr/share/locale/ber/]
> but ber locale exists:
>
Package: lintian
Version: 2.115.1
Severity: normal
Hi, on a lintian output I saw:
W: xapps-common: unknown-locale-code ber [usr/share/locale/ber/]
but ber locale exists:
https://www.loc.gov/standards/iso639-2/php/langcodes_name.php?code_ID=54
14 matches
Mail list logo
