Re: Encoding and i18n - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Encoding and i18n
Date
Msg-id 20071006165212.GE7190@alvh.no-ip.org
Whole thread Raw
In response to Re: Encoding and i18n  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: Encoding and i18n
List pgsql-hackers
Gregory Stark wrote:
> "Alvaro Herrera" <alvherre@commandprompt.com> writes:
> 
> > Gregory Stark wrote:
> >
> >> So does the _() macro automatically recode it to the current server encoding?
> >
> > Well, I'm not sure if it's _(), elog() or what, but it does get recoded.
> > If I have a different client_encoding and get a NOTICE, then both the
> > server and client get a message in the corresponding encoding.
> 
> Actually I was thinking about things like formatting.c which take localized
> strings and return them as data which can end up in the database. If they're
> in the wrong encoding then they'll be invalidly encoded strings in the
> database.

Oh, I didn't think of that.  Let me see if I can get an invalid string
into the database that way.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: Gregory Stark
Date:
Subject: Re: Encoding and i18n
Next
From: Andrew Dunstan
Date:
Subject: Re: Encoding and i18n