From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Maus Subject: Re: [ANN] Org to Atom, revisited Date: Fri, 18 Jun 2010 18:03:42 +0200 Message-ID: <87zkysjpk1.wl%dmaus@ictsoc.de> References: <87ocfcdyt3.wl%dmaus@ictsoc.de> <20100616131014.GA21525@pomerol.lix.polytechnique.fr> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: multipart/mixed; boundary="===============0289246716==" Return-path: Received: from [140.186.70.92] (port=35164 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OPe4G-0002yK-Kd for emacs-orgmode@gnu.org; Fri, 18 Jun 2010 12:05:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OPe4F-0000AW-8U for emacs-orgmode@gnu.org; Fri, 18 Jun 2010 12:05:20 -0400 Received: from mysql1.xlhost.de ([213.202.242.106]:43622) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OPe4F-0000AB-0C for emacs-orgmode@gnu.org; Fri, 18 Jun 2010 12:05:19 -0400 In-Reply-To: <20100616131014.GA21525@pomerol.lix.polytechnique.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Olivier Schwander Cc: emacs-orgmode@gnu.org --===============0289246716== Content-Type: multipart/signed; boundary="pgp-sign-Multipart_Fri_Jun_18_18:03:42_2010-1"; micalg=pgp-sha256; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit --pgp-sign-Multipart_Fri_Jun_18_18:03:42_2010-1 Content-Type: text/plain; charset=US-ASCII Olivier Schwander wrote: >> [here]: http://ictsoc.de/code/org-atom/example.atom >Is there the source of this feed somewhere ? It would be nice to have a >self sufficient example. I've uploaded the source of the example feed to http://ictsoc.de/code/org-atom/example.org But it's really as straightforward as the simple example in the documentation. >> * Download and installation >Maybe it would be useful to have the emacs lisp fragment users need to >put in their .emacs file ? And add this part to the "Download and >install" section of the online manual. I'll put more detailed install instructions there as soon as there is a decision about including org-atom into Org or not (yet). >> 1.2 Headline properties >> ======================== >> >> A headline that matches the TAGS/PROP/TODO query for feed entries >> requires at least two headline properties to be present: The =ID= >> property with a unique identifier of the headline (preferable a UUID) >> and a property called =atom_published= containing a time stamp with >> the date an entry should be considered to be published. If these two >> properties are not present, they are automatically created using Org's >> default method to create ID properties[2] and current time and date for >> the publishing >> date[3] >Maybe it should be better to extract timestamp from the usual timestamp >below headlines, like this one: >* Some title > [2010-06-16 mer. 14:19] >or >* DONE Some title > CLOSED: [2010-06-16 mer. 14:19] >Actually, with this solution, it would be better to remove the timestamp >used from the export, since it will displayed by the reader. The problem is, that the Atom specification requires an entry to have at least a atom:updated element. Thus there must be timestamp somewhere. Binding the timestamp to a special position in Org mode markup would limit the functionality of the exporter. However: I understand that it could be reasonable to not use a property, but an already present timestamp. What about something like this: The name of the published and updated property can be customized. It can either be a string with the property name or the symbol 'timestamp_ia. If it is this symbol, the exporter uses the first inactive timestamp of a headline. If the headline does not have an inactive timestamp, the exporter throws an error. >> 1.3 Export settings >> ==================== >> content: turn on/off publishing content >When content is t, the headline is exported both in title and in >content, is this a feature or a bug ? If it's a feature, it should be >nice to have an option to disable it. Hah! Good catch. Never paid attention to this. Just pushed a commit that removes the title in the content element. Thanks for the comment and suggestions. -- David -- OpenPGP... 0x99ADB83B5A4478E6 Jabber.... dmjena@jabber.org Email..... dmaus@ictsoc.de --pgp-sign-Multipart_Fri_Jun_18_18:03:42_2010-1 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iF4EABEIAAYFAkwbmN4ACgkQma24O1pEeOZ3aAEAmFO/cGIMkVPgTqu8DhcSz3eC N18zdQWacqaRW5E4OwABAKErvDmji6G1pSOS1RdqWo8HRS5i6JjTjPQpNQsYdQEx =fe2Y -----END PGP SIGNATURE----- --pgp-sign-Multipart_Fri_Jun_18_18:03:42_2010-1-- --===============0289246716== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode --===============0289246716==--