From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexis Subject: Re: org-contacts development Date: Mon, 26 May 2014 14:06:12 +1000 Message-ID: <878uppkwuj.fsf@gmail.com> References: <8761kxnno5.fsf@gmail.com> <87ioovf7cw.fsf@tanger.home> <87fvjzgjan.fsf@gmail.com> <87bnulfcn1.fsf@tanger.home> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48907) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WomBA-0002vN-20 for emacs-orgmode@gnu.org; Mon, 26 May 2014 00:06:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WomB1-0005VU-0F for emacs-orgmode@gnu.org; Mon, 26 May 2014 00:06:28 -0400 Received: from mail-pb0-x230.google.com ([2607:f8b0:400e:c01::230]:60657) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WomB0-0005UQ-P3 for emacs-orgmode@gnu.org; Mon, 26 May 2014 00:06:18 -0400 Received: by mail-pb0-f48.google.com with SMTP id rr13so7009192pbb.7 for ; Sun, 25 May 2014 21:06:17 -0700 (PDT) Received: from localhost (ppp118-209-145-187.lns20.mel6.internode.on.net. [118.209.145.187]) by mx.google.com with ESMTPSA id mq10sm5134248pbc.62.2014.05.25.21.06.15 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Sun, 25 May 2014 21:06:17 -0700 (PDT) In-reply-to: <87bnulfcn1.fsf@tanger.home> 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Daimrod writes: > Sure, but then how would we define the map? with a fixed set of rules? > with a user customizable map (e.g. '(("MOBILE" -> "TELL;CELL") > ("EMAIL_WORK" -> "EMAIL;TYPE=work")))? More the latter. My initial (again, brainstorming!) thinking has an user-modifiable data structure along the lines of the following: +-----------------------------------+------------+--------------------+ | elisp var |org property| ~ vCard equivalent | +-----------------------------------+------------+--------------------+ | org-contacts-email-work-property |EMAIL_WORK |EMAIL;TYPE=work | | org-contacts-mobile-work-property |MOBILE_WORK |TEL;CELL;TYPE=work | +-----------------------------------+------------+--------------------+ English-language properties for the org property column could be provided by default, but users who wanted to use non-English property names could do so by modifying the relevant entries. > I'm not saying that it's impossible nor that we shouldn't do it but that > we need to think about it first. :) Oh 100% agreed! That's why i've started this discussion here, so as to get input, feedback, and hopefully at least rough consensus, on how to approach all this. :-) > Well, if people are willing to help, I'll see if I can come up with a > proposal. :-) Sounds good! Alexis.