| Summary: | Invitation received from Microsoft Exchange Server 2010 not recorded in Google calendar | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] libkgapi | Reporter: | Martin van Es <bugs> |
| Component: | General | Assignee: | Daniel Vrátil <dvratil> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/akonadi-google/1aa962fde79a779e014ca3e5819c56ee4a3d556d | Version Fixed In: | 2.0.2 |
| Sentry Crash Report: | |||
|
Description
Martin van Es
2013-06-21 12:09:22 UTC
I'm almost sure this is caused by the obscure time zone name (TZID) that Exchange uses. Usually we are able to map the timezones thanks to X-MICROSOFT-CDO-TZID parameter, but it's missing here and Google does not accept these (we could theoretically strip the timezone and save the event with a wrong timezone to Google, which is not a good solution, but still better than not saving the event at all) Do you have access to the web interface for the Exchange Server? It would be very useful if I could get list of all the timezone names they use so that I could create an artificial mapping to Olson format, which is accepted by Google. I don't have access to this server, I'm only invited by them. On the other hand, I don't see a X-MICROSOFT-CDO-TZID in my invitation, but I assume you know what you're talking about? Isn't there any documentation about what timezones M$ uses in Exchange? (In reply to comment #2) > On the other hand, I don't see a X-MICROSOFT-CDO-TZID in my invitation, but I assume you > know what you're talking about? Missing X-MICROSOFT-CDO-TZID is exactly the reason why LibKGAPI failed to convert the time zone in TZID into some reasonable format that would be accepted by Google. > Isn't there any documentation about what timezones M$ uses in Exchange? I managed to Google this: http://support.microsoft.com/kb/973627 which seems to provide exactly that kind of mapping we need. This also makes it clear why there's not X-MICROSOFT-CDO-TZID parameter - this is not a CDO timezone (it would be too simple if Microsoft had only one internal and incompatible timezones format, right? :D ) Git commit 1aa962fde79a779e014ca3e5819c56ee4a3d556d by Dan Vrátil. Committed on 24/06/2013 at 21:25. Pushed by dvratil into branch 'LibKGAPI/2.0'. Add support for Microsoft Standard Time Zones Because one incompatible timezone format would be to simple, Microsoft has invented yet another one. Some invitations generated by Exchange 2010 (and maybe others) use "X Y Standard Time" as a TZID string. This commit adds mapping between these strings and Olzon timezones that are accepted by Google Calendar API FIXED-IN: 2.0.2 M +122 -11 libkgapi2/calendar/calendarservice.cpp http://commits.kde.org/akonadi-google/1aa962fde79a779e014ca3e5819c56ee4a3d556d Wow thx! That's quick. Will this fix trickle down via standard KDE minor updates in Ubuntu packages? Currently I can only see 0.4.4 in Lunchpad (I'm not an Ubuntu user), current stable is 2.0.1. 2.0.2 with this fix will be out in about month or so when I collect few more bugfixes (unless something supercritical appears). You can nag libkgapi maintainer in Ubuntu to update to 2.0.1 and backport the patch or build LibKGAPI yourself from git. Note that kdepim-runtime must be rebuilt as well due to ABI break between 0.4.x and 2.0.x. Solved by upgrading to Kubuntu 14.04 |