datebook and timezone issues

[wylbur]

I\'m using a SL-5600 (with a sharp kernel and the zynergy initrd). I\'ve set the timezone in the date/time. However, no calendar app seems to respect the zone. I\'ve used kopi and tkccalendar and opie-datebook (with the OZ rom), and they all take my calendar data (either by import [kopi] or via multisync) from ximian evolution. However, the resulting appointments are all at UTC, not at PDT (GMT-7) where I live.

Yes, I\'ve set all the timezone options in the calendars, to no avail. Further info:

-- I\'ve hacked kopi\'s mycalendar.ics to insert a

X-WR-TIMEZONE
 :America/Los Angeles

note at the top. No change.

-- I\'ve hacked the datebook.xml entries to add a timezone=\"America/Los Angeles\" attribute to each entry. No change.

-- kopi\'s current time status line shows that kopi thinks that the current time is GMT, so it\'s picking up the machine time and not translating for timezone.

-- however, the sharp system time (and the opie system time) apps, and the clock applet, understand the timezone translation.

ideas? TIA -- wylbur.

[zautrix]

You have to set the TZ environment variable.
E.g. you can set the timezone from UTC to CET by typing in the console:
export TZ=Europe/Paris

Then the new timezone is valid for all apps started from the console.
To set the timezone globally, you have to set the TZ somewhere in the boot process.

But I am not sure, if this helps, what I am writing ...

[wylbur]

thanks, zaurix. I\'ve set the TZ variable and launched kopi from the command line. No change -- the appointments stubbornly stick to GMT. Ditto for tkcCalendar (I don\'t have opie or sharp datebook currently loaded, but they\'ve been doing the same thing).

so I went to rc.local and wrote

Code: [Select]

export TZ="America/Los Angeles". I symlinked rc[01345].d/S90local to rc.local, and rebooted.  $TZ is still empty, though, and there\'s no change in the TZ problem.

am I doing something obviously wrong? TIA -- wylbur

[wylbur]

I switched to the initrd.bin-tkrom2.0alpha3-sl5600 and the problem just went away. And yep, the TZ environment variable is set now. That was probably the problem. thanks -- wylbur.