[Bug localedata/14684] New: Support ISO-3166 completely.

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug localedata/14684] New: Support ISO-3166 completely.

maiku.fabian at gmail dot com


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: [hidden email]

        ReportedBy: [hidden email]

                CC: [hidden email]

    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.
Reply | Threaded
Open this post in threaded view
|

[Bug localedata/14684] Support ISO-3166 completely.

maiku.fabian at gmail dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=14684



--- Comment #1 from csolisr at riseup dot net 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: [hidden email]

>         ReportedBy: [hidden email]

>                 CC: [hidden email]

>     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_t
able.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=ema
il

> ------- 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



--

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.