On 09/09/2007, Kai Schlamp <kschlamp(a)roborg.com> 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.
You normally need to instruct mysqldump not to bother messing about
with the character set during export; see
http://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki#Character_set.
You may also be able to run the dump file through iconv or similar if
it's been corrupted.
Rob Church