14 Mar
2009
14 Mar
'09
9:57 p.m.
Le 14-mars-09 à 19:53, Vincent Massol a écrit :
We'd need to put huge disclaimers everywhere since
this would cause
problems with users (the majority?) who have MySQL or other dbs set in
ISO8859-1, or their containers set a ISO8859-1 as the default, right?
Actually no.
My experience is that there's no "encoding mismatch" even with a mysql
which is set to iso-8859-1 while xwiki and jdbc is set to utf-8. The
only mismatch we endured until we moved to a mysql that's parametrized
for utf-8 is the storage inability for high-bytes characters (my test
cases was lambda λ and leq ≤) which simply got garbled after the
persist and read cycle happened (may take one hour sometimes on xwiki).
Is mysql in UTF8 by default?
It was in my MacOSX MySQL which I downloaded (from mysql.org) about a
year ago.
Same for my colleague on Windows.
Same for our sysadmin with a Linux MySQL downloaded from there.
But it was not the case with the mysql coming from a 3-years old SuSE
installation.
Same question for tomcat or other JEE containers.
Many many many times the platform encoding is used rather than the
containers' encoding. So that's MacRoman on mac! (enjoy!)
The re-encoding happens transparently though, there's no commonality
between that back-end and front-end.
One thing that has bitten me more often than not is that Apache Httpd
defaults to iso-8859-1 set explicitly on files with suffix html (so
the mime-type is text/html;charset=iso-8859-1 instead of leaving to
the meta head element the luxury of specifying that). I believe it
should not affect normal XWiki though.
paul
PS: I think that a sane admin that does an update will diff xwiki.cfg
and will see the difference!