[Tickets #7218] Re: PGP problem with charset UTF-8

bugs at horde.org bugs at horde.org
Tue Aug 19 06:01:05 UTC 2008


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

Ticket URL: http://bugs.horde.org/ticket/7218
------------------------------------------------------------------------------
  Ticket             | 7218
  Updated By         | horde at ashish.neomailbox.com
  Summary            | PGP problem with charset UTF-8
  Queue              | IMP
  Version            | 4.2.1-RC1
  Type               | Bug
  State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Horde Developers
------------------------------------------------------------------------------


horde at ashish.neomailbox.com (2008-08-19 02:01) wrote:

> You can simply fix this by making sure that your server supports
> UTF-8. Decoding should still work if it doesn't though.

How do I make sure Apache 1.3.29 supports UTF-8?

I tried AddDefaultCharset UTF-8 in the relevant VirtualHost section  
and it made no difference.

The comments in the code at the relevant point in  
lib/Horde/MIME/Contents.php refer to the browser's charset, not the  
server's:

         /* If this is a text/* part, AND the text is in a different character
          * set than the browser, convert to the current character set.
          * Additionally, if the browser does not support UTF-8, give the
          * user a link to open the part in a new window with the correct
          * character set. */
         $charset = $mime_part->getCharset();

I tried setting the default charset to UTF-8 in Firefox and that  
didn't make any difference either.

As of now, PGP messages coming in as text/plain parts with charset  
UTF-8 fail to trigger PGP decryption and only show this charset message.





More information about the bugs mailing list