Closed Bug 371133 Opened 19 years ago Closed 19 years ago

Extra linebreak in ics/webdav publishing removes SUMMARY in Apple iCal

Categories

(Calendar :: Provider: ICS/WebDAV, defect)

Lightning 0.3.1
PowerPC
macOS
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 324198

People

(Reporter: hoekstra, Unassigned)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-GB; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1 Build Identifier: Lightning 0.3.1 build 2007021405 The ics files created by lighting have an extra linebreak between the ID and SUMMARY content lines. This causes the Apple iCal ics import/subscription mechanism to interpret the linebreaks as '\n\n', which results in the ID field and SUMMARY field being concatenated. The effect for Apple iCal subscribers to Lightning-published calendars is that the VEVENTs don't have a title anymore. An example, Lightning created the following lines: UID: D31D4389-2F7D-48C1-98B7-F0D395D60037-1C81897E-88A5-41AA-A6A6-B69760851175 SUMMARY:Juridisch Kennismanagement Which are interpreted by Apple iCal as: UID:D31D4389-2F7D-48C1-98B7-F0D395D60037-1C81897E-88A5-41AA-A6A6-B697608 51175\n\nSUMMARY:Juridisch Kennismanagement Perhaps the way Apple iCal parses the ics file is not standards-compliant, but the extra line seems to be redundant, and can be left out. Reproducible: Always Steps to Reproduce: 1. Create a calendar using Lightning 2. Publish it to a WebDAV thingy 3. Subscribe to the calendar using Apple iCal Actual Results: The titles of the events in the created calendar do not show up in iCal. Having a look in the cache (e.g. in ~/Library/Application\ Support/iCal) shows the way iCal has parsed the calendar files Expected Results: Wel... show the titles of the events ;)
Version: unspecified → Lightning 0.3.1
Lightning doesn't create that kind of long UIDs itself. But it has some problems when reading and writing such UIDs from foreign source, see Bug 324198. Duplicate?
Whiteboard: [qa discussion needed]
Tested in iCal V. 2.0.4, this issue is indeed caused by the problem in bug 324198. Marking this as a dupe of 324198.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Whiteboard: [qa discussion needed]
You need to log in before you can comment on or make changes to this bug.