Re: [PATCH 02/14] Fix character encoding aliases for OS/2

[KO Myung-Hun]

Daiki Ueno wrote:
> KO Myung-Hun <address@hidden> writes:
> 
>>> For example, it says:
>>>
>>>   If the output character set is ommited from the LANG variable, the
>>>   default codepage is ALWAYS taken from the operating system (e.g. the
>>>   codepage setting from locale.alias is always ignored, so "russian"
>>>   stays just for "ru_RU" and not for "ru_RU.ISO-8859-5"); you may want
>>>   to set it just if you want to override the active OS/2 codepage.
>>
>> This patch does not change any behaviors of OS/2 port of gettext.
>> Because this patch embeds charset aliases into localcharset.c instead of
>> using charset.alias file, and fixes the problem a locale instead of a
>> charset if a charset is not specified is returned.
> 
> Thanks for checking, looks safe then.  One question is: where did you
> take the mapping data?  I found this chart:
> http://www.borgendale.com/locale.htm
> 

I used CODEPAGE and COUNTRY parts of OS/2 command references.

> I'm not sure how authoritative it is, but there are some differences
> from yours: ar_AA, bg_BG, lt_LT, lv_LV, and zh_CN.
> 

Owing to you, I've found that I omitted ar_AA and comments for code page
lists. Thanks.

And the differences of others is because cp915, cp921 and cp1381 are not
supported by libiconv. In these cases, I picked up code pages from
config.charset.

Finally, I changed a code page for bg_BG from cp1251 to cp855 which is
etc code page.

-- 
KO Myung-Hun

Using Mozilla SeaMonkey 2.7.2
Under OS/2 Warp 4 for Korean with FixPak #15
In VirtualBox v4.1.32 on Intel Core i7-3615QM 2.30GHz with 8GB RAM

Korean OS/2 User Community : http://www.ecomstation.co.kr

0001-Fix-character-encoding-aliases-for-OS-2.patch
Description: Text document