Alvaro Herrera <alvherre@commandprompt.com> writes:
> Understood. In fact, after having a look at this patch and giving it a
> little refactoring I think it's pretty obvious; right now we're calling
> bind_textdomain_codeset only for the main domain, and with this patch we
> also set it for all other domains we use.
> Does this patch work for you?
Seems like this comment needs to move into the new function:
> * On Windows, we need to explicitly bind gettext to the correct
> * encoding, because gettext() tends to get confused.
More generally, should we push the bindtextdomain calls themselves into
the new function (and perhaps call it something else than
SetDomainCodeSet)? Seems like logically this should be thought of as
all one operation, ie, it's not clear to me that it ever makes sense to
call bindtextdomain without also worrying about encoding.
regards, tom lane