Bug 14684 - localedef: support ISO-3166 (territory) completely (including user assigned codes)
Summary: localedef: support ISO-3166 (territory) completely (including user assigned c...
Status: NEW
Alias: None
Product: glibc
Classification: Unclassified
Component: localedata (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-08 04:37 UTC by Agron Selimaj
Modified: 2016-04-15 18:08 UTC (History)
3 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:
fweimer: security-


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Agron Selimaj 2012-10-08 04:37:54 UTC
Libc only partially complies with ISO-3166 by supporting only assigned and some reserved two letter codes.

There is no support for user-assigned, unassigned and other codes.

Libc should support all codes defined in ISO-3166, regardless of whether they are assigned or not.

The codes currently defined by ISO-3166 are:

All assigned codes,
All unassigned codes,
All reserved codes
and 
All user assigned codes.

Please find all defined codes by ISO 3166 at:
http://www.iso.org/iso/home/standards/country_codes/iso-3166-1_decoding_table.htm


Libc should also allow user to dynamically change language, monetary, address, etc. locale information for lets say "QQ" country code without have the need to add a new country to the system.

This way, every distribution will have localedata for all countries, the ones that exist now and the ones that will exist in the future.

For the countries that seize to exist, split or merge with other ones, we wouldn't have to create a new locale (or delete) for them in the Libc since Libc would have the whole table of ISO-3166 codes already in it. By whole table I mean assigned, unassigned and reserved codes.

Libc will be less dependent on the political status of each code, don't have to add/remove code for every political change, and will increase compatibility of programs across political changes - the country codes will always be there.


Thanks,
//Agron
Comment 1 csolisr 2012-10-08 17:04:14 UTC
>
> http://sourceware.org/bugzilla/show_bug.cgi?id=14684
>
>              Bug #: 14684
>            Summary: Support ISO-3166 completely.
>            Product: glibc
>            Version: unspecified
>             Status: NEW
>           Severity: normal
>           Priority: P2
>          Component: localedata
>         AssignedTo: unassigned@sourceware.org
>         ReportedBy: linuxmaster@verizon.net
>                 CC: libc-locales@sources.redhat.com
>     Classification: Unclassified
>
>
> Libc only partially complies with ISO-3166 by supporting only assigned and
> some
> reserved two letter codes.
>
> There is no support for user-assigned, unassigned and other codes.
>
> Libc should support all codes defined in ISO-3166, regardless of whether
> they
> are assigned or not.
>
> The codes currently defined by ISO-3166 are:
>
> All assigned codes,
> All unassigned codes,
> All reserved codes
> and
> All user assigned codes.
>
> Please find all defined codes by ISO 3166 at:
> http://www.iso.org/iso/home/standards/country_codes/iso-3166-1_decoding_table.htm
>
>
> Libc should also allow user to dynamically change language, monetary,
> address,
> etc. locale information for lets say "QQ" country code without have the
> need to
> add a new country to the system.
>
> This way, every distribution will have localedata for all countries, the
> ones
> that exist now and the ones that will exist in the future.
>
> For the countries that seize to exist, split or merge with other ones, we
> wouldn't have to create a new locale (or delete) for them in the Libc
> since
> Libc would have the whole table of ISO-3166 codes already in it. By whole
> table
> I mean assigned, unassigned and reserved codes.
>
> Libc will be less dependent on the political status of each code, don't
> have to
> add/remove code for every political change, and will increase
> compatibility of
> programs across political changes - the country codes will always be
> there.
>
>
> Thanks,
> //Agron
>
> --
> Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
>

Now that we're in that: is it possible to completely support at least the
section 1 of ISO 639? That would cover many of the languages that are
missing from libc, unless said languages required more effort than just
adding their respective code.

http://www.iso.org/iso/home/standards/language_codes.htm

- Carlos Solís
Comment 2 Chris Leonard 2013-08-24 15:37:42 UTC
Carlos, please open a new ticket if you have a different bug to report.  If you have a glibc locale file developed for each of the language codes in ISO-639-1 then by all means submit them.
Comment 4 Wei-Lun Chao 2014-12-03 01:45:42 UTC
(In reply to Wei-Lun Chao from comment #3)
> Found some discussions:
> http://blogs.koreanclass101.com/blog/2008/08/06/whats-the-difference-between-
> %ED%95%9C%EA%B5%AD%EC%96%B4-and-%ED%95%9C%EA%B5%AD%EB%A7%90/
> http://www.koreanclass101.com/forum/viewtopic.php?t=2402

Sorry, misposted! please ignore :)