Hi!
To rephrase for anyone else who stumbles across this
thread:
$wgDBmysql5 = false means that the tables are created with DEFAULT
CHARSET=latin1, which isn't especially a problem as long as the
software atop it (mediawiki) knows that it's actually storing UTF-8.
I wonder if DEFAULT CHARSET=binary would help here.
But when you use the Java library to speak to MySQL,
it notices that
the table is marked as latin1 and tries to convert your UTF-8 data for
you while importing.
You can hack around that by specifying connectionEncoding=UTF-8 in
JDBC params, then execute 'SET NAMES latin1', to avoid any
conversions ;-) Oh well, there might be some escaping issues, but
let's assume they don't exist.
--
Domas Mituzas --
http://dammit.lt/ -- [[user:midom]]