On 19/06/15 16:06, Patrick Ohly wrote: > That DTSTART and DTEND then never gets parsed is a side effect of giving > up the parsing.
Wouldn't it be better to completely abort the processing and reject the object rather than generating a corrupted object when an error occurs? > So the fix is to remove mandatory="1" and adapt the total counts in > 11calendar-profile.xml for SUMMARY. You can do that locally by copying > the attached modified file to $HOME/.config/syncevolution-xml/datatypes That works, thanks (note to anyone else applying this: you may need to create the directory). This obviously isn't a big issue as no one else seems to have come across it! I saw it in 2 out of 2200 events in my calendar. Graham _______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
