#90: jabber lives in utf8 world, and the mysql must know it explicitly
------------------------+---------------------------------------------------
Reporter: don_oles | Owner: smoku
Type: enhancement | Status: new
Priority: major | Component: General
Version: 2.1 | Blocking:
------------------------+---------------------------------------------------
Long time ago, since MySQL 4.1, the use of my.cnf to set the client
character set is very very deprecated, and the right way to put data to
MySQL is explicitly specifying client character set. This is done by
issuing SET NAMES, which in our case should be
SET NAMES 'utf8'. Without that the national character set encoded data
like names etc goes into MySQL as utf8 but it thinks that it is in default
'latin7' encoding, and the data becomes in very useless encoding to any
other application.
--
Ticket URL: <http://jabberd2.xiaoka.com/ticket/90>
jabberd2 <http://jabberd2.xiaoka.com/>
jabberd2 project
_______________________________________________
jabberd2 mailing list
[email protected]
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
