Browse code

tmrec: more details about duration format for time recurrences

Daniel-Constantin Mierla authored on 01/09/2015 07:17:39
Showing 1 changed files
... ...
@@ -126,9 +126,14 @@ modparam("tmrec", "separator", ";")
126 126
 			For a recurring interval, the <quote>duration</quote> parameter MUST
127 127
 			be small enough such that subsequent intervals do not overlap. 
128 128
 			For non-recurring intervals, durations of any positive length are 
129
-			permitted.  Zero-length duration means <quote>forever</quote>. 
130
-			Negative-length durations are not allowed. See RFC 2445 for
131
-			the format of duration.
129
+			permitted. Zero-length duration means <quote>forever</quote>. 
130
+			Negative-length durations are not allowed.
131
+			</para>
132
+			<para>
133
+			See RFC 2445 for the format of duration. In short for common cases
134
+			when the duration doesn't exeed a data, it must start with PT
135
+			followed by the value for hours, minutes or seconds - e.g., a
136
+			duration of 8 hours must be written as PT8H.
132 137
 			</para>
133 138
 		</listitem>
134 139
 		<listitem>
... ...
@@ -253,7 +258,7 @@ modparam("tmrec", "separator", ";")
253 258
 		Next is an example of evaluating multiple Byxxx parameters.
254 259
 		</para>
255 260
 		<para>
256
-		startdate=<quote>20100101T093000</quote> duration=<quote>10H30M</quote>
261
+		startdate=<quote>20100101T093000</quote> duration=<quote>PT10H30M</quote>
257 262
 		frequency=<quote>yearly</quote> interval=<quote>4</quote> 
258 263
 		bymonth=<quote>3</quote> byday=<quote>SU</quote>
259 264
 		</para>