Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calendar Properties should be prior to any calendar component #94

Closed
Unrud opened this issue Sep 5, 2017 · 0 comments · Fixed by #98
Closed

Calendar Properties should be prior to any calendar component #94

Unrud opened this issue Sep 5, 2017 · 0 comments · Fixed by #98
Assignees
Milestone

Comments

@Unrud
Copy link
Contributor

Unrud commented Sep 5, 2017

From https://tools.ietf.org/html/rfc5545#section-3.7:

   They SHOULD be specified after the "BEGIN:VCALENDAR"
   delimiter string and prior to any calendar component.

Unfortunately Outlook seems to ignore properties that are specified after components: Kozea/Radicale#697 (comment)

Test

import vobject
s="""\
BEGIN:VCALENDAR
X-WR-CALNAME:test
BEGIN:VEVENT
END:VEVENT
END:VCALENDAR
"""
print(vobject.readOne(s).serialize())

Result:

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//PYVOBJECT//NONSGML Version 1//EN
BEGIN:VEVENT
UID:20170905T152211Z - 65144@laptop
DTSTAMP:20170905T152211Z
END:VEVENT
X-WR-CALNAME:test
END:VCALENDAR

The calendar property X-WR-CALNAME is specified after the calendar component VEVENT.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants