Additional details
Some of the problem may be due to the emulator not supporting
Jabber or Skype as a contact type (even after I installed the Pidgin
protocols plugin to add support for these to the N900 conversations.
Still I would expect the VCF not to be changed. The contact might not
display which is fine.
Just tested the other IM protocols available for a contact in evolution:
Gadu-Gadu, MSN, Icq, Groupwise.
Result: All display fine after sync to N900 except NO Groupwise
(probably due to lack of installed support for Groupwise)
Also tested VCF compare using synccompare
Result: MSN and GaduGadu remove "TYPE=HOME"
On Sat, 2010-05-29 at 16:41 -0400, Jeff wrote:
> [I'm doing all testing in a virtual machine including an n900 emulator]
>
> In the course of my testing, I decided to create a jumbo contact and
> fill all it's fields (in evolution), then sync to the N900.
>
> Exporting and comparing the contact on each side, then running
> synccompare reveals the following changes.
>
> 1) IM contact fields used in test: AIM, Jabber, Yahoo, SKYPE
>
> Observed: N900 side after sync shows that the
> portion of the VCF for the IM field that says "TYPE=HOME"
> has been removed from Skype and Jabber but NOT AIM or Yahoo
>
> N900 does NOT display these contact fields
>
> Expected: No change in VCF
> N900 SHOULD display skype and jabber contact detail
>
> 2) Address field (ADR in the VCF) for Home address, work address and
> Other addresses appear to have had an extra space inserted after the
> semicolon for the zip field (in th VCF) causing an extra space
> in the country field at it's start
>
>
> Seems to me the 1st issue could cause problems syncing back to N900 IF
> Evolution cared about TYPE for IM fields. Right now it does not seem to
> care.
>
>
> Both seem like issues... please let me know your thoughts on these...
>
> --Jeff
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
