|
|
Posted by Dikkie Dik on 11/15/07 15:13
> I have to port data from MySQL 4.1.x to MySql 4.0.27 (The client is
> changing hosts). Call these S for source and D for destination.
>
> On D, if I put in data with an apostrophe (using addslashes), it goes
> in fine and comes out fine. However, data from S which is now in D
> via an export/import (done already, but I can redo it if needed) when
> retrieved via PHP comes up with a strange sequence of âEURO(tm) instead of
> an apostrophe. Also, the e with the back accent mark as in Café comes
> out CafÃ(c),
>
> S has a default character set of lantin1, while D has a character set
> of utf8.
OK. Let's anlyse this. What you are seeing if utf-8, but rendered as
latin-1. It is a real pity that you have to backport data, as encoding
support only gets better with the versions. Therefore, getting back
makes things worse. Your best bet is to adapt the database in the most
recent version of the two and then backport it.
But if you get utf-8 anyway (even if rendered incorrectly), I suppose
this went well. You can always check by using the mysql_dump utility and
see what strings it generates. This is one of the few reliable methods
to see how the strings are stored.
So what is wrong is that you see data in utf-8, but your client does not
know it.
Take a look at my.cnf (your MySQL config file). It contains a section
[mysql], a section [mysqld] and a section [client]. Check if the client
section has its "character set" option set to utf-8.
>
> I have tried an "alter table foo character set latin1" on D. No
> help. I have then gone and put it back to utf8. Nothing changes. I
> have also tried exporting from S specifying it as utf8 and importing
> it on D. No luck there either.
>
> When I go into phpMyAdmin and look at the data, I see an apostrophe.
>
> Short of digging through all the data and doing an update, or looking
> at the export from D, massaging it, and reimporting it, I don't know
> how to fix these data.
So far, it could be a mysql issue. But you have not told us what
application renders the query results. If you have a web page that just
tells the browser to render "text/html; charset=iso-8859-1" and send
strings in utf-8, it is clear that you will get the above output. In
that case, it is a PHP problem.
It can be solved by sending the correct encoding. This can be done in
PHP.INI (server-wide, or from an apache config section-wide), or just by
sending the appropriate Content-Type header "by hand".
Good luck!
Navigation:
[Reply to this message]
|