A week or so ago I explored this in depth because I was having the same
problems. (It was affecting an English file that had some Windows (CP-1252)
characters that didn't directly map to UTF-8. That message is at
http://lists.mysql.com/mysql/212392. I didn't mention it in my posting, but
latin1 is CP-1252. I couldn't get that to work, either.
I don't know how it would apply directly to your situation, but I think you
are running into a similar kind of problem. I also can't guarantee that my
conclusions were entirely correct.
Perhaps someone else can add to this.
The Infoshop by Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032
860.674.8796 / FAX: 860.674.8341
>From: sulochan acharya [mailto:sulochan@stripped]
>Sent: Sunday, April 27, 2008 6:01 AM
>Subject: Problem with character set and connection collation
>here is my problem:
>I am trying to set mysql to unicode character, so that i can get my
>dictionary application to look at words in Nepali.
>here is my setting:
>mysql charset: utf-8 unicode
>when i make a new database:
>mysql connection collation is utf8-general-ci
>and my new database collation is also utf-general-ci
>i import tables into this database using mysql command : source /path to
>when i browse the tables in this database i dont see nepali world
>seems like mysql cant read the characters;