| 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 15:15:55 |
| Message-ID: | 20071006151555.GE5618@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Of course, then it is up to the translator to get it right ... but I
think when he doesn't, people notice fairly quickly.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2007-10-06 15:19:43 | Re: Encoding and i18n |
| Previous Message | Shane Ambler | 2007-10-06 00:50:00 | Re: [SQL] Why does the sequence skip a number with generate_series? |