[Vobject] no TZ info in parsed dates?

[Jeffrey Harris]

Great find!

The mechanism to make vobject understand those tzids, then, is to  
first map the relevant olson tzids to tzinfo classes; I've used pyicu  
for this, myself, but vobject is agnostic as to how you do this.

Next, there's a vobject dictionary mapping tzids to tzinfo classes,  
when vobject finds a vtimezone it uses dateutil's vtimezone->tzinfo  
code and fills in that dictionary. You can do this manually.

It would be great if you wanted to contribute your code for this back  
(with whatever olson->tzinfo library you want to use), I'm sure you're  
not the only one with this problem.

Jeffrey

On Jun 9, 2009, at 1:54 PM, Bill Janssen <janssen at parc.com> wrote:

> Bill Janssen <janssen at parc.com> wrote:
>
>> Well, I'll see if I can cobble together something; looks like you  
>> have
>> all the machinery in either vobject or dateutil to do it.  It would  
>> be
>> nice to have a package system for enabling these kinds of things (I'm
>> sure there are others), something like
>> "vobject.enable_outlook_invalid_tzid_handling()" that I could call  
>> when
>> initializing my code.
>
> The mapping from Windows tz names to Olson tz names is available from
> the Unicode Consortium at
> http://unicode.org/cldr/data/diff/supplemental/windows_tzid.html.
>
> Bill
>
>