Re: prevent encoding conversion recursive error

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>, pgsql-patches(at)postgresql(dot)org
Subject: Re: prevent encoding conversion recursive error
Date: 2005-08-20 23:48:49
Message-ID: 17347.1124581729@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Is there a TODO here?

Yeah:

* Fix problems with wrong runtime encoding conversion for NLS message files

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 ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2005-08-21 14:26:48 Re: PostgreSQL 8.0.3 and Ipv6
Previous Message Tom Lane 2005-08-20 23:40:02 Re: A couple of patches for PostgreSQL 64bit support

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2005-08-21 01:18:49 Re: PL/Perl embedding string common elements
Previous Message Tom Lane 2005-08-20 23:40:02 Re: A couple of patches for PostgreSQL 64bit support