[TYPO3-core] RFC #7942: Enable UTF-8 by default

[Peter Niederlag]

Hello,

Am 10.11.2010 22:25, schrieb Jigal van Hemert:
> Hi,
[..]
> If you try to use data which contains characters which cannot be
> represented in the character set of the column (or table or database)
> data loss may occur, but other than that everything is converted
> automatically by MySQL.

On top of the loss of non represantable characters MySQL won't touch any 
binary fields, which might contain serialized data in some 
cases(remember TSconfig?, caches?, ...). Maybe this could be considered 
"broken by db design" but still why not avoid if that can easily be done?

[...]
> There may be cases where people specifically use a charset or collation.
> Suppose you have an Danish only website and want to ensure that sorting
> and comparing of titles is done according to Danish rules you could set
> the collation of those columns to utf8_danish_ci (or a similar collation
> compatible with the charset of the column).

Well, so far I didn't get any complaints about "broken collation" in 
utf-8 setups.

The collation issue is not really covered by TYPO3 yet IMO.

Greets,
Peter
-- 
Peter Niederlag * Ehlentruper Weg 70 * 33604 Bielefeld *
Fon (mobil): 0172 / 516 48 55 *
http://www.niekom.de * TYPO3 und EDV Dienstleistungen *