Version: (using KDE KDE 3.3.92) Installed from: Gentoo Packages Compiler: gcc version 3.4.3-20050110 (Gentoo Linux 3.4.3.20050110, ssp-3.4.3.20050110-0, pie-8.7.7) OS: Linux importing vcal files fails if "VERSION:1.0" is missing. it is maybe not a bug because according to the vcal definition it is a mandatory property. nevertheless i think there should be a more failsafe behaviour for importing files. thank you, daniel
there is another problem in case the (optional!) UID field is missing in the import file. when you add the imported file as a new calendar, and then hide and re-show the resource of that calendar, every time you do this an additional instance of its events is shown (of that resource) is this worth an own bug report? regards
On Monday 28 February 2005 13:00, Daniel Reichhard wrote: > is this worth an own bug report? Yes, definitly. The events should not be duplicated... > ------- there is another problem in case the (optional!) UID field is > missing in the import file. yeah, it's optional per vCalendar spec, but the spec also says: Calendaring applications that do not generate this property in vCalendar entities may be limiting their interoperability with other group scheduling applications. In particular, group scheduling with these events will never work, because each time the vCalendar file is loaded, a randon uid will be assigned to these events, and these uids (by which the events are identified) will not be the same when you load such an event again. Still, the events should not be duplicated . Reinhold
Actually, the duplication happens for all VTODOs, regardless of whether there is a UID or not. If there is no UID, also events are duplicated. For loading, we first try to load it as iCalendar (VERSION:2.0), and if that fails as vCalendar (VERSION:1.0). I agree that korganizer should at least try to load such broken files. Cheers, Reinhold
I thought a bit more on the missing VERSION line, and we can't try to load files without such a version string. The reason is that iCalendar (V 2.0) and vCalendar (V 1.0) have the same structure, but some fields are named and interpreted differently. So, if we simply try to load a file without VERSION: x.x, we don't know if the entries are interpreted as iCalendar or vCalendar. You *can* load an iCalendar file as vCalendar and vice versa, but the events will look broken to the user (but not the computer)! So we can't ignore a missing version line (the vCalendar and iCalendar specs are pretty clear that these lines are absolutely mandatory!). Cheers, Reinhold
Reassigning all KOrganizer bug reports and wishes to the newly created korganizer-devel mailing list.
At this point, if the VERSION line is needed for the importing, shouldn't this report be closed?
yes, I'm closing.