Tickets :: [#5050] When incoked from Imp's Message Composition window, Turba gets the character encoding wrong, under particular conditions

Summary	When incoked from Imp's Message Composition window, Turba gets the character encoding wrong, under particular conditions
Queue	IMP
Queue Version	4.1.4-RC1
Type	Bug
State	Resolved
Priority	2. Medium
Owners	Jan Schneider <jan (at) horde (dot) org>
Requester	Otto (dot) Stolz (at) uni-konstanz (dot) de
Created	02/28/2007 (586 days ago)
Due
Updated	02/28/2007 (586 days ago)
Assigned
Resolved	02/28/2007 (586 days ago)
Attachments	config.txt
Milestone
Patch	No

02/28/2007	Jan Schneider	Comment #3 State ⇒ Resolved Assigned to Jan Schneider	Reply to this comment
Fixed.

02/28/2007	Jan Schneider	Comment #2 Queue ⇒ IMP	Reply to this comment
It's an IMP bug.

02/28/2007	Otto (dot) Stolz (at) uni-konstanz (dot) de	Comment #1 State ⇒ Unconfirmed Type ⇒ Bug Priority ⇒ 2. Medium Summary ⇒ When incoked from Imp's Message Composition window, Turba gets the character encoding wrong, under particular conditions New Attachment: config.txt Queue ⇒ Turba	Reply to this comment
A test case in my LDAP directory has non-Latin characters in its cn field. If I invoke "Address Book" from Imp's Message Composition form, then in the Adress Book form choose "Display: Email Address", then retrieve that test case, the cn (Name) field is not properly encoded (apparently the UTF-8 bytes are interpreted as ISO 8859-1). The name is both wrongly displayed in the Address Book form (when I change the Display setting, afterwards) and wrongly inserted in the message's address fields. If I invoke the Address Book in the same way, but choose "Display: Name", before retrieving the test case, all is well. If I invoke "Expand Names" from Imp's Message Composition form, then the cn field of that test case is properly encoded; however, the quotes around the name (required by RFC 2822, § 3.4) are missing. Attached are pertinent excerpts from imp/config/servers.php and turba/config/sources.php.