From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
---|---|
To: | jm(dot)poure(at)freesurf(dot)fr |
Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org, pgsql-odbc(at)postgresql(dot)org, Inoue(at)tpf(dot)co(dot)jp |
Subject: | Re: [ODBC] UTF-8 data migration problem in Postgresql 7.2 |
Date: | 2002-02-21 01:08:26 |
Message-ID: | 20020221100826Y.t-ishii@sra.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-odbc |
> I recompiled PHP with UTF-8 internal encoding. So no transcoding is performed.
Recompiled PHP with UTF-8? That sounds new to me. As far as I know,
there is no such a compiling option in PHP.
> > BTW, it seems entirely likely that Windows apps might display something
> > for UTF-8 sequences that are invalid according to the published specs.
> > It'd be just like Microsoft to "extend" the standard...
>
> It might be the case, I agree. Could it be a problem of surface (UCS-2
> characters embedded in UTF-8)? PostgreSQL 7.3 should accept more UTF-8
> characters anyway as I can display all Japanese characters. Many users may
> have the same problem. So why filter?
You need to make sure that M$ or whatever define such kind of
"extention" before jumping to the conclusion.
I still hard to believe E3/82/27 is a valid UTF-8 character even in
M$'s extention...
--
Tatsuo Ishii
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2002-02-21 01:08:33 | Re: UTF-8 data migration problem in Postgresql 7.2 |
Previous Message | Marc G. Fournier | 2002-02-21 00:49:20 | Re: Finally took the plunge ... |
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2002-02-21 01:08:33 | Re: UTF-8 data migration problem in Postgresql 7.2 |
Previous Message | Laurette Cisneros | 2002-02-21 01:05:25 | Re: odbc version |