Re: [ODBC] UTF-8 data migration problem in Postgresql 7.2
Tatsuo Ishii <t-ishii@sra.co.jp>
From: Tatsuo Ishii <t-ishii@sra.co.jp>
To: jm.poure@freesurf.fr
Cc: tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org, pgsql-odbc@postgresql.org, Inoue@tpf.co.jp
Date: 2002-02-21T01:08:26Z
Lists: pgsql-hackers
> 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