Sync-Engine : timezone conversions

[Aurelien Bompard]

Hello John,

I'm looking at a conversion problem in Sync-Engine : events set as "all day
long" on the device are synced to the computer with the wrong date.
What happens is that the start time on the device is the start day at
midnight, minus the timezone. When we convert it to opensync, we only keep
the date part and just strip the time part, resulting in the wrong day when
the timezone is positive.
I'm looking into that, and found that the ConvertASTimezoneToVcal function
in formats/tzconv.py is disabled (it returns immediatly). Any reason for
that ? Is the timezone conversion from airsync to opensync a work in
progress ? Can I help you with it ?

Thanks

Aurélien

[Mark Ellis]

Post by Aurelien Bompard
Hello John,
I'm looking at a conversion problem in Sync-Engine : events set as "all day
long" on the device are synced to the computer with the wrong date.
What happens is that the start time on the device is the start day at
midnight, minus the timezone. When we convert it to opensync, we only keep
the date part and just strip the time part, resulting in the wrong day when
the timezone is positive.
I'm looking into that, and found that the ConvertASTimezoneToVcal function
in formats/tzconv.py is disabled (it returns immediatly). Any reason for
that ? Is the timezone conversion from airsync to opensync a work in
progress ? Can I help you with it ?
Thanks
Aurélien

There are a couple of bug reports in sourceforge about this, I've never
got around to looking at it.

Can't comment on why the code is like it is, but if you can fix it
you'll be an absolute star !

Mark

[Dr J A Gow]

Post by Aurelien Bompard
Hello John,
I'm looking at a conversion problem in Sync-Engine : events set as "all day
long" on the device are synced to the computer with the wrong date.
What happens is that the start time on the device is the start day at
midnight, minus the timezone. When we convert it to opensync, we only keep
the date part and just strip the time part, resulting in the wrong day when
the timezone is positive.
I'm looking into that, and found that the ConvertASTimezoneToVcal function
in formats/tzconv.py is disabled (it returns immediatly). Any reason for
that ? Is the timezone conversion from airsync to opensync a work in
progress ? Can I help you with it ?

I'll need to go back and check why this was commented out: it could be
something I commented out during development and forgot to re-include
it. I don't remember there being a problem with this function as such.

By all means try including it again and see what happens - let me know
the result. I am currently working on the Opensync 0.4x stuff - which
version of Opensync are you running?


John.

[Aurelien Bompard]

Post by Dr J A Gow
I'll need to go back and check why this was commented out: it could be
something I commented out during development and forgot to re-include
it. I don't remember there being a problem with this function as such.
By all means try including it again and see what happens - let me know
the result.

Sure, will do.

Post by Dr J A Gow
I am currently working on the Opensync 0.4x stuff - which
version of Opensync are you running?

I'm still using 0.22. Good thing, we won't step on each other's feet then.


Aurélien