[TYPO3-dev] problem:: report & analysis: 4.1.2 is coming with codepage inconsistancy

[Michael Stucki]

Hey Ries,

> Of course it's a problem to have UTF-8 bytes in a latin-1 encoded table.
> This because the application expects latin-1 encoding and when we output
> to UTF-8 some encoding is needed.

Well, it's no problem to do it this way. As you see it works great in many
TYPO3 installations out there... :-)

But of course you are right. I think it's a big problem that was mainly
caused by the forceCharset and the multiplyDBfieldSize (some even don't use
that) settings. Although it works all fine, the data is tagged wrong
(latin1 but containing utf8) and users end up with chaos if they ever want
to fix this up (or need to export the data to another system).

I've started to do some research on how we can fix this big mistake, but I
could only test it on MySQL 5.0 so far...

So please have a look here and comment on it, if you are interested and want
to contribute: http://bugs.typo3.org/view.php?id=6098

>> The mentioned static-tables (from typo3/cms/) are almost all obsolete,
>> in special those that contain 8-bit codes (translation for several
>> old-school extensions).
> 
> fully agreed...

François Suter recently wrote an extension that will help us to create
static data tables based on our reference manuals, so we will most likely
continue to use that in future...

- michael
-- 
Use a newsreader! Check out
http://typo3.org/community/mailing-lists/use-a-news-reader/