Kent Tong <[EMAIL PROTECTED]> writes:
> You mean the OS fails to convert unicode strings to Big5 or the
> OS assumes the bytes are already in Big5?
The latter.
> It is the locale used for initdb or the default system locale
> set in Windows that is used by the collation routines that you
> mentio
Peter Eisentraut wrote:
On a POSIX system, you can do
$ LC_ALL= locale charmap
and verify manually that the printed charmap (= character set encoding)
matches what you use in PostgreSQL. I don't know whether an equivalent
interface exists on Windows.
Right, there is no such command.
Reading and
Kent Tong wrote:
> Is there any way to check?
On a POSIX system, you can do
$ LC_ALL= locale charmap
and verify manually that the printed charmap (= character set encoding)
matches what you use in PostgreSQL. I don't know whether an equivalent
interface exists on Windows.
> I have other prog
Peter Eisentraut wrote:
Here is a test (run in pgadmin III):
1. createdb db1 -E Unicode
Probably your locale does not support Unicode. You need to pick an
encoding that matches your locale or vice versa.
Is there any way to check?
I have other programs reading and writing Unicode on this
compute
Kent Tong wrote:
> I'm running PostgreSQL v8 beta4 on Win2K. The default language
> selected in Win2K is Big5.
Big5 is an encoding, not a language.
> I am using the Windows installer to install it. Everything is
> left as default except that the locale for initdb is set to
> "traditional-chinese"
