Use of the Olson database (Re: Basic rationale of the KEP #2 design)
bernhard at intevation.de
Thu Mar 3 10:56:31 CET 2011
Am Mittwoch, 2. März 2011 18:17:14 schrieb Joon Radley:
> > For us, the only big issue is to write a Olson Timezone to/from Outlook
> > (Windows) Timezone since we cannot depend on the name of the timezone to
> > translate to Windows, we have to resolve the timezone by looking for the
> > time zone string from the Olsen database and then we need to translate
> > the Olsen timezone information into Windows. Also reverse the process.
> > I'm not sure if that we will be able to cover 100% of the different
> > timezone data between the two different set of timezone data, but we can
> > come close.
> This is a MUST requirement. Since neither you or us can control this, no
> Outlook Kolab client can be KEP2 compliant or get certified.
Joon, my Outlook test showed that invitations with VTIMEZONE
are handled by Outlook (2007). This seems to indicate that Outlook is able
to deal with everything that VTIMEZONE could display. If it can be done by
invitations, it must be representable within the Outlook objects somewhere.
If this is the case, I'd say it should be sufficient for our purposes.
As for the Olson mapping database, KEP2 id=10864 says that we shall come up
with a mapping for systems that do not have this database. Being compliant
with this mapping would be enough for being compliant with KEP2.
Managing Director - Owner: www.intevation.net (Free Software Company)
Deputy Coordinator Germany: fsfe.org. Board member: www.kolabsys.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: This is a digitally signed message part.
More information about the format