On 4/28/06, Sergio Polini <[EMAIL PROTECTED]> wrote:
What's happening about locales/languages?
I've tried to install PHP-Nuke and Xoops, but one of them (I don't
remember which one, now ;-)) doesn't like utf8 encoding, because it
creates too long primary keys for MySQL.
So I remerged MySQL and replaced "utf8" with "latin1"
in /etc/mysql/my.conf.
I've emerged Mediawiki (thanks Ric!) with the math USE flag, but when
I try to save a page containing a formula I get the error message:
"1267: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and
(utf8_general_ci,COERCIBLE) for operation '=' (localhost)"
Yes! My wikidb database was created with latin1_swedish_ci
collation!!!
And phpmyadmin says to me that MySQL charset is utf8!!!
Who has set those collation values??? I didn't...
Sergio
That's exactly the reason we still use mysql 4.0 in our production environment.
The mysql charset thingy is basically a whole load of mess.
A brief search on mysql's bug database shows some of the encoding bugs
and unicode key length not correctly calculated are still not properly
fixed yet they pushed their production version to 5.0.
We might be switching to postgres, at least it supports views,
triggers and handles encoding properly. The only thing preventing us
from doing so is that we use Mantisbt, which only works with mysql.
-- Joe
--
There are 3 kinds of people in the world:
Those who can count, and those who can't.
--
gentoo-user@gentoo.org mailing list
