[mapguide-users] RE: Chinese text on feature lable are incorrect, feature data source is MySQL

[fishtrees]

Thank you,Dave

I have already set my database's default charset to UTF8 before I insert the
data, and the tables too.
and I don't use ODBC,however, the problem still exist.
Sometimes I use PHP work with MySQL, but without MapGuide ,either I set
default chartset to utf8 or not, it show "???" after import bakup from .sql
files, after I excute "set names utf8" ,the chinese text correct.

This is my first time work with PHP,MySQL and MapGuide, so, I think maybe
the problem caused by same reason. I insert spatial data from a .sql file
which created by shp2mysql.exe.

All of above is my guesswork. I'm not sure about that.

FishTrees



Dave Wilson-3 wrote:
> 
> You should ensure that your table definition uses the UTF8 charset. You
> may have to do an alter table to change the charset before you insert
> the data. I'm not sure that doing an alter after the table is populated
> will work. You may be able to create a database and set the charset
> default to UTF8 before you create any tables.
> 
> The MySQL FDO provider should have no problems retrieving double byte
> data. Note if you plan to use ODBC for MySQL their 3.51 ODBC connector
> (driver) does NOT support double byte characters according to their own
> documentation.
> 
> Regards,
> Dave
> 

-- 
View this message in context: http://www.nabble.com/Chinese-text-on-feature-lable-are-incorrect%2Cfeature-data-source-is-MySQL-tf3760491s16610.html#a10630465
Sent from the MapGuide Users mailing list archive at Nabble.com.