| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | Hiroshi Saito <saito(at)inetrt(dot)skcapi(dot)co(dot)jp> |
| Cc: | "Serguei A(dot) Mokhov" <mokhov(at)cs(dot)concordia(dot)ca>, Ângelo Marcos Rigo <angelo_rigo(at)yahoo(dot)com(dot)br>, pgadmin-hackers(at)postgresql(dot)org |
| Subject: | Re: |
| Date: | 2003-10-01 17:33:32 |
| Message-ID: | 3F7B0FEC.4010707@pse-consulting.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Hiroshi Saito wrote:
>From: "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>
>
>
>
>>Serguei A. Mokhov wrote:
>>
>>
>>
>>>Hi,
>>>
>>>I think I have a similar issue... A pgAdmin III user contacted me with the
>>>question why they can't see the data in Russian and how to to solve the
>>>problem. I queried them for more information. I think their data must be
>>>encoded in some other encoding (e.g. KOI8-R) and when it gets to the
>>>client side, it's not converted.
>>>
>>>
>>>
>>>
>>This is correctly diagnosed, non-ascii data in a SQL_ASCII encoded
>>database will not be shown because the server doesn't know how to encode
>>it in Unicode.
>>
>>This is fixed for HEAD and BRANCH.
>>
>>
>
>No.
>Server encoding as below.
>
This is not suitable for non-ascii chars, because the upper bit will be
chopped off (ascii->utf8), effectively destroying the string, or
converted to a bogus char (xx), effectively destroying the string.
Regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Saito | 2003-10-01 17:39:24 | Re: |
| Previous Message | Jean-Michel POURE | 2003-10-01 17:28:25 | MacOSX compilation steps |