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

[Ernesto Baschny [cron IT]]

Hi Martin,

Martin Bless wrote: on 17.08.2007 19:45:

> Problem:
> In a freshly installed Dummy-TYPO3-4.1.2 all UTF-8 installation you
> will find that your MySql-dump will contain UTF-8 errors right away.

What do you mean with "MySql-dump will contain UTF-8 errors"? Which
MySQL version are you using? What is the exact "error" you get and when?
I think it is not illegal to have latin-1 bytes in UTF-8 tables (or the
other way around), its just a matter what you do with that data in your
application. So I wonder where did you hit this problem?

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).

But you are right that in general no charset conversion is made when
reading in ext_tables_static+adt.sql. This is not really possible,
because we will have to know (and record) the charset for every INSERT
statement in that file as we could have different charsets in a single
installation (e.g. each language has its own default charset). Another
choice would be to force this file to be UTF-8 encoded by default, but
then we will have to know the language for each single INSERT statement
to be able to do a conversion to the chosen charset for that specific
installation. Both I consider non-trivial.

Best and easiest is to use UTF-8 in ext_tables_static+adt.sql and have
people use forceCharset to UTF-8 if they want to use them. And instead
of fixing the provided sysext/cms/ext_tables_static+adt.sql file, we
should just drop those static templates "for good". :)

Cheers,
Ernesto