Hi Thomas,
you are right, the database table character set was latin1_swedish_ci,
after converting it to utf8_general_ci it works fine. Thx
@Paul what should be the correct character set for all mysql tables?
Because mine are mix... I would convert them to utf8 but I'm not sure if
this is save. Should we correct the mysql update script?
Harald
On Mon, 31 Dec 2012 21:36:08 +0100, Tomas Kuliavas
<[email protected]> wrote:
2012.12.27 11:57 Harald Leithner rašė:
Hi,
I have some problems with utf8 characters and timsieved and sievecmd.
If I try to use roundcube sievemanage plugin to add a out of office
reply
with utf8 characters like umlauts it double encode them. Even if I use a
plaintext file with utf8 characters and import it with sievecmd it get
encoded.
The only way it works for me is to save it directly in the database.
Should UTF8 work?
dbmail 3.0.2 git revision 22b964b653ba149b63b9b6787aeac7803c2121e5
libsieve2-1 2.2.9-1 (Debian)
Which db backend are you using?
Which charset is set in dbmail database schema?
Which charset is used in your db client connections by defaut?
Double encoding could happen, if client does not care about charset used
in its queries and DB charset does not match default client library
charset.
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
