Browse code

tmrec: readme regenerated

Daniel-Constantin Mierla authored on 17/12/2015 09:24:08
Showing 1 changed files
... ...
@@ -146,7 +146,11 @@ modparam("tmrec", "separator", ";")
146 146
        subsequent intervals do not overlap. For non-recurring intervals,
147 147
        durations of any positive length are permitted. Zero-length
148 148
        duration means "forever". Negative-length durations are not
149
-       allowed. See RFC 2445 for the format of duration.
149
+       allowed.
150
+       See RFC 2445 for the format of duration. In short for common cases
151
+       when the duration doesn't exeed a data, it must start with PT
152
+       followed by the value for hours, minutes or seconds - e.g., a
153
+       duration of 8 hours must be written as PT8H.
150 154
      * frequency - can be one of the following values: "daily" - specify
151 155
        repeating periods based on an interval of a day or more; "weekly" -
152 156
        specify repeating periods based on an interval of a week or more;
... ...
@@ -216,7 +220,7 @@ modparam("tmrec", "separator", ";")
216 220
 
217 221
    Next is an example of evaluating multiple Byxxx parameters.
218 222
 
219
-   startdate="20100101T093000" duration="10H30M" frequency="yearly"
223
+   startdate="20100101T093000" duration="PT10H30M" frequency="yearly"
220 224
    interval="4" bymonth="3" byday="SU"
221 225
 
222 226
    First, the interval="4" would be applied to frequency="yearly" to match