[TYPO3] Bug? Using UTF-8, 'Ä' in template.constants: Error 102!

[Karsten Dambekalns]

Hi.

Andreas Becker wrote:
> We figured out that it is mainly the way HOW you import the database.

Yes, of course! ;)

MySQL does now "know" the charset of the content (earlier it didn't care 
a f$#?k). So it tries to convert things between internal and external 
character sets. Which is a Good Thing[tm], at least in theory. :)

If the DB is latin1, and you feed it utf8, it'll try to convert.
If the DB is utf8 and you feed latin2, it'll try to convert.
If the DB is ... you get the point.

So either have matching charsets or matching settings. If you need to 
convert later, you can do this by dumping and reimporting, but make sure 
you dump structure and data seperately (make slife easier).

Another hint is to  make columns BINARY, then switch charset/collation 
and remove the BINARY again. This keeps MySQL from converting characters 
when switching a columns from latin1 to utf8 - which is something you 
don't want for an older database having utf8 in columns declared as latin1.

Karsten