Noah Misch escribió:
> On Tue, Dec 17, 2013 at 01:42:08PM -0500, Bruce Momjian wrote:
> > On Fri, Dec 13, 2013 at 10:41:17PM +0900, MauMau wrote:
> > > [Fix]
> > > Disable message localization during session startup. In other
> > > words, messages are output in English until the database session is
> > > established.
> >
> > I think the question is whether the server encoding or English are
> > likely to be better for the average client. My bet is that the server
> > encoding is more likely correct.
> >
> > However, you are right that English/ASCII at least will always be
> > viewable, while there are many server/client combinations that will
> > produce unreadable characters.
> >
> > I would be interested to hear other people's experience with this.
>
> I don't have a sufficient sense of multilingualism among our users to know
> whether English/ASCII messages would be more useful, on average, than
> localized messages in the server encoding. Forcing English/ASCII does worsen
> behavior in the frequent situation where client encoding will match server
> encoding. I lean toward retaining the status quo of delivering localized
> messages in the server encoding.
The problem is that if there's an encoding mismatch, the message might
be impossible to figure out. If the message is in english, at least it
can be searched for in the web, or something -- the user might even find
a page in which the english error string appears, with a native language
explanation.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services