Actually I have tracked down the problem yesterday as follows:
On RedHat 9, I always had problems with daylight savings time when using an internet time server, so I set both my phone and the computer to not use daylight savings time at all. Now I have Ubuntu, and it seems that Ubuntu automatically (and correctly) sets the daylight savings flag based on the current date. So my phone actually had the wrong setting. Now both my phone and computer use CEST (GMT+2) and this works fine.
I don't know why the shift only occured in one direction, though. This seems to be a bug. Maybe it would be a good thing to have a spec for OpenSync that says that VEvents always need to have correct timezone information attached (or always be in GMT or something), otherwise they are rejected? And a set of helper functions that converts VEvents between timezones? Would be a bit more work for plugin developers but at least the chance to "get it right" would be higher by default.
Markus
Paul Rensing schrieb:
I have noticed a similar problem with the Opie plugin, but I attribute the bug to Evo. When I sync a calendar event off my Zaurus into Evolution2, the appointment appears in the correct place in the GUI calendar display, but the alarm dialog pops up as if the appointment occurred in the GMT timezone.
See bugzilla report: http://bugzilla.gnome.org/show_bug.cgi?id=304278
Paul Rensing
On Tue, 2005-05-17 at 12:11 +0200, Armin Bauer wrote:
Markus Meyer wrote:
Armin Bauer schrieb:
Yes, gmt+1, without (!) daylight savings time. (Actually, currentlyMarkus Meyer wrote:
ahh ok. which timezone is this supposed to be in? gmt+1?Armin Bauer schrieb:
Could you show me the vcal object as it is sent from the device?
BEGIN:VEVENT UID:t1116318685c1 X-IRMC-LUID:3423995946 CATEGORIES:Memo SUMMARY:Abiball christoph DTSTART:20050618T210000 DTEND:20050619T000000 END:VEVENT END:VCALENDAR
should be daylight savings time, but I disabled that option on both the
phone and the computer, because I had problems with other programs that
didn't understand the daylight savings time)
hmm... thats very interesting. the vevent does not include the timezone information (by either including it in dtstart/dtend or as a separate entity) so evo2 probably uses the wrong default timezone (UTC?). But i dont really know how to fix this...
Markus
------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Multisync-users mailing list Multisync-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/multisync-users
