[sync] Sync experience HP2410 with Sync4j client again.

[Chuck Hagenbuch]

Quoting Han Spruyt <han.spruyt at ijsselgroep.nl>:

> date('O') accepts a time stamp as a second argument.
> When I change date('O') in lines 917 and 918 in _exportDateTime() to
> date('O', $value) then offset is correctly calculated for the passed
> date.

Okay, try what I committed? Other folks, does this work for you?  
Should it be merged?

> Then the syncing is correct, except in case I create an event in the
> pda for a date where DST is in effect. This event ends up in Kronolith
> one hour late.
>
> I tracked this down to funny behavior of the Sync4j client (I use
> 1.7.9). The times Horde receives from the client are always event
> times minus time zone offset. So DST is not taken in account. I only
> tested this for the time zone I am in (GMT+1).
>
> I guess this is Sync4j only behavior, so that should be taken care of
> in Sync4j.php, then.

Can you create a ticket so this doesn't get lost? http://bugs.horde.org/

-chuck

-- 
"we are plastered to the windshield of the bus that is time." - Chris