Re: More message encoding woes - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: More message encoding woes
Date
Msg-id 20090331200628.GC23023@alvh.no-ip.org
Whole thread Raw
In response to Re: More message encoding woes  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: More message encoding woes  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: protect dll lib initialisation against any exception, for 8.5
Next
From: Peter Eisentraut
Date:
Subject: Re: SSL over Unix-domain sockets