-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've recently discovered a problem with Subject header encoding of Japanese text with mail notifications. the problem manifests in thunderbird (mac and windows) and Mail.app.
in thunderbird, the part of the encoding up until the first break point (where a subject is > 75 characters long and split into multiple encodings) is displayed properly, and then either a question mark or "mojibake" (basically a string of single byte characters that don't make any sense) is displayed. in Mail.app, the =?UTF-8?B? from the front and the ?= on the back of the encoded string are stripped and the subject is displayed as-is remaining. (I can provide screen shots if necessary) I've been able to determine that this occurs only when a mix of single-byte and 2-byte characters are in the subject at the same time. this happens whether the ticket is opened via the web interface or via the email gateway. I've poked around the source code to see if I could figure it out, but I haven't found anything coherent yet. Any help would be greatly appreciated. Thanks. Alan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFExvqkE2gsBSKjZHQRAmgXAKCbM9bBnYdjrDRI6tdQOTumwaMj0gCeJJrN vxiPvNaH9FMxJcRIfbEoKts= =VzA4 -----END PGP SIGNATURE----- _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com We're hiring! Come hack Perl for Best Practical: http://bestpractical.com/about/jobs.html
