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

[Daiki Ueno]

KO Myung-Hun <address@hidden> writes:

> I'm using this in libiconv. On OS/2, a charset is not specified
> generally. Just only a locale is specified. And all LC_xxx are not
> specified. Just only LANG is specified. For examples, set LANG=ko_KR for
> Korean. And the case that charset aliases are used is that '.' to
> specify a charset is not found or a buffer is overflowed, which is
> impossible if a charset is correct. So charset-to-charset mapping is not
> useful on OS/2.

Thanks for the update.

>> Also if it changes anything in the OS/2 port of gettext, consider
>> updating this file:
>> http://git.savannah.gnu.org/cgit/gettext.git/tree/os2/README.OS2
>> 
>
> Ok. If I work on gettext later, I'll consider.

I meant to ask if the patch could potentially change the behavior
described in that documentation.  Would you mind double-checking that?

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.

Regards,
--
Daiki Ueno