Re: wrong codepage used by gettext

[Bruno Haible]

Bram Moolenaar wrote:
> The problem is not so much that it can't be solved in some way, but that
> the default codepage that gettext is using is wrong.

It is wrong for your case, because vim is outputting the resulting string
to a console.

If it were outputting it to an Emacs buffer, or to a file that is then
opened by the user in a GUI editor, it would be right.

But gettext cannot guess what an application will do with the strings.
Therefore there cannot be a default setting that is right in all cases.

> This means the
> invoking program must know all the details and tricks to get it right.

Yes. You know who is responsible for the Woe32 APIs.

Bruno