Follow-up Comment #21, bugs #1981 (project savane):

Hi,



while fixing a bug which prevented the Russian, Japanese and Korean
translations to be shown, I played around a bit with the utf-8 issue.



It is not too hard to set up savane to use utf-8; however, there are some
caveats.



I used the header() function to explicitely set the charset to utf-8 and added
".UTF-8" to all locales. Moreover, I converted the .po files to utf-8 and
regenerated the .mo files.



You can see the result in the savane test install at gna.org/test. It is fully
working for me.



Note that some texts are not managed through gettext, but are from the
database. Those texts won't display correctly under utf-8, because they were
stored in the DB using iso-8859-1 (or -15). As an example, see
<https://gna.org/test/projects/nasgaia/>.



In conclusion:

* The switch to utf-8 in the php source code is rather trivial. A couple of
lines in php/include/i18n.php have to be modified.



* The site-specific files can easily be converted, e.g. by using iconv.



* The database has to be converted. There is a mysql function for this,
CONVERT(). Its syntax is CONVERT(iso-8859-15-field USING utf-8), see
<http://dev.mysql.com/doc/mysql/en/charset-convert.html>.



All those steps are not really hard, but especially the last one involves a
huge amount of data. I'd suggest to make a backup of the DB first ... ;-)



    _______________________________________________________

Reply to this item at:

  <http://gna.org/bugs/?func=detailitem&item_id=1981>

_______________________________________________
  Message sent via/by Gna!
  http://gna.org/


_______________________________________________
Savane-dev mailing list
[email protected]
https://mail.gna.org/listinfo/savane-dev

Reply via email to