| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | jm(dot)poure(at)freesurf(dot)fr |
| Cc: | pgsql-hackers(at)postgresql(dot)org, pgsql-odbc(at)postgresql(dot)org, Inoue(at)tpf(dot)co(dot)jp |
| Subject: | Re: UTF-8 data migration problem in Postgresql 7.2 |
| Date: | 2002-02-21 01:08:33 |
| Message-ID: | 20020221100833R.t-ishii@sra.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-odbc |
> You are right, Yudit shows an invalid UTF-8 character.
>
> For example, record OID 20643 has invalid =E3=82 character. But, when
> querying the PostgreSQL 7.1.3 database, I can see the missing character which
> displays well in Apache/PHP.
How did you judge "displays well"? Can you show me the window capture?
The broken UTF-8 (E3/82/27) should be E3/82/92 by guessing from a
consistency and grammertical correctness as Japanese according to
Hiroshi (and I agree with him).
--
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Warner | 2002-02-21 02:12:19 | Re: SET NULL / SET NOT NULL |
| Previous Message | Tatsuo Ishii | 2002-02-21 01:08:26 | Re: [ODBC] UTF-8 data migration problem in Postgresql 7.2 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2002-02-21 01:15:10 | Re: odbc version |
| Previous Message | Tatsuo Ishii | 2002-02-21 01:08:26 | Re: [ODBC] UTF-8 data migration problem in Postgresql 7.2 |