From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Jerram Subject: Re: exported contacts problem Date: Sat, 3 Aug 2019 18:48:31 +0100 Message-ID: References: <20190802160236.GR17561@protected.rcdrun.com> <87mugrb7fi.fsf@ericabrahamsen.net> <20190802213421.GZ17561@protected.rcdrun.com> <875znfaycd.fsf@ericabrahamsen.net> <20190803103340.GN23820@protected.rcdrun.com> <874l2yxnrs.fsf@ericabrahamsen.net> <20190803163219.GZ23820@protected.rcdrun.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000f32060058f3a15e8" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:52613) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hty96-0001zk-PK for emacs-orgmode@gnu.org; Sat, 03 Aug 2019 13:48:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hty95-0008Nh-ST for emacs-orgmode@gnu.org; Sat, 03 Aug 2019 13:48:44 -0400 Received: from mail-qt1-x82b.google.com ([2607:f8b0:4864:20::82b]:42880) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hty95-0008NS-OC for emacs-orgmode@gnu.org; Sat, 03 Aug 2019 13:48:43 -0400 Received: by mail-qt1-x82b.google.com with SMTP id h18so77224619qtm.9 for ; Sat, 03 Aug 2019 10:48:43 -0700 (PDT) In-Reply-To: <20190803163219.GZ23820@protected.rcdrun.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Jean Louis Cc: Eric Abrahamsen , Org Mode List --000000000000f32060058f3a15e8 Content-Type: text/plain; charset="UTF-8" I've tried to work on contact conversion and synchronization in the past, aiming to merge and unify contacts that I've built up in BBDB, Google Contacts, email systems, pre-Android phones, etc. The problematic aspect was different systems using different field names and structures, e.g. one with separate First Name and Last Name, and another with a combined Name field; different approaches to breaking up addresses; additional arbitrary notes fields; etc. With that in mind, I'm curious if the writers on this thread could comment on: 1. is this situation any better now? 2. if you favour using org-contacts or org-vcard, what do you see as the benefit of Org as your master contact format, as opposed to say BBDB or .vcf? --000000000000f32060058f3a15e8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I've tried to work on contact convers= ion and synchronization in the past, aiming to merge and unify contacts tha= t I've built up in BBDB, Google Contacts, email systems, pre-Android ph= ones, etc.=C2=A0 The problematic aspect was different systems using differe= nt field names and structures, e.g. one with separate First Name and Last N= ame, and another with a combined Name field; different approaches to breaki= ng up addresses; additional arbitrary notes fields; etc.

With that in mind, I'm curious if the writers on this thread could com= ment on:
1. is this situation any better now?
2. if you= favour using org-contacts or org-vcard, what do you see as the benefit of = Org as your master contact format, as opposed to say BBDB or .vcf?

--000000000000f32060058f3a15e8--