Am 05.11.2010 12:28, schrieb Patrick Ohly:
On Fr, 2010-11-05 at 09:33 +0000, Nils Faerber wrote:
> Am 04.11.2010 20:59, schrieb Patrick Ohly:
>> On Do, 2010-11-04 at 17:58 +0000, Nils Faerber wrote:
>>> I have to admit I have never ever seen or heard about
>>> so I have no clue what this is about.
>> The Horde server is not configured correctly. It sends the client
>> calendar data in an out-dated Funambol XML format.
> Does this also apply to the contacts? Because the same happens with
> contacts - N900->Horde works, but not in the other direction.
That might be the same problem.
It was, yes ;) (see below)
> Now here comes my ignorance: I read "between" the lines
here on the
> mailinglist that basically Syncevolution negotiates dataformats and
> profiles with the syncml partner. There also are config options in the
> sync sources (like calendar) to hardy-fix some of those formats (like
> using icalendar V2.something).
SyncEvolution/Synthesis support that, but Horde doesn't. It basically
detects the peer and then picks one format for sending. That goes wrong
> Is there probably something that I can do on the N900 side to
> Horde into another mode?
You might check your deviceId. That was a workaround that worked a while
ago, but it should be in the code. Hmm, perhaps the N900 port still has
that problem? The workaround was released as part of 1.0 beta 2.
This was it, yes!
I now use something like:
deviceId = sc-api-nat-<identifier>
which you proposed earlier on the SyncEvo Wiki:
(I should have read that earlier!).
Author: Patrick Ohly <patrick.ohly(a)intel.com>
Date: Fri Feb 19 16:13:43 2010 +0100
deviceId: use syncevolution- prefix, helps Horde (MB #9347)
Hmm... would that make a diference in contrast to sc-api-nat-... ?
kernel concepts GbR Tel: +49-271-771091-12
Sieghuetter Hauptweg 48
D-57072 Siegen Mob: +49-176-21024535