RE: wrong codepage used by gettext

[vassily ragosin]

hello,

> For vim, I can see two solutions:
> 
> a) vim knows for what purpose it will use each string, and 
> sets the environment variable OUTPUT_CHARSET before calling 
> gettext(). (There is a Woe32 specific caveat here; see
> http://www.haible.de/bruno/gettext-FAQ.html#windows_setenv)

I don't know, what Bram would say for that. Mind you, it needs to set/unset
that variable
each time console window title is about to change as well...

> Or equivalently, vim distributes each .mo file in two copies, 
> say, vim_gui.mo and vim_console.mo, uses dcgettext to access 
> them, and uses bind_textdomain_codeset("vim_console", "CP866").

not possible: too much confusion and headache for end-user and for
supporting our language pack releases.

> b) Let a low-level I/O layer take care of it. GNU clisp does 
> it this way; look at the ANSI2OEM_table transformation in the 
> function write_helper in 
> http://cvs.sourceforge.net/viewcvs.py/clisp/clisp/src/win32aux
> .d?rev=1.36&view=text

that would be a better solution, but what prevents from including it into
gettext itself?

resourcefully yours,
vassily

mailto:vr[at]vrgraphics.ru
pgp key id 0x92B4A97C