[TYPO3-v4] Moving from UTF-8 as default to UTF-8 only in 4.6?

[Xavier Perseguers]

Hi,

> I'd like to suggest to drop all support for other character encodings
> besides UTF-8 in TYPO3 4.6, at least for internal processing.
>
> While we moved to have UTF-8 as a default, in theory you could still
> switch to other encodings in TYPO3 4.5. I do not see a benefit in having
> this possibility, but there are several drawbacks.
>
> For backend rendering, data storage in the database and frontend
> rendering there's no point in using other encodings.
>
> The only usecase for other encodings could be sending mails, but still
> converting to other encodings should then be the last step. All internal
> handling of strings should be done in UTF-8 (like MySQL does AFAIK).
>
> Do I miss something?

Prior testing with DBAL, as usual :-) (not usual that your forgot about 
it but usual that I come with that topic). For example, UTF8 support in 
MSSQL 2000 is a pain and personnaly I never tested it but besides that, 
I like the idea of course.

-- 
Xavier Perseguers
Release Manager TYPO3 4.6

TYPO3 .... inspiring people to share!
Get involved: http://typo3.org