Re: prevent encoding conversion recursive error

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 olvidar�s; ve y recordar�s; haz y entender�s" (Confucio)