Tickets :: [#2790] Depending on character enconding, the subject header is left unencoded

6.0.0-beta1

7/23/25

Summary	Depending on character enconding, the subject header is left unencoded
Queue	IMP
Queue Version	RELENG_3
Type	Bug
State	Not A Bug
Priority	1. Low
Owners
Requester	leena.heino (at) uta (dot) fi
Created	10/15/2005 (7221 days ago)
Due
Updated	10/25/2005 (7211 days ago)
Assigned
Resolved	10/17/2005 (7219 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

10/25/2005 12:40:06 PM	Jan Schneider	Comment #5	Reply to this comment
Please create a new ticket in the correct queue/version with enough details and examples and a clear description of what is happening.

10/17/2005 12:09:21 PM	leena (dot) heino (at) uta (dot) fi	Comment #4	Reply to this comment
You can't select the charset in the RELENG_3 branch. My mistake. I should have chosen FRAMEWORK_3 branch. This bug has something to do with String::convertCharset. It Seems that it fails to convert string's charset and therefore should return the original string. Unfortunately it seems to return the original string with all the 8-bit characters converted to ?.

10/17/2005 11:03:26 AM	leena (dot) heino (at) uta (dot) fi	Comment #3	Reply to this comment
You can't select the charset in the RELENG_3 branch. My mistake. I should have chosen FRAMEWORK_3 branch.

10/17/2005 10:41:45 AM	Jan Schneider	Comment #2 State ⇒ Not A Bug	Reply to this comment
You can't select the charset in the RELENG_3 branch.

10/15/2005 01:16:41 PM	leena (dot) heino (at) uta (dot) fi	Comment #1 State ⇒ Unconfirmed Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Depending on character enconding, the subject header is left unencoded Queue ⇒ IMP	Reply to this comment
If in the compose window user chooses character encoding that is not UTF8 or ISO-8859-* then the subject header is left unencoded and any 8-bit characters in the header are replaced with ?-characters.