Den 05. nov. 2011 21:21, skrev Patrick Ohly:
> On Sat, 2011-11-05 at 14:24 +0100, Ove Kåven wrote:
>> Den 05. nov. 2011 13:27, skrev Ove Kåven:
>>>> You can comment out the whole <parameter></parameter> part or remove it
>>>> to try out whether it works.
>>>
>>> I'll give it a shot, thanks...
>>
>> Well, that works for the entries where SyncEvolution is adding EXDATEs
>> itself, but for those EXDATEs which have already been pushed to Google
>> and is coming back from Google with TZIDs, there's still a problem... I
>> suppose it'll take a rule for the non-auto-generated EXDATEs too.
>
> Attached two patches, both also committed to the maemo5-recurrences
> branch.
>
> The first one should suppress the TZID also for regular EXDATEs.
>
> The second one attempts to add that time zone information back when
> reading from the storage.
>
> Both patches are completely untested.
diff --git a/src/syncevo/configs/scripting/11calendar.xml
b/src/syncevo/configs/scripting/11calendar.xml
index fe38eb6..c47958f 100644
--- a/src/syncevo/configs/scripting/11calendar.xml
+++ b/src/syncevo/configs/scripting/11calendar.xml
@@ -193,8 +193,10 @@
// the Maemo calendar storages because it uses EXDATE
// without TZID.
if (!ISFLOATING(DTSTART)) {
- STRING tz = TIMEZONE(DTSTART);
+ STRING tz;
+ tz = TIMEZONE(DTSTART);
if (tz != "UTC") {
+ INTEGER i;
i = 0;
while (i<SIZE(EXDATES)) {
if (ISFLOATING(EXDATES[i])) {
Anyway, it seems to work, now there are no more visible duplicates in
the calendar.
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
