Re: Rep:Re: [BUGS] Encoding Problem?

Started by Tatsuo Ishiialmost 24 years ago2 messages

t-ishii@sra.co.jp

almost 24 years ago

I guess you are inserting correct EUC Traditional
Chinese (EUC-TW)
characters but hard to tell what is happening unless
you are showing
us the character sequences in hexa decimal format.
--
Tatsuo Ishii
===============================
Many thanks! Tatsuo,

Please see below. Best Regards,

CN
---------------
linux:~$ cat /tmp/tt
1111
¦¨¥\
³\
2222
linux:~$ od -t x /tmp/tt
0000000 31313131 a5a8a60a 5cb30a5c 3232320a
0000020 00000a32
0000022

Are you sure that they are EUC-TW? Considering the byte swapping, they
are actually like this:

0x31,0x31,0x31,0x31,0x0a,
0xa6,0xa8,0xa5,0x5c,0x0a,
0xb3,0x5c,0x0a,
0x32,0x32,0x32,0x32,0x0a

Here we see a55c and b35c, which should never happen in EUC-TW, since
the each second byte is lower than 0x80.
I guess they are BIG5. If my guess is correct, you could set the
client encoding to BIG5 ("\encoding BIG5" in psql) and get correct
result.
--
Tatsuo Ishii

Import Notes

Reply to msg id not found: 200203050335.0a24@th00.opsion.frReference msg id not found: 200203050335.0a24@th00.opsion.fr

Tatsuo Ishii

t-ishii@sra.co.jp

almost 24 years ago

In reply to: Tatsuo Ishii (#1)

Re: Rep: [BUGS] Encoding Problem?

Glad to hear that. Enjoy PostgreSQL!
--
Tatsuo Ishii

From: cnliou@eurosport.com
Subject: Rep: [BUGS] Encoding Problem?
Date: Wed, 6 Mar 2002 10:40:48 GMT
Message-ID: <200203061040.30a8@th00.opsion.fr>

Show quoted text

Hello! Tatsuo,

Please pardon my ignorance! I did not understand the
basic concept: the client encoding being different
from server encoding.

It works perfectly after I rest my client from EUC_TW
and MULE_INTERNAL to BIG5.

Best Regards,

CN

linux:~$ od -t x /tmp/tt
0000000 31313131 a5a8a60a 5cb30a5c 3232320a
0000020 00000a32
0000022

Are you sure that they are EUC-TW? Considering the
byte swapping, they
are actually like this:

0x31,0x31,0x31,0x31,0x0a,
0xa6,0xa8,0xa5,0x5c,0x0a,
0xb3,0x5c,0x0a,
0x32,0x32,0x32,0x32,0x0a

Here we see a55c and b35c, which should never happen
in EUC-TW, since
the each second byte is lower than 0x80.
I guess they are BIG5. If my guess is correct, you
could set the
client encoding to BIG5 ("\encoding BIG5" in psql)
and get correct
result.
--
Tatsuo Ishii

--------------------------------------------------------
You too can have your own email address from Eurosport.
http://www.eurosport.com

Import Notes

Reply to msg id not found: 200203061040.30a8@th00.opsion.frReference msg id not found: 200203061040.30a8@th00.opsion.fr | Resolved by subject fallback