6.0.0-alpha12
6/8/25

[#3765] subject with 8-bit characters, encoding is lost when replying
Summary subject with 8-bit characters, encoding is lost when replying
Queue Horde Framework Packages
Queue Version HEAD
Type Bug
State Resolved
Priority 1. Low
Owners
Requester leena.heino (at) uta (dot) fi
Created 04/13/2006 (6996 days ago)
Due
Updated 04/15/2006 (6994 days ago)
Assigned 04/13/2006 (6996 days ago)
Resolved 04/15/2006 (6994 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
04/15/2006 05:26:21 PM Michael Slusarz Version ⇒ HEAD
Queue ⇒ Horde Framework Packages
 
04/15/2006 05:26:04 PM Michael Slusarz Comment #9
State ⇒ Resolved
Reply to this comment
I've narroved this down to this setting of default_charset in
imp/lib/base.php:
Thanks - this was the key piece of information.  We did charset 
conversion in MIME_Headers::getOb() after we did MIME decoding, when 
the order should be reversed.  I wasn't seeing this in IMP HEAD since 
we no longer use the MIME_Headers:: version of getOb().



This has been fixed in HEAD and Horde 3.1.2.
04/15/2006 09:25:36 AM leena (dot) heino (at) uta (dot) fi Comment #8 Reply to this comment
I've narroved this down to this setting of default_charset in 
imp/lib/base.php:



// Set default message character set, if necessary

if (isset($prefs) && ($def_charset = $prefs->getValue('default_msg_charset')))

  {

     $GLOBALS['mime_structure']['default_charset'] = $def_charset;

     $GLOBALS['mime_headers']['default_charset'] = $def_charset;

}



If I remove this block, then 8-bit characters are shown correctly in 
Subject header in the reply message window.
04/14/2006 08:07:25 PM leena (dot) heino (at) uta (dot) fi Comment #7 Reply to this comment
Still don't see any problem with CVS FRAMEWORK_3 versions of
IMP/Horde.  Tested with a subject including the character "ö" that
was sent in both UTF-8 and ISO-8859-1.
Is there an preference setting that could interfere with this charset 
and multibyte regocnition in Imp or Horde?



Could this be somehow related to the charset information that browser 
is sending to Horde?



For me this situation is repeatable in IE and Firefox browsers with 
Imp running on Linux or Solaris OS. It does not matter if user is 
using english or finnish locale in Horde.
04/14/2006 07:41:22 PM Michael Slusarz Comment #6 Reply to this comment
Still don't see any problem with CVS FRAMEWORK_3 versions of 
IMP/Horde.  Tested with a subject including the character "ö" that was 
sent in both UTF-8 and ISO-8859-1.
04/13/2006 08:41:08 PM leena (dot) heino (at) uta (dot) fi Comment #5 Reply to this comment
Possibly a related issue to Bug #3746?
As far as I can understand it is not the same issue. It seems that 
charset are converted between iso-8859-1 and utf-8 either too many 
times or too few times. Somehow somewhere the multibyte charset 
recognition is not working and text with utf-8 charset is shown as if 
it were iso-8859-1.



This issue appeared after Imp release 4.1.0.


04/13/2006 07:14:29 PM Michael Slusarz Comment #4 Reply to this comment
Possibly a related issue to Bug #3746?
04/13/2006 04:33:03 PM leena (dot) heino (at) uta (dot) fi Comment #3 Reply to this comment
I can't reproduce this.  In the message you are replying to, is the
subject MIME encoded or are there bare 8-bit characters in the
Subject (which would mean it is a very broken message)?
Subject text in the original message is correctly MIME encoded. But 
when you open this message to compose windows eg. to reply then the 
subject text looks like it is converted from iso-8859-1 to utf-8 but 
then shown as if it still were in iso-8859-1charset.


04/13/2006 02:31:20 PM Michael Slusarz Comment #2
Summary ⇒ subject with 8-bit characters, encoding is lost when replying
State ⇒ Feedback
Reply to this comment
I can't reproduce this.  In the message you are replying to, is the 
subject MIME encoded or are there bare 8-bit characters in the Subject 
(which would mean it is a very broken message)?
04/13/2006 10:26:29 AM leena (dot) heino (at) uta (dot) fi Comment #1
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ subject with 8-bit characts, encoding is lost when replying
Queue ⇒ IMP
State ⇒ Unconfirmed
Reply to this comment
1. Compose message that has 8-bit characters in it's subject

2. reply to this message, and 8-bit characters in the Subject: seems 
to be in utf-8, but they are shown as though they were in iso-8859-1 
eg. letter 'ö' (one character)   is shown as 'ö' (two characters).


Saved Queries