It is a common problem that a server uses a nontrivial character set
encoding (e.g., Unicode) but users forget to set an appropriate
client-side encoding. Then they get bogus displays for non-ASCII
characters because their client isn't actually prepared for Unicode.
There is a standard interface
I strongly object this idea. We already have had enough trouble with
initdb because of its locale awareness (I still think we should turn
on the --no-locale switch by default).
--
Tatsuo Ishii
It is a common problem that a server uses a nontrivial character set
encoding (e.g., Unicode) but
Peter Eisentraut [EMAIL PROTECTED] writes:
There is a standard interface (SUSv2) for detecting the character set
based on the locale settings.
Hmm. How trustworthy is that really?
If it works, great, but I wonder if we wouldn't be chasing a
will-o-the=wisp. My impression is that LC_xxx
On Wed, May 28, 2003 at 11:56:07PM +0200, Peter Eisentraut wrote:
There is a standard interface (SUSv2) for detecting the character set
based on the locale settings. I suggest we use this (if available) in
applications like psql and pg_dump by default unless it is overridden by
the usual