Re: Encoding and i18n

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Encoding and i18n
Date: 2007-10-06 16:52:12
Message-ID: 20071006165212.GE7190@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Gregory Stark wrote:
> "Alvaro Herrera" <alvherre(at)commandprompt(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2007-10-06 17:03:06 Re: Encoding and i18n
Previous Message Gregory Stark 2007-10-06 16:49:02 Re: Encoding and i18n