| 1 |
System timezones |
|---|
| 2 |
|
|---|
| 3 |
Download, build and run vciz |
|---|
| 4 |
|
|---|
| 5 |
*********** More instructions for that |
|---|
| 6 |
|
|---|
| 7 |
|
|---|
| 8 |
Use the tzconvert target to convert the generated timezone info into input for |
|---|
| 9 |
bedework. |
|---|
| 10 |
|
|---|
| 11 |
Use a properties file looking like: |
|---|
| 12 |
|
|---|
| 13 |
# bedework.timezones.properties |
|---|
| 14 |
|
|---|
| 15 |
org.bedework.timezones.arg.debug=-debug |
|---|
| 16 |
org.bedework.timezones.arg.dumpfile=/home/douglm/data/bwtimezones.xml |
|---|
| 17 |
org.bedework.timezones.arg.dir=/home/douglm/drop2/calendar/timezone/vzic/vzic-1.2/zoneinfo |
|---|
| 18 |
|
|---|
| 19 |
|
|---|
| 20 |
Upload the generated data with the admin client |
|---|
| 21 |
|
|---|
| 22 |
|
|---|
| 23 |
How they work. |
|---|
| 24 |
|
|---|
| 25 |
We have two levels of timezone information, the system level and the user level. |
|---|
| 26 |
|
|---|
| 27 |
System timezones are those installed by the above process. |
|---|
| 28 |
|
|---|
| 29 |
User timezones are timezones harvested from events as they are imported into the |
|---|
| 30 |
users calendar(s). They also appear there as the result of exporting icalendar |
|---|
| 31 |
format events from shared calendars. |
|---|
| 32 |
|
|---|
| 33 |
For the simple case of non-shared events the process is: |
|---|
| 34 |
|
|---|
| 35 |
On import (or incoming from caldav) if the event refers to a timezone id we look |
|---|
| 36 |
up the id in the repository. This first checks the user timezones and if not |
|---|
| 37 |
found there tries the system timezones. |
|---|
| 38 |
|
|---|
| 39 |
If it's not found and there is a timezone contained in the vcalendar object, we |
|---|
| 40 |
add the timezone to the user repository. |
|---|
| 41 |
|
|---|
| 42 |
On export of an event, we first check to start and end dates. If there is a |
|---|
| 43 |
tzid, we look it up and add the timezone information to the vcalendar object. |
|---|
| 44 |
|
|---|
| 45 |
The minor complication on this lookup is that we supply the owner of the event to |
|---|
| 46 |
the lookup and check that users repository rather than the current users. |
|---|
| 47 |
|
|---|
| 48 |
If the timezone is found we add it to the current users repository. |
|---|
| 49 |
|
|---|
