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.
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
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l