From: "Rüdiger Sonderfeld" <firstname.lastname@example.org>
To: email@example.com, firstname.lastname@example.org
Subject: Re: Converting org-mode/org-contacts to VCard (importing to Android)
Date: Sat, 23 Nov 2013 01:00:56 +0100 [thread overview]
Message-ID: <81482742.cUeHUGJmrV@descartes> (raw)
On Friday 22 November 2013 18:09:42 Karl Voit wrote:
> I have to admit that I don't know the feature-set of the Org-mode
> export. I would be very surprised, if the Org-mode export method is
> able to follow my custom "photo:" link I am using, grab the image
> file, test if it has a image format that works with VCard
> 2.1 on Android, and encodes it in base64 accordingly.
Org-contacts has an :ICON: property and supports Gravatar. It doesn't seem to
be handled in the VCard export though.
> You see: I want to have ways to tweak the export process. And as
> long as I don't know ELISP that well, I stick to the tools I know.
I understand that and it solved your problem for now. But having an external
tool in a different programming language is usually not a good idea to solve
the problem in the long run. The code base of org-contacts and your tool is
under the risk of diverting quickly. If it's in org-contacts then it is
maintained in one piece and easily accessible to other users.
So my point is you should take a look at elisp. It's a lot of fun to use and
if you are using org-mode and Emacs then you will have to learn it sooner or
> A side remark of mine: a couple of months ago I tried to find out
> how to store address information, phone numbers, and so on in
> org-contact properties. AFAIR I could not find anything except the
> :EMAIL: property. Is there a standard out there that answers
> questions like "separate street from house number?", "how to cope
> with multiple addresses for one contact?", and so forth? I created
> something on my own as you can see on .
I have to admit the org-contacts format is pretty much ad-hoc and not really
well designed. It is documented a bit in the file itself
(contrib/lisp/contacts.el). M-x customize-group RET org-contacts RET should
also tell you more about the options.
Your format choice is not fully compatible with the existing org-contacts.
Right now multiple entries are separated by space (which sadly breaks for
addresses) and different entry names are used.
However I'd look forward to some new ideas and improvements. Right now it's
not ideal solution.
next prev parent reply other threads:[~2013-11-23 0:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 16:37 Converting org-mode/org-contacts to VCard (importing to Android) Karl Voit
2013-11-22 16:54 ` Rüdiger Sonderfeld
2013-11-22 17:09 ` Karl Voit
2013-11-23 0:00 ` Rüdiger Sonderfeld [this message]
2013-11-24 13:06 ` Implementing Org-mode tools in languages other than ELISP (was: Converting org-mode/org-contacts to VCard (importing to Android)) Karl Voit
2014-01-04 14:58 ` Implementing Org-mode tools in languages other than ELISP Bastien
2014-01-04 16:43 ` François Pinard
2014-01-05 16:43 ` Daniel Clemente
2014-01-06 10:44 ` Parsing Org-mode in Python (was: Implementing Org-mode tools in languages other than ELISP) Karl Voit
2014-01-07 2:33 ` Parsing Org-mode in Python François Pinard
2014-01-07 16:09 ` Brett Viren
2014-01-08 12:33 ` François Pinard
2014-01-08 15:42 ` Brett Viren
2014-01-08 16:11 ` François Pinard
2014-01-09 4:13 ` Daniel Clemente
2014-01-09 14:13 ` Brett Viren
2014-01-07 1:47 ` Implementing Org-mode tools in languages other than ELISP François Pinard
2013-11-23 8:36 ` Converting org-mode/org-contacts to VCard (importing to Android) Feng Shu
2013-11-23 8:29 ` Feng Shu
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).