[Tickets #5972] Re: Subject line encoding problem

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=5972
-----------------------------------------------------------------------
 Ticket             | 5972
 Updated By         | Michael Slusarz <slusarz at horde.org>
 Summary            | Subject line encoding problem
 Queue              | IMP
 Version            | 4.1.5
 Type               | Bug
 State              | Assigned
 Priority           | 2. Medium
-Owners             | Michael Slusarz
+Owners             | Horde Developers, Michael Slusarz
-----------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2007-12-14 03:44) wrote:

This one is easy.  None of our MIME:: functions work with multibyte
characters.  And it may be difficult to fix this in PHP since we need a
multibyte character-aware regular expression engine, and mb_ereg() doesn't
seem to accept ISO-2022-JP as a valid charset - I get 'Warning:
mb_regex_encoding() [function.mb-regex-encoding]: Unknown encoding
"ISO-2022-JP"' errors.

It *is* possible to use mb_encode_mimeheader() to encode multibyte headers
properly, but mb_encode_mimeheader() is much much too greedy to use on
everyday, non multi-byte messages (it apparently will encoding everything,
even if the string is ASCII).  So this is a viable solution only if we can
restrict use of this function to multibyte charsets only.  is there an easy
way to determine if a charset is multibyte or not (without maintaing a
static list)?