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 (at) horde (dot) org |
Requester | Otto.Stolz (at) uni-konstanz (dot) de |
Created | 02/28/2007 (6709 days ago) |
Due | |
Updated | 02/28/2007 (6709 days ago) |
Assigned | |
Resolved | 02/28/2007 (6709 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
Assigned to Jan Schneider
State ⇒ Resolved
Version ⇒ 4.1.4-RC1
Queue ⇒ IMP
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ When incoked from Imp's Message Composition window, Turba gets the character encoding wrong, under particular conditions
Queue ⇒ Turba
New Attachment: config.txt
State ⇒ Unconfirmed
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.