On Sun, 2015-02-15 at 17:42 +0100, Daniel CLEMENT wrote:
Hello, sorry for the delay in the reply, I was away this week.
Le lundi 09 février 2015 à 14:47 +0100, Patrick Ohly a écrit :
> On Sat, 2015-01-03 at 18:13 +0100, Daniel CLEMENT wrote:
> > Hello, and happy 2015 year to all list members.
> >
> > Linux Mint Debian, Evolution 3.8.5, SyncEvolution 1.5.
> >
> > I have noticed that when I sync from Evolution to my phone (Nokia E72),
> > the calendar item is 1 hour late on the Nokia. But when I sync from the
> > phone to Evolution, there is no such offset.
> >
> > I'm puzzled, AFAICT it was not the case before we switched to winter
> > time. On the phone, as usual, it was automatic, and then I got the
> > message that "calendar entries had been updated". But I had never
seen
> > this offset the years before.
> >
> > Evolution is set to "use system time zone", and the phone gets its
time
> > from the GSM network.
> >
> > TIA for any input about this. Best regards,
>
> Such cases are always hard to diagnose without examples.
>
> It would help to compare the data sent by the phone and data sent by
> SyncEvolution. Use loglevel=4 and then check syncevolution-log.html for
> "parsing" and "generated" dumps of the event in question.
>
I observe this offset with every event created in Evolution. As I said
in another message, I was could check that phone <==> Funambol server
was OK both ways (which is expected, since the phone uses the Funambol
client, not Syncevolution). The only problem is Evolution ==> Funambol
server.
So I created a dummy event "Livraison" (delivery) scheduled next Tuesday
(0217), 14.00 to 14.30 (Paris time).
Below is the contents of syncevolution-log.html for this event under
"generated" (no "parsing", which I assume normal as the event is
new).
The event ends up on the Funambol (OneMediaHub) server 1 hour late
(15.00).
[...]
DTSTART;TZID="Europe/Paris":20150217T140000
[...]
I see strange things in the TZ name (CET vs. CEST vs. Europe/Paris,
with
or without quotes)... Could that be the problem?
The quotation marks around the TZID parameter value seem to be the
problem. I removed them and then it works. It seems that the Funambol
iCalendar 2.0 parser fails to remove the marks and then does not apply
the correct time zone when storing the event.
This is a bug in Funambol, there's nothing wrong with using redundant
(in this case) quotation marks. Can you report this problem to Funambol
and report back what the response is and/or provide a link to the bug
report?
SyncEvolution started using these quotation marks in 1.4.99.2 when
fixing incorrect escaping via backslash. It is not required to quote the
Europe/Paris value; SyncEvolution does it because it has a fairly
conservative list of characters that are allowed without quoting. I can
add the slash to that white list and include that change in 1.5.1, but I
don't know when I'll release that.
If you want to compile from source, then patch like this:
diff --git a/src/sysync/mimedirprofile.cpp
b/src/sysync/mimedirprofile.cpp
index e618f80..384e7dc 100644
--- a/src/sysync/mimedirprofile.cpp
+++ b/src/sysync/mimedirprofile.cpp
@@ -2378,6 +2378,7 @@ sInt16 TMimeDirProfileHandler::generateValue(
if (aParamValue) {
for (const char *p=val.c_str();(c=*p)!=0;p++) {
if (!(isalnum(c) ||
+ c == '/' ||
c == '-' ||
c == '_')) {
quotedstring = true;
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.