17 Mar
2009
17 Mar
'09
1:14 p.m.
For latin1 databases, or any other limited encoding, a sanity check at storage migration sounds right or? Put lambda, close connection, reopen, read lambda worked? If not add a warning in the log. Paul Le 17-mars-09 à 10:46, Sergiu Dumitriu <[email protected]> a écrit :
The only problem I've seen in practice is the PDF export, which uses new String(bytes) and String.getBytes() without specifying the xwiki.cfg encoding. I've opened http://jira.xwiki.org/jira/browse/XWIKI-3361 which isn't hard to fix.
And now it's fixed, so there's no other problem for switching to utf8, except latin1 databases.