[TYPO3] Characterset weirdness

Dennis Cheung hkdennis2k at gmail.com
Mon Feb 13 04:36:34 CET 2006


First, forget all previous data.
Make sure your new records can input and display these broken character.
Then everything should be fine.

The bad news is, some informations were already lost while saving
these text into database.
You may have to find them all and fix these character manually after
you config it right.


On 2/8/06, Nikolas Hagelstein <hagelstein at hauptsache.net> wrote:
> hi,
> > add "SET character set UTF8" after mysql_pconnect (check
> > mysql website)
> yes it is my plan also ;)
> But i still got the problem that i am not able to import
> the dump.
> I guess the problem is the following:
> When exporting the dump  names are set to utf8 while db table
> is set to latin1 (mysql default). Imho this makes mysql convert
> the content of latin1 fields to utf8. In common with typo3 the problem
> is that there are already utf8 chars inside latin1 fields (e.q.bodytext
> which look
> unreadble when examined with phpmyadmin).
> These get "double encodet" which may cause problems during importing the
> dump.
> What do you think?
> cheers,
>          Nikolas
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english

More information about the TYPO3-english mailing list