|
From: Emanoil K. <del...@ya...> - 2011-01-21 10:08:20
|
Hi, thanks for the discussion and paying attention to this subject.
--- On Thu, 1/20/11, Chris Frey <cd...@fo...> wrote:
> > > Experience teaches us that implementation of the
> V-formats in the real world
> > > is very poor! It would be worth both the
> vformat and xmlformat code in
> > > OpenSync to be more tolerant. OpenSync is
> in the business of syncing user's
> > > devices, not enforcing minor standards
> violations.
> >
> > Yes, you are absolutely right. OpenSync should
> be way more
> > tolerant towards format errors. A format error
> is not the same
> > as an exit error in terms of libopensync, which
> automatically
> > leads to slow-sync of all of the entries available.
>
> I don't know which software stack is creating this vCard
> data.
>
> Emanoil: can you let us know if you are getting this data
> from Akonadi
> or if you are creating it
> yourself? If the plugin is creating
> the vCard data, the plugin should be
> fixed, not the parser.
The history as follows. After I bought the phone I used windows to sync my contacts from the old phones (nokia and sony-err). I've managed then to sync my contacts with kde3 (somehow, with having a lot of duplicates) with opensync 0.22. After this I've been using Nokia in windows (vmware) and later the SyncEvolution app. So I guess somehow this contact was transfered to the phone. Now the strange thing is that this GEO field is not visible on the phone and I can not edit it.
>
> But, if people have time on their hands, and want to hack
> on the code,
> go to the vformat plugin, in src/xmlformat-vcard.c, line
> 444, and
> change the handle_location_attribute() function. Test
> code would also
> be nice. :-)
>
I'll have a look at it.
regards
|