Bruce Momjian <> writes:
> Is there a TODO here?


* 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

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to [EMAIL PROTECTED] so that your
       message can get through to the mailing list cleanly

Reply via email to