D7775: Initial submission of Akonadi EWS Resource to KDE PIM

Krzysztof Nowicki noreply at phabricator.kde.org
Sun Sep 17 10:35:55 BST 2017


nowicki added a comment.


  The KDateTime removal might be a bit more digging.
  
  The current calendar code downloads the calendar event from Exchange in form of a vCal event. While this is not ideal (the Exchange's vCal exporter is not perfect) it is good enough for a start. On the Akonadi EWS side I feed it to a memory calendar in order to get an event. Previously the importer just created a KDateTime and didn't attempt to parse the timezone (it was just provided as a name). This was fine when the timezone name was an IANA name as it was then parsed correctly. Unfortunately the Window$ world has it's own standards and the timezone names are often different (either MS timezone names of even some non-standard ones). These I need to attempt to parse.
  
  After the changes I get a QDateTime, which has an already parsed QTimeZone. I assume the parsing is done in KCalCore. The question is what happens when it occurs some non-IANA timezone name.
  
  I'll need to dig into the code a bit more.

REPOSITORY
  R44 KDE PIM Runtime

REVISION DETAIL
  https://phabricator.kde.org/D7775

To: nowicki, #kde_pim, dvratil, mlaurent
Cc: kde-pim, dvasin, winterz, vkrause, mlaurent, knauss, dvratil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20170917/62ffcfb9/attachment.html>


More information about the kde-pim mailing list