On Wed, 2011-10-12 at 12:25 +0200, Patrick Ohly wrote: > David, how does the Evolution EWS backend handle this? Does it silently > throw away data or remap it when the EDS vCard doesn't fit into the EWS > data model?
Hm, haven't looked very hard at the addressbook code; that's a question for Chen. Looking at the convert_contact_to_xml() function at http://git.gnome.org/browse/evolution-ews/tree/src/addressbook/e-book-backend-ews.c#n676 I think we just iterate over the known properties and map them, and drop anything we don't have a mapping for. I'm not sure if we have a filter (or capability list) somewhere which prevents the UI from *adding* fields that we don't understand. That would make some sense, in the case where it is specifically an Exchange-based 'folder' in Evolution rather than being a file-based store which just happens to be synced today to Exchange. -- Sent with MeeGo's ActiveSync support. David Woodhouse Open Source Technology Centre [email protected] Intel Corporation
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
