[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
wrong codepage used by gettext
From: |
vassily ragosin |
Subject: |
wrong codepage used by gettext |
Date: |
Wed, 28 Apr 2004 05:14:28 +0400 |
hello,
sorta bugreport:
Gettext version: all gettext releases up to 0.13.1 have this bug.
Concerned platforms: WinNT console, maybe Win95 console as well
Background information: As usual with Microsoft, for "historic reasons",
different codepages are used by win32 gui and win32 console when working
with Russian 8-bit text. Console window uses cp866, GUI uses cp1251 as a
native encoding.
Description: When gettext performs the output to win32 *console* stdout,
wrong (cp1251) codepage (instead of cp866) is used for Russian locale. As a
result, localized messages output to win32 console from gettext-enable
console programs are not usable, because most of the mature Russian-speaking
population do not have the ability of builtin libiconv in their brains to be
able to decipher wrong codepage messages on the fly.
Solutions: gettext need to convert text to cp866 when output is on windows
console stdout or when trying to set a title of win32 console with a
localized russian string.
Patches: sorry.
resourcefully yours,
vassily
mailto:vr[at]vrgraphics.ru
pgp key id 0x92B4A97C
- wrong codepage used by gettext,
vassily ragosin <=