Paul J Stevens wrote:
Mysql and postgresql users using anything but ENCODING=utf8 should take
notice. Dbmail uses utf8 internally because gmime uses utf8 internally.
You should do too. Convert your databases if you can, or plan to do so
soon. Unicode and its UTF8 representation are the future.
Converting your mysql database is trivial, but takes time and table
locks (making the database read-only). A couple of 'ALTER' statements
got me going just fine.
Sounds good, but which collation should we use?
http://dev.mysql.com/doc/refman/5.0/en/charset-unicode-sets.html
There's utf8_bin, utf8_general_ci (default), utf8_unicode_ci and for me
there's utf8_estonian_ci too.
I'll hold 2.2.5 for just a day or two extra to see how this latest patch
works out. If there are unforseen problems, I'll rewind my tree a bit
and release svn revision 2564 as 2.2.5, or branch out from there if
anything needs to go in.
So test and time will learn. Stay tuned.
Running 2566 since a few minutes ago with latin1.
Alex
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
