5

I have some legacy mysql files of the format frm, MYI and MYD that i wish to export to csv. Using sequel pro on OSX, i created a new database and copied those files over.

All the data can be accessed fine but i have major issues with the query results due to unknown encoding. I have no idea what format the previous programmer used.

This database contain English, Chinese, Japanese and Korean song titles but as i have no idea what format these names are encoded in, so i get weird characters using utf8 format:

ÄÐÉù ÂèÂèºÃ+ɵ´ó½ã+ÆÃË®¸è Àä¿ÕÆøµÄ¶À°× À¶É«µÄÃÎ

Most of them begins with A with an accent though, i wonder if they do provide any clue as to which encoding format the programmer used.

I've tried putting these text onto safari/chrome browser and ran through the various encoding options but to no avail.

Will anyone please help me?

  • I would say this looks like an issue with it not being UTF8 but UTF16. Too late for my brain to function now, but that A character is common on UTF issues. – jcolebrand Dec 27 '11 at 5:43
1

Is your client talking utf8? Run

SET NAMES utf8;

and see if your selects output correctly?

| improve this answer | |
0

I'm not familiar with Sequel Pro but here's my guess at what happened: The records we dumped out in utf8 correctly but the import was treating the dump as if it was latin1.

Ensure that both schemas are set to utf8 and both the export and import connections are told to talk in utf8.

Using the built in mysqldump command is pretty good about making sure all variables get set properly to avoid character encoding issues.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.