Closed
Bug 356397
Opened 19 years ago
Closed 19 years ago
ICS Import fails with CAL_UTF8_DECODING_FAILED when importing an event that contains a UK Pound (£) symbol
Categories
(Calendar :: Import and Export, defect)
Calendar
Import and Export
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 334657
People
(Reporter: keith_is_back_2004, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7
The following event is an example of this error:
BEGIN:VCALENDAR
PRODID:-//Randy L Pearson//NONSGML Outlook2vCal V1.1//EN
VERSION:2.0
BEGIN:VEVENT
CREATED:20040829T163323
UID:00000000EBFAC68C9B92BF119D643623FBD17E1424312000
SEQUENCE:1
LAST-MODIFIED:20060615T231158
DTSTAMP:20040829T163323
ORGANIZER:Unknown
DTSTART:20011004T141500
DESCRIPTION:Please bring £1
CLASS:PUBLIC
LOCATION:Church
CATEGORIES:Church Events
SUMMARY:Test Event
PRIORITY:1
DTEND:20011004T141500
RRULE:FREQ=MONTHLY;INTERVAL=1;BYDAY=1SU,3SU,5SU
END:VEVENT
END:VCALENDAR
Reproducible: Always
Steps to Reproduce:
1. Save the above event to a file (UTF-8 encoded).
2. Import to a calendar or connect remotely using WebDav and file:///
Actual Results:
Pop-up box appears with the text...
"There has been an error reading data for calendar: Test Event. It has been placed in read-only mode, since changes to this calendar will likely result in data-loss. You may change this setting by choosing 'Edit Calendar'.
Error Number: CAL_UTF8_DECODING_FAILED
Description: An error occured while decoding an iCalendar (ics) file as UTF-8. Check that the file, including symbols and accented letters, is encoded using the UTF-8 character encoding."
Expected Results:
The event should import without error, and the description field of the event should read "Please bring £1"
Tested on linux with Sunbird 0.3a2 and WinXP with Sunbird 0.2.
Comment 1•19 years ago
|
||
Bug 334657, bug 338415 and bug 173039 cover this problem (ICS files being not entirely encoded in UTF-8 as required in the RFC and appropriate error handling).
Comment 2•19 years ago
|
||
*** This bug has been marked as a duplicate of 334657 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
OS: Windows XP → All
Hardware: PC → All
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•