Re: Rep: [BUGS] Encoding Problem? - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject Re: Rep: [BUGS] Encoding Problem?
Date
Msg-id 20020306215956T.t-ishii@sra.co.jp
Whole thread Raw
List pgsql-hackers
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>

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


pgsql-hackers by date:

Previous
From: mlw
Date:
Subject: Re: Postgresql backend to perform vacuum automatically
Next
From: Bruce Momjian
Date:
Subject: Re: Postgresql backend to perform vacuum automatically