[Tickets #10148] Re: Incorrect message charset in replies with reply_headers

bugs at horde.org bugs at horde.org
Mon Feb 13 09:47:14 UTC 2012


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

Ticket URL: http://bugs.horde.org/ticket/10148
------------------------------------------------------------------------------
  Ticket             | 10148
  Updated By         | teplavoda at gmail.com
  Summary            | Incorrect message charset in replies with reply_headers
  Queue              | IMP
  Version            | Git master
  Type               | Bug
  State              | Resolved
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


teplavoda at gmail.com (2012-02-13 09:47) wrote:

I'd like to point out a situation where replying with the original  
message encoding breaks the message:

I've received an email encoded in ISO-8859-1. It looks good because it  
contains no accented characters (many people in my country write  
without accented characters because of various reasons).

I reply to this email using Horde. There are accented characters in my  
name and that means they should be both in my identity (From header in  
the message) and in my signature. These characters are sent as  
question marks and my message looks like my UA is broken (and that is  
truth in my opinion).

The other thing is I alwalys use accented characters because they are  
a part of my mother tongue. When I reply to a message in an encoding  
which doesn't support accented characters, my message will be  
unreadable by the recipient.

I think I'm not the only one willing to compose emails in my mother  
tongue and there should be a way to make it possible. I would prefer a  
configuration option to force all outgoing messages to UTF-8. I would  
have definitely enabled it in our installation if it was possible.

It's certainly truth that clients with broken UTF-8 support exist  
somewhere on the internet and they wouldn't be able to read our  
messages. But I prefer to inform my users and recipients of my  
messages that the problem lies on the receiving side and not in our  
webmail. With current Horde my users realize that replaying to an  
email with the same message text in e.g. Thunderbird works while in  
Horde it doesn't work.





More information about the bugs mailing list