Interesting. a 'é' shows up fine, but '中文' does not.
I wrote in about it. I will check to make sure it's not an issue with the Exchange server it's passing through first.
Seems to be related to this:
Things like é work since they're already in latin-1. I'm not sure why WHD doesn't just force UTF-8 in the schema. I implemented the MySQL 5.5 equivalent of the FAQ's suggestions:
character-set-server = utf8
collation-server = utf8_general_ci
init-connect='SET NAMES utf8'
Now, the characters aren't rendered as "??" when I submit from the web interface, but I get errors like:
There was a problem saving the ticket: com.webobjects.eoaccess.EOGeneralAdaptorException: EvaluateExpression failed: : Next exception:SQL State:HY000 -- error code: 1366 -- msg: Incorrect string value: '\xE7\xB9\x81\xE9\xAB\x94...' for column 'SUBJECT' at row 1
Converting to UTF-8 seems to work.
Even though the WHD docs explain how to pre-configure the db configs to force UTF-8 and lowercase table names, I do wonder, though, why the schema shipped with WHD doesn't simply define the relevant tables as UTF-8 explicitly, or at least why the app doesn't provide a warning when the db is configured without UTF-8 as the default before the schema is imported.