Tickets :: [#3675] removed attachment replacement text is using wrong charset information

6.0.0-beta1

8/8/25

Summary	removed attachment replacement text is using wrong charset information
Queue	IMP
Queue Version	HEAD
Type	Bug
State	Resolved
Priority	2. Medium
Owners	jan (at) horde (dot) org, slusarz (at) horde (dot) org
Requester	leena.heino (at) uta (dot) fi
Created	03/23/2006 (7078 days ago)
Due
Updated	04/13/2006 (7057 days ago)
Assigned	03/23/2006 (7078 days ago)
Resolved	04/12/2006 (7058 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

04/13/2006 10:39:02 AM	leena (dot) heino (at) uta (dot) fi	Comment #8	Reply to this comment
No further feedback, I guess that fixed it. This bug is fixed, charset used and encoding information in the mime part is as it should be.

04/12/2006 10:50:37 PM	Jan Schneider	Comment #7 State ⇒ Resolved	Reply to this comment
No further feedback, I guess that fixed it.

03/28/2006 05:36:08 PM	Michael Slusarz	Comment #6 Priority ⇒ 2. Medium Version ⇒ HEAD	Reply to this comment
Take 2 - just committed another change so see if that fixes things.

03/24/2006 03:55:07 PM	Jan Schneider	Comment #5	Reply to this comment
Jan, is this right? No, it isn't. NLS::getCharset() always returns the charset that is used for the gettext messages.

03/24/2006 03:31:52 PM	Michael Slusarz	Assigned to Jan Schneider

03/24/2006 03:31:34 PM	Michael Slusarz	Comment #4	Reply to this comment
Does this fix the problem? http://lists.horde.org/archives/cvs/Week-of-Mon-20060320/056140.html Almost, now the text in the text/plain attachment is in charset utf-8, but charset information in mime headers is iso-8859-1. Then this is probably a question for Jan. I am using NLS::getCharset(true) as the charset of the part which (I think from the documentation, at least) will return the character set of the localized text from gettext. Therefore if NLS::getCharset(true) is returning 'iso-8859-1' instead of 'UTF-8', there might be a problem with your locale's entry in config/nls.php. Jan, is this right?

03/24/2006 03:01:06 PM	leena (dot) heino (at) uta (dot) fi	Comment #3	Reply to this comment
Does this fix the problem? http://lists.horde.org/archives/cvs/Week-of-Mon-20060320/056140.html Almost, now the text in the text/plain attachment is in charset utf-8, but charset information in mime headers is iso-8859-1.

03/23/2006 11:18:34 PM	Michael Slusarz	Comment #2 Summary ⇒ removed attachment replacement text is using wrong charset information State ⇒ Feedback	Reply to this comment
Does this fix the problem? http://lists.horde.org/archives/cvs/Week-of-Mon-20060320/056140.html

03/23/2006 05:48:18 PM	Chuck Hagenbuch	Assigned to Michael Slusarz State ⇒ Assigned

03/23/2006 11:00:47 AM	leena (dot) heino (at) uta (dot) fi	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ removed attachment replacement text is using wron charset information Queue ⇒ IMP State ⇒ Unconfirmed	Reply to this comment
When attachent is removed from the message then the attachment is replaced with a text/plain attachment that has informational message about original attachment. Problem is that this informational message attachment is writen with language the user has chosen to use, but the charset information is wrong. Imp always adds the informational message attachment with charset us-ascii. This unfortunately means that text in the message might be shown as gibberish if the localized informational message contains any 8-bit characters.