1 Preferences and Settings
2 ========================
3
4 LANG
5 ----
6
7 Default: en (English)
8 Alternatives: (any recognised and supported locale)
9
10 The language for messages and user interface text.
11
12 TZID
13 ----
14
15 Default: system timezone (see /etc/timezone)
16 Alternatives: (any recognised Olson time zone identifier)
17
18 The default time zone/regime for calendars, new events and local times.
19
20 event_refreshing
21 ----------------
22
23 Default: never
24 Alternative: always
25
26 Indicate whether messages requesting a refresh of event details shall be
27 handled automatically. If not, such messages will be passed on to the
28 recipient for their mail program to handle.
29
30 freebusy_bundling
31 -----------------
32
33 Default: never
34 Alternative: always
35
36 Indicate whether to bundle free/busy details with other payloads such as
37 event and free/busy objects.
38
39 freebusy_messages
40 -----------------
41
42 Default: none
43 Alternative: notify
44
45 Indicate whether recipients are notified about received free/busy payloads.
46
47 freebusy_sharing
48 ----------------
49
50 Default: no
51 Alternative: share
52
53 Share free/busy details generally:
54
55 * bundling in e-mail messages if bundling is configured
56 * responding to free/busy requests via e-mail
57 * publishing as Web resources if a static Web resource is configured
58
59 incoming
60 --------
61
62 Default: summary-wraps-message
63 Alternatives: (see below)
64
65 Define how incoming event messages are delivered to recipients:
66
67 message-only deliver only the incoming message as it was received
68
69 message-then-summary deliver the message first followed by a summary
70 message
71
72 summary-then-message deliver a summary first followed by the message
73
74 summary-only deliver only a summary of the message
75
76 summary-wraps-message deliver a summary that includes the original message
77 as an attachment
78
79 organiser_replacement
80 ---------------------
81
82 Default: attendee
83 Alternatives: (see below)
84
85 Indicate whether the organiser of an event can be replaced and the nature of
86 any replacement:
87
88 any any identity, regardless of whether it is already
89 present or even previously unknown, may become the
90 organiser
91
92 attendee any new organiser must be a previously-recognised
93 attendee
94
95 never forbid the replacement of an event's organiser
96
97 participating
98 -------------
99
100 Default: participate
101 Alternative: no
102
103 Indicate whether a recipient participates in the calendar system. Note that
104 participation by default occurs because the handler programs will be defined
105 in the mail system for recipients fulfilling certain criteria; other
106 recipients will be handled in other ways. Thus, initial non-participation must
107 be defined by initialising this setting to "no" for all eligible users, if
108 this is the general policy on initial calendar system participation.
109
110 permitted_times
111 ---------------
112
113 Default: (none)
114 Alternatives: (see below)
115
116 Define the time values at which events can be scheduled. In its simplest form,
117 this indicates the resolution of a calendar for a participant supporting this
118 setting, with the given minute values being those allowed for the start and
119 end of an event. This setting requires a value of one of the following forms:
120
121 <minute values>
122 <hour values>:<minute values>
123 <hour values>:<minute values>:<second values>
124
125 Each list of values is a comma-separated collection of permissible values for
126 the unit of time being constrained. Any unspecified list is taken to permit
127 all normally permissible values for that unit of time. For example:
128
129 0,15,30,45 every 15 minutes from the start of each hour
130 10,12,14,16:0,20,40 every 20 minutes from 10:00 until 16:40 inclusive
131 12::0,30 every 30 seconds from the start of each minute during
132 the period from 12:00:00 until 12:59:30 inclusive
133
134 The purpose of this setting is not necessarily to impose availability
135 constraints but instead to impose a "grid" to which event start and end points
136 shall be "locked".
137
138 The values are interpreted in the local time of the participant. Thus, a time
139 represented in UTC may have apparently inappropriate hour (and for some zones)
140 minute values that correspond to permitted values in this participant's own
141 time zone.