|
54.
|
|
|
Event text
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]EVENT_TEXT
|
|
55.
|
|
|
The text that describes the actual event (for a system command, this is the actual PHP/OcCLE code or URL).
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]DESCRIPTION_EVENT_TEXT
|
|
56.
|
|
|
Daily
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]DAILY
|
|
57.
|
|
|
Weekly
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]WEEKLY
|
|
58.
|
|
|
Monthly
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]MONTHLY
|
|
59.
|
|
|
Yearly
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]YEARLY
|
|
60.
|
|
|
Recurrence
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]RECURRENCE
|
|
61.
|
|
|
The basis with which this event recurs (if it is not a one-off).
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]DESCRIPTION_RECURRENCE
|
|
62.
|
|
|
Recurrence pattern
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]RECURRENCE_PATTERN
|
|
63.
|
|
|
If non-blank, this adds extra control to the occurence. It allows you to provide on/off repeating patterns. For example, to make something recur on weekdays, enter <tt>1111100</tt> with daily recurrence if the event first starts on a Monday. For example, to make something occur every other day, enter <tt>10</tt> with daily recurrence. For example, if a farmer laid land fallow for one year in five, with the next fallow year in 2 years, he might choose a plowing event with yearly recurrence and pattern <tt>11011</tt> (assuming he creates the event just before his first occurence, giving him two plowing seasons before fallow).
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]DESCRIPTION_RECURRENCE_PATTERN
|