Re: prevent encoding conversion recursive error

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>, pgsql-patches(at)postgresql(dot)org
Subject: Re: prevent encoding conversion recursive error
Date: 2005-09-01 16:46:16
Message-ID: 20050901164616.GA30081@surnet.cl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Thu, Sep 01, 2005 at 05:48:55PM +0200, Peter Eisentraut wrote:
> Am Sonntag, 21. August 2005 01:48 schrieb Tom Lane:
> > One thing that occurred to me is that we might be able to simplify the
> > problem by adopting a project standard that all NLS message files shall
> > be in UTF8, period. Then we only have one encoding name to figure out
> > rather than N. Maybe this doesn't help much ...
>
> I suppose this would then break NLS on Windows, no?

We now have a patch to handle UTF-8 on Windows, via recoding to UTF-16
and back, so I guess not (not sure though). It would manage to annoy me
as a translator, but nothing too serious really.

--
Alvaro Herrera -- Valdivia, Chile Architect, www.EnterpriseDB.com
"Escucha y olvidars; ve y recordars; haz y entenders" (Confucio)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew - Supernews 2005-09-01 16:58:00 Re: TODO item: set proper permissions on non-system schemas
Previous Message Patrick Welche 2005-09-01 16:41:34 upgrade path / versioning roles

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2005-09-01 16:49:32 Re: sum(int4)/sum(int2) improvement
Previous Message Josh Berkus 2005-09-01 16:31:55 Re: Version number in psql banner