1.1 --- a/TO_DO.txt Sat Jul 09 20:57:14 2011 +0200
1.2 +++ b/TO_DO.txt Sat Jul 09 22:26:01 2011 +0200
1.3 @@ -1,3 +1,32 @@
1.4 +Localised Keywords
1.5 +------------------
1.6 +
1.7 +It should be possible to define events using localised equivalents of "start",
1.8 +"end", "summary" and so on. To achieve this, the page language would be found
1.9 +and regular expressions built to use the localised keywords, falling back on
1.10 +the English keywords, would then search for event details.
1.11 +
1.12 +Recurring Events
1.13 +----------------
1.14 +
1.15 +Having events recur at certain intervals would potentially involve the
1.16 +expansion of events to produce multiple instances within a specified period of
1.17 +interest, and such expansion could occur after an event's details have been
1.18 +read. Care would need to be taken in cases where no limits are placed on a
1.19 +calendar: the expanded instances should not be allowed to recede into the past
1.20 +and future indefinitely; where no other events exist to provide implicit
1.21 +limits, some other default limits might be required to let the expansion
1.22 +occur.
1.23 +
1.24 +The description of recurring events could be based on the iCalendar
1.25 +specification, although simpler schemes could be preferable. Recurring event
1.26 +descriptions might start with "every" and then provide a time period ("day",
1.27 +"week", "month", "year") for offsets from a specified date or time, perhaps
1.28 +using qualifiers ("first", "second", "other", and so on), or instead provide a
1.29 +more complete description using additional qualifiers that may override any
1.30 +specified date or time for instances other than the primary occurrence. For
1.31 +example, "every second Wednesday of every other month".
1.32 +
1.33 Map Views
1.34 ---------
1.35