On 09/09/2007, Kai Schlamp schlamp@gmx.de wrote:
Hm, still having problems. Is there perhaps a way to forbid MySQL the reencoding when importing a SQL dump, so that Ãœ stays as it is, not encoded to Ãâ€", although it comes from an utf-8 file and goes to a latin1 table? Cause that would solve that tricky problem.
From your first post, I understood that both MySQL belong to you, right? I mean, you have access to them in whatever way you want. If that's the case, try to install MySQL Administrator (now is an element in the GUI Tools package). MySQL Adminitrator has the backup function which has been working every well to me. The backup file is a SQL file within which I could see that charset for every table is specified clearly (in UTF-8) for my case.
Restoring back is also very simple. Try it.
Platonides wrote:
Kai Schlamp wrote:
The only thing I can think of, is that by importing the file back to
the
new db, the content of the dump file is encoded again. And that's why those two cryptic chars, are now four. Ü (1) -> Ãœ (2) -> Ãâ€" (4)
Ups, last one are 5 cryptic chars ... it was late ;-) So, I am unsure if my theory is correct.
Yes, your theory is correct. mysqldump will be too intelligent. See http://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki