> On 19.06.2015, at 17:06, Patrick Ohly <[email protected]> wrote: > > [...] I inherited this "SUMMARY is mandatory" from the example configs in > libsynthesis; not sure what the rationale was at the time.
Oh, time for some tales from the old days ;-) The rationale was that entries without summary would get invisible in many calendar apps of that time. So the decision for the default config was to reject those. > [...] > As you noted, a fake summary gets synthesized if the field is missing, > probably because it is safer this way. So there is no need to declare > the field as "mandatory", because setting it to non-empty before > encoding will ensure that it gets generated when sending (should that be > required). That part was not present back then. I agree, if something gets generated into the summary in case it is parsed empty, the field does need to be mandatory at the VEVENT level any more. Lukas
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
