Dada Mail can speak UTF-8 and almost expects that everything else around it does, too.
That means:
If you're installing Dada Mail for the first time, there's nothing you'll need to do, but below are some guidelines on how to keep your lists configured, so you continue to have a good experience.
If you're upgrading, make sure your configuration reflects the advice below.
It's heavily advised to keep everything in Dada Mail speaking UTF-8 without
any real exceptions.
By default, the config variable, $HTML_CHARSET is set to, UTF-8
Keep it that way, same case (UTF-8) - same everything.
Dada Mail is only tested with the charset set this way.
Set this as, UTF-8 UTF-8
There's really only a few choices recommended for Dada Mail.
Should work.
If you have any trouble with 8bit, try quoted-printable. Because of the
amount of time that Dada Mail creates, tweaks, formats and templates out email
messages, the encoding can potentially get mucked up.
This potential mucking-up is mitigated when Dada Mail uses quoted-printable encoding
internally. This should be the default for email messages.
Have this option checked.
Encoding for PostgreSQL databases is done when the database is created - make sure
to create your database with a, UTF-8 encoding, like so:
CREATE DATABASE dadamail WITH ENCODING 'UTF-8'
Nothing you'll have to do, but do note that the schema that's shipped with Dada Mail for MySQL does set the character set and collation for UTF-8 in the tables where this is needed. If you're upgrading Dada Mail (from before 4.0.3), you may have to change the charset/encoding of your tables.
Nothing you'll have to do.
DBM Files have no encoding support, but Dada Mail knows this and compensates.
The MySQL schemas are set to create tables with an encoding of, UTF-8
Nothing has changed.
Nothing has changed.
The current support SQL backends, mysql (MySQL), Pg (PostgreSQL) and SQLite all have different ways to somewhat, "enable" their UTF-8 support.
add,
mysql_enable_utf8 => 1,
has been added to the $DBI_PARAMS hashref.
add,
pg_enable_utf8 => 1,
has been added to the $DBI_PARAMS hashref.
add,
sqlite_unicode => 1
has been added to the $DBI_PARAMS hashref.
No explicit encoding/decoding is done in Dada Mail when saving/retrieving data. Hopefully, the drivers are UTF-8-aware enough.
The Plugins and Extensions that come with Dada Mail have not been as thoroughly tested as the main program. There's still warts.
Dada Bridge has a unique position needing to handle a lot of different stuff thown at it and deal with it gracefully. Dada Mail does, in fact, handle, any realistic character set/encoding you throw at it, but Dada Mail will convert messages it receives to its internal format, before it resends it out to your list.
This means the encoding of your choice (8bit or quoted-printable) and the charset of your choice (as long as your charset is, UTF-8)
You are potentially going to have problems.
Its possible that, since List Settings were never decoded/encoded correctly in past versions, they'll show up the program (once you've upgrade) incorrectly. The easiest thing to do is to edit the mistakes and resave the information. For most of the program, you're going to have to manually export the information and re-import it with the correct encoding, sadly. Dada Mail will probably fail gracefully with old information, but it's possible that you'll see squiggly charaters, instead of what you want to see. There's nothing in Dada Mail that will stop this from happening. If you experience it (from old information), we're not going to count it as a bug, but rather a known issue.
Please let us know via the Support Boards:
http://dadamailproject.com/support/boards/
Or the developer mailing list:
http://dadamailproject.com/cgi-bin/dada/mail.cgi/list/dadadev/
Thanks!