From 128d45bf1c7f9b2b01009f9a8f87862aaaf934c0 Mon Sep 17 00:00:00 2001 From: Tobias Schlemmer Date: Tue, 26 Jun 2018 10:05:41 +0200 Subject: [PATCH 2/2] Add support for the iCalendar CLASS property * doc/org-manual.org (iCalendar export): Document the CLASS tag TINYCHANGE --- doc/org-manual.org | 30 +++++++++++++++++++++--------- 1 file changed, 21 insertions(+), 9 deletions(-) diff --git a/doc/org-manual.org b/doc/org-manual.org index ee25fc78b..68da3adff 100644 --- a/doc/org-manual.org +++ b/doc/org-manual.org @@ -15029,18 +15029,20 @@ connections. #+cindex: @samp{DESCRIPTION}, property #+cindex: @samp{LOCATION}, property #+cindex: @samp{TIMEZONE}, property +#+cindex: @samp{CLASS}, property The iCalendar export back-end includes =SUMMARY=, =DESCRIPTION=, -=LOCATION= and =TIMEZONE= properties from the Org entries when -exporting. To force the back-end to inherit the =LOCATION= and -=TIMEZONE= properties, configure the ~org-use-property-inheritance~ -variable. +=LOCATION=, =TIMEZONE= and =CLASS= properties from the Org entries +when exporting. To force the back-end to inherit the =LOCATION=, +=TIMEZONE= and =CLASS= properties, configure the +~org-use-property-inheritance~ variable. #+vindex: org-icalendar-include-body -When Org entries do not have =SUMMARY=, =DESCRIPTION= and =LOCATION= -properties, the iCalendar export back-end derives the summary from the -headline, and derives the description from the body of the Org item. -The ~org-icalendar-include-body~ variable limits the maximum number of -characters of the content are turned into its description. +When Org entries do not have =SUMMARY=, =DESCRIPTION=, =LOCATION= and +=CLASS= properties, the iCalendar export back-end derives the summary +from the headline, and derives the description from the body of the +Org item. The ~org-icalendar-include-body~ variable limits the +maximum number of characters of the content are turned into its +description. The =TIMEZONE= property can be used to specify a per-entry time zone, and is applied to any entry with timestamp information. Time zones @@ -15048,6 +15050,16 @@ should be specified as per the IANA time zone database format, e.g., =Asia/Almaty=. Alternately, the property value can be =UTC=, to force UTC time for this entry only. +The =CLASS= property can be used to specify a per-entry visibility +class or access restrictions, and is applied to any entry with class +information. The iCalendar standard defines three visibility classes: +- PUBLIC :: The entry is publicly visible (this is the default). +- CONFIDENTIAL :: Only a limited group of clients get access to the + event. +- PRIVATE :: The entry can be retrieved only by its owner. +The server should treat unknown class +properties the same as PRIVATE. + Exporting to iCalendar format depends in large part on the capabilities of the destination application. Some are more lenient than others. Consult the Org mode FAQ for advice on specific -- 2.18.0.rc2