Re: wrong interpretation of timezone information

Hi Patrick,

On May 10, 2010, at 9:04 , Patrick Ohly wrote:

> Confirmed, works for me.

Thanks!

> I should have mentioned that I had already made similar changes as you
> on the moblin.org master branch (check for NULL obj in debug macros,
> enable debug logging inside vtimezone code when invoked by mimedir
> profile parser).
> 
> My own debug logging patches go a bit further:
> - log an error when parsing a VTIMEZONE fails
> - logging of libical timezone conversion
> - logging of timezone matching
> 
> I'm trying to track down an unexpected timezone failure with this which
> occurs when normal Evolution events are involved.
> 
> Do you agree with these changes? Would you mind merging them? I rebased
> them on your "luz" branch.

The attempt to init the time zones after reading config (fc000b0f45 (TSyncAppBase: moved system time zone
parsing after config reading)) creates a chicken and egg problem. The config reading process relies
itself on the time zone stuff being initialized, most prominently for <definetimezone>, but also for
other tags that have ISO8601 timestamp values.

Maybe the dilemma can be solved by adding an optional, second initialize run after config reading that can
be switched on specifically to track down timezone init problems. Another option would be to use the
ConferrPuts() channel, which is ready before config is read by definition.

Best Regards,

Lukas Zeller (luz@...)
- 
Synthesis AG, SyncML Solutions  & Sustainable Software Concepts
info@..., http://www.synthesis.ch