| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com> |
| Cc: | "PostgreSQL-development Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Encoding and i18n |
| Date: | 2007-10-06 15:19:43 |
| Message-ID: | 87sl4otgmo.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Alvaro Herrera" <alvherre(at)commandprompt(dot)com> writes:
> Gregory Stark wrote:
>>
>> Reading the commit message about the TZ encoding issue I'm curious why this
>> isn't a more widespread problem. How does gettext now what encoding we want
>> messages in? How do we prevent things like to_char(now(),'month') from
>> producing strings in an encoding different from the database's encoding?
>
> The PO files include encoding information, so it's easy for the server
> to recode them from that to the server (or client) encoding, as
> appropriate.
So does the _() macro automatically recode it to the current server encoding?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-10-06 15:25:34 | Re: Encoding and i18n |
| Previous Message | Alvaro Herrera | 2007-10-06 15:15:55 | Re: Encoding and i18n |