[Typo3] Did typo3 3.8 compatible to mysql 4.1??
Elmar Hinz
elmar.DOT.hinz at team.MINUS.red.DOT.net
Mon Nov 21 11:09:38 CET 2005
> for example. mysql 4.1 unicode compatible.
> I didn't notice that before I saw some character broken.
> And I found, mysqld using utf8, typo3 using utf8, but mysql_connect using
> iso-8859-1.
> All chinese character are broken inside database,
> (one utf8 character from typo3 it convert into three 8859-1 char, and then
> convert one 8859-1 char into one utf character again)
>
I did some testing my own and come to similar results.
* DB MySQL 4.1.11, Collation utf8_unicode_ci
* TYPO3 3.8.0
Setup: page.config.metaCharset = utf-8
Config: $[BE][forceCharset]=utf-8;
As long as I enter iso chars editing and output works fine.
But non ascii chars look *ugly* in the database in phpMyAdmin is set to
utf-8.
When I try to enter chinese or russian letters, I get an error window
directly after submit:
102: These fields are not properly updated in database: (bodytext)
Probably value mismatch with fieldtype.
A few days ago there was a discussion about a russian site. They needed
to setup the DB as iso-8859-1 to get a utf-8 site running. That sounds
paradox in some way and can't be the regular solution.
It may be that "SET NAMES 'charset_name'" don't work as Dennis suspected
in his first posting. Maybe it should bette be "SET CHARACTER SET
charset_name".
Elmar
--
Climate change 2005: Mexico, Guatemala, New Orleans, Sahel, Bangladesh,
Spain, Portugal, Austria, Swiss, France, ...
Production of CO2 is killing people.
Production of CO2 just for fun is killing people just for fun.
More information about the TYPO3-english
mailing list