From: Armin B. <arm...@de...> - 2006-06-05 00:16:12
|
Graham Cobb wrote: > Before I submit a bug ticket I thought I would check with the list to s= ee if=20 > there was anything I missed. >=20 > It looks like format detection doesn't happen during conflict checking = -- and=20 > it should. =20 >=20 > For example, if I sync between kdepim and file I can get a directory wi= th file=20 > versions of my contacts, events and notes. Great. However, if I force= a=20 > slow sync (without changing anything in the KDE side or in the files) e= very=20 > one of those files is marked as a conflict. >=20 > The problem is that the comparison check (to see if the entries conflic= t) is=20 > done with the XML datatype but that the file data cannot be converted t= o XML. =20 > Of course, when actually performing a change the file data is converted= to=20 > XML perfectly well, but that requires using a detector. And the detect= or is=20 > not used during the comparison check. >=20 > Is there any reason this shouldn't be regarded as a bug? Is there some= reason=20 > it is particularly hard to do? Yes, this can be regarded as a bug and will be fixed in the next version of opensync. The problem with fixing this bug is: Lets assume that we have telephone which can store notes and contacts. We are synchronizing this telephone with a directory which contains a single vcard. But opensync has a problem now: how should this file be treated? Should it be synchronized as a contact or as a note? At the moment it would be synchronized as a note (thats also the reason why the comparison fails). But we cannot simply always run the detector on it, because someone might want to really transfer it as a note. But i already have a solution in mind. I just need to find some time to implement it. Armin >=20 > Graham >=20 >=20 > _______________________________________________ > Opensync-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensync-users >=20 |