Mark Ellis
2009-01-28 10:50:21 UTC
-------- Forwarded Message --------
Tried this myself using confidential, airsync entry is
<Sensitivity
xmlns="http://synce.org/formats/airsync_wm5/calendar">3</Sensitivity>
resulting vcal has no Class element.
In event-from-airsync.xsl, the lookup for Sensitivity is conspicuously
missing missing a C: namespace designation, and so I guess never runs.
Any idea if this is deliberate or accidental, or any bad repercussions
from putting it in ?
Ta
Mark
Subject: [synce - Help] RE: Sensitivity on Messages is mapped wrongly!
Date: Tue, 27 Jan 2009 23:35:53 +0100
https://sourceforge.net/forum/message.php?msg_id=6273418
By: hubsif
I sync my Windows Mobile 6.1 Device with evolution.
When I create an appointment in Evolution having sensitivity "Private" and then
sync, the appointment is also "Private" in WinMobile.
When I create a "Private" appointment in WinMobile, it is "Public"
in Evolution.
To find out if this is related to the opensync evolution-plugin, I tested with
synce and file-sync plugin.
I found out that the classification (=sensitivity, ical property "CLASS") is
not set in the created ical-files.
John, wanted to run this past you.Date: Tue, 27 Jan 2009 23:35:53 +0100
https://sourceforge.net/forum/message.php?msg_id=6273418
By: hubsif
I sync my Windows Mobile 6.1 Device with evolution.
When I create an appointment in Evolution having sensitivity "Private" and then
sync, the appointment is also "Private" in WinMobile.
When I create a "Private" appointment in WinMobile, it is "Public"
in Evolution.
To find out if this is related to the opensync evolution-plugin, I tested with
synce and file-sync plugin.
I found out that the classification (=sensitivity, ical property "CLASS") is
not set in the created ical-files.
Tried this myself using confidential, airsync entry is
<Sensitivity
xmlns="http://synce.org/formats/airsync_wm5/calendar">3</Sensitivity>
resulting vcal has no Class element.
In event-from-airsync.xsl, the lookup for Sensitivity is conspicuously
missing missing a C: namespace designation, and so I guess never runs.
Any idea if this is deliberate or accidental, or any bad repercussions
from putting it in ?
Ta
Mark
So I guess synce does not read the classification of appointments.
@synce-developers: Is that right? Could you add that feature?
Thank you!
hubsi.
confidential).
@synce-developers: Is that right? Could you add that feature?
Thank you!
hubsi.
confidential).