| Summary | iTip reply to organizer containing extended characters |
| Queue | IMP |
| Queue Version | 4.2 |
| Type | Bug |
| State | No Feedback |
| Priority | 1. Low |
| Owners | Horde Developers (at) |
| Requester | patrick.abiven (at) apitech (dot) fr |
| Created | 05/28/2008 (6244 days ago) |
| Due | |
| Updated | 08/29/2008 (6151 days ago) |
| Assigned | 08/18/2008 (6162 days ago) |
| Resolved | 08/29/2008 (6151 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Feedback
Milestone ⇒
Assigned to
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ iTip reply to organizer containing extended characters
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
When an attendee accepts an invitation which name and description
contain extended characters (such as french accents), then the
organizer receives a message with incorrect characters.
A workaround is to utf8 encode the attributes of the vEvent_reply
message in imp/lib/MIME/Views/itip.php.
line 219:
if (!is_a($vEvent->getAttribute('SUMMARY'), 'PEAR_error')) {
- $vEvent_reply->setAttribute('SUMMARY', $vEvent->getAttribute('SUMMARY'));
+ $vEvent_reply->setAttribute('SUMMARY', String::convertCharset
($vEvent->getAttribute('SUMMARY'), NLS::getCharset(), 'utf-8') );
}
if (!is_a($vEvent->getAttribute('DESCRIPTION'), 'PEAR_error')) {
- $vEvent_reply->setAttribute('DESCRIPTION',
$vEvent->getAttribute('DESCRIPTION'));
+ $vEvent_reply->setAttribute('DESCRIPTION', String::convertCharset
($vEvent->getAttribute('DESCRIPTION'), NLS::getCharset(), 'utf-8') );
regards
Patrick