Hi Mantis devs (and
Unicode support planned in 1.1, after some testing in my working
converted all the strings files to utf-8 (in cvs head).
So any NEW
(and upgraded) installation could use any national chars correctly with any
settable thru UI or autodetection are all utf-8.
There is currently
no easy way to upgrade the already entered text in existing installations
characters already in database will probably break).
reason, legacy non-utf8 string files are still included, and you can use them
via config_* if needed.
It is possible
to convert the entire database manually (unloading it to the text file,
converting with iconv
back), but, of course, I can not recommend this in production
removed 2 of string files: the non-unicode Italian translation (reported to be
Canadian French one (diff showed no differences from
any inconsistencies found.
Any help with
writing the db upgrading routine is welcome.
do NOT update non-utf8 language files anymore as they are considered