Should message subjects always be converted to UTF-8?

Still looking in the attachments SQL table, I notice several subjects
looking like this:

=?ISO-8859-1?B?W3J0LWRldi51aW8ubm8gIzE3XSBGb3Ig5SBibGkgb3BwcmV0dGV0IHNv?= =?ISO-8859-1?B?bSBicnVrZXI=?=

Why aren’t these subjects converted from ISO-8859-1 MIME encoding to
UTF-8 when storing them in the database?

The subject without this MIME wrapping are stored in UTF-8, so I
surprised me that these ugly subject strings were not converted.

That sure sounds like a bug. But we’ve discovered another issue in our
handling of mime-encoded words. Expect to see RT convert all message
headers with embedded mime encoded bits to be stored as UTF8 mime
encoded bits.On Sep 3, 2004, at 4:12 AM, Petter Reinholdtsen wrote:

Still looking in the attachments SQL table, I notice several subjects
looking like this:

=?ISO-8859-1?B?
W3J0LWRldi51aW8ubm8gIzE3XSBGb3Ig5SBibGkgb3BwcmV0dGV0IHNv?=
=?ISO-8859-1?B?bSBicnVrZXI=?=

Why aren’t these subjects converted from ISO-8859-1 MIME encoding to
UTF-8 when storing them in the database?

The subject without this MIME wrapping are stored in UTF-8, so I
surprised me that these ugly subject strings were not converted.


Rt-devel mailing list
Rt-devel@lists.bestpractical.com
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel