242060 - Who's to blame that several iCalendar objects in calendar file lead to problems sharing calendars with Apples iCal?

Status: RESOLVED DUPLICATE of bug 179985

(Calendar :: General, defect)

Description

[Jakob Fredriksson]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030802 Mozilla Sunbird/0.1

I have problems sharing my calendar file with my collegues using Apple
ical.

We found that Sunbird uses one (1) iCalender object for each diary
entry.  This seems correct (see rfc2445, sections 4.4 and 4.6 (last
paragraph before 4.6.1)), but doesn't cooperate well with apples
implementation of ical.  Apples implementation relies on a series of
components (see section 4.6.1) included in a single object.

Is the Sunbird implementation correct?
Is it apple that should be blamed?

This has been discussed at apple.com also:
http://discussions.info.apple.com/WebX?[e-mail].5@.68914f3f/12

The blame was put on apple...  but is this correct?


Reproducible: Always
Steps to Reproduce:
1.
2.
3.



Expected Results:  
Perhaps using just one iCalendar object encompassing all components.

Comment 1

[Jussi Kukkonen]

Blame Apple, the RFC clearly says both ways of saving events are ok.

Still, to me it looks like the patch in bug 179985 will take care of this...
That bug is about exporting events, but it looks like the patch changes the way
ical files are handled generally.

Comment 2

[Jakob Fredriksson]

*** This bug has been marked as a duplicate of 179985 ***

Comment 3

[Reed Loden [:reed]]

The bugspam monkeys have been set free and are feeding on Calendar :: General. Be afraid for your sanity!