[TYPO3-dev] Bug 1039 - Why T3 has that few success in asia!!!

[Elmar Hinz]

Hi all,

bug 1039 mentions -- rather as a subordinate clause -- the problem to
store UTF-8 into an UTF-8 database. 

Michael Stucki writes on 28.07.06 16:58:

===========================================

Just curious: Imagine that phpMyAdmin in TYPO3 would render the chars correctly - they would still be broken in an external phpMyAdmin installation!

I think the problem is much more difficult: TYPO3 does not offer a way to store data in UTF-8 _natively_ (right?)

I just made some tests and converted a complete database from latin1 to UTF-8. But now the fonts were broken when using forceCharset=utf8.

I would really like to discuss this in Dietikon...

===========================================

This is a heavy, heavy, heavy bug and it is really surprising that it has
not been soleved yet. (Has it been solved meanwhile?)

If you can't store UTF-8 cleanly into an UTF-8 database, you will not be
able to execute alphabetical sorting queries for characters, that are non
ASCII. So it's a limited problem for european languages with many ASCII
characters but makes Typo3 nearly useless for non european languages.
Right?

Are there any plans to fix this before version 5.0? 

Regards

Elmar