| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: More message encoding woes |
| Date: | 2009-03-31 20:06:28 |
| Message-ID: | 20090331200628.GC23023@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> At first that sounded like an ideal answer, but I can see a gotcha:
> suppose the translation's author's name contains some characters that
> don't convert to the database encoding. I suppose that would result in
> failure, when we'd prefer it not to. A single-purpose string could be
> documented as "whatever you translate this to should be pure ASCII,
> never mind if it's sensible".
One problem with this idea is that it may be hard to coerce gettext into
putting a particular string at the top of the file :-(
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-03-31 20:33:26 | Re: SSL over Unix-domain sockets |
| Previous Message | Pavel Stehule | 2009-03-31 20:04:23 | protect dll lib initialisation against any exception, for 8.5 |