[Tickets #10054] Re: Subject didn't encode with attachment

[bugs at horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: http://bugs.horde.org/ticket/10054
------------------------------------------------------------------------------
  Ticket           | 10054
  Aktualisiert Von | bjoern.koester at mediata.net
  Zusammenfassung  | Subject didn't encode with attachment
  Warteschlange    | IMP
  Version          | 5.0.1
  Typ              | Bug
  Status           | Unconfirmed
  Priorität        | 2. Medium
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


wangshichen17 at gmail.com (2011-05-09 02:12) hat geschrieben:

I think that it is Big-5 that use double-8it to encode one Chinese  
word. Do you think that it is the reason caused this problem??
In fact, I have thought that it might be the problem of Big-5 charset.  
Therefore, i also tested for the UTF-8 charset.
Then, I found the same problem when using the UTF-8 charset.


> Is Big-5 one of those charsets that only contains ASCII characters,  
> even though it represents an 8+bit representation?  That would  
> explain this behavior.  See, e.g., Horde_mime::is8bit:
>
>         /* ISO-2022-JP is a 7bit charset, but it is an 8bit representation so
>          * it needs to be entirely encoded. */
>         return is_string($string) &&
>                ((stristr('iso-2022-jp', $charset) &&
>                 (strstr($string, "\x1b\$B"))) ||
>                 preg_match('/[\x80-\xff]/', $string));