On Thursday 11 September 2003 20:13, Peter Eisentraut wrote:
> Darko Prenosil writes:
> > Here is the idea: there is problem to find out in which encoding is using
> > mo file, but we can force gettext to serve known encoding for example
> > utf8. After that we can always convert from unicode to cl
Darko Prenosil writes:
> Here is the idea: there is problem to find out in which encoding is using mo
> file, but we can force gettext to serve known encoding for example utf8.
> After that we can always convert from unicode to client encoding.
Hmm, I've never heard of bind_textdomain_codeset().
- Original Message -
From: "Peter Eisentraut" <[EMAIL PROTECTED]>
To: "Darko Prenosil" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, September 10, 2003 7:20 PM
Subject: Re: [HACKERS] Trouble with error message encoding
> Dar
Darko Prenosil writes:
> I have encoding problems using translated error messages (7.4beta1).
> When database encoding is set to SQL_ASCII, all mesages arrive to client
> correctly respecting the CLIENT_ENCODING, but if I create database WITH
> ENCODING='unicode' or WITH ENCODING='latin2', m
I have encoding problems using translated error messages (7.4beta1).
When database encoding is set to SQL_ASCII, all mesages arrive to client
correctly respecting the CLIENT_ENCODING, but if I create database WITH
ENCODING='unicode' or WITH ENCODING='latin2', messages are displayed
corre
