From mboxrd@z Thu Jan 1 00:00:00 1970 From: "T.F. Torrey" Subject: Re: [ANN] Org to Atom, revisited Date: Sun, 20 Jun 2010 01:54:10 -0700 Message-ID: <4C1DD732.8000707@tftorrey.com> References: <87ocfcdyt3.wl%dmaus@ictsoc.de> <20100616131014.GA21525@pomerol.lix.polytechnique.fr> <87zkysjpk1.wl%dmaus@ictsoc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from [140.186.70.92] (port=44587 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OQGIJ-0005EL-2Z for emacs-orgmode@gnu.org; Sun, 20 Jun 2010 04:54:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OQGIG-00048N-OM for emacs-orgmode@gnu.org; Sun, 20 Jun 2010 04:54:22 -0400 Received: from slow3-v.mail.gandi.net ([217.70.178.89]:57395) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OQGIG-00043Y-FN for emacs-orgmode@gnu.org; Sun, 20 Jun 2010 04:54:20 -0400 Received: from mrelay2-d.mgt.gandi.net (mrelay2-d.mgt.gandi.net [10.0.21.96]) by slow3-v.mail.gandi.net (Postfix) with ESMTP id A966487080 for ; Sun, 20 Jun 2010 10:54:18 +0200 (CEST) Received: from mfilter3-d.gandi.net (mfilter3-d.gandi.net [217.70.178.44]) by mrelay2-d.mgt.gandi.net (Postfix) with ESMTP id 8A5EC2251C1 for ; Sun, 20 Jun 2010 10:54:18 +0200 (CEST) Received: from mrelay2-d.mgt.gandi.net ([10.0.21.96]) by mfilter3-d.gandi.net (mfilter3-d.gandi.net [217.70.178.44]) (amavisd-new, port 10024) with ESMTP id C5fKmDAQuzKG for ; Sun, 20 Jun 2010 10:54:14 +0200 (CEST) Received: from [192.168.1.27] (ip98-165-69-201.ph.ph.cox.net [98.165.69.201]) (Authenticated sender: tftorrey@tftorrey.com) by mrelay2-d.mgt.gandi.net (Postfix) with ESMTPSA id 6FCFE2251B9 for ; Sun, 20 Jun 2010 10:54:12 +0200 (CEST) In-Reply-To: <87zkysjpk1.wl%dmaus@ictsoc.de> 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: emacs-orgmode@gnu.org On 06/18/2010 09:03 AM, David Maus wrote: > 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. This would be a welcome addition. I would use it, and perhaps it would entice RMS to adopt Org Mode as well. It's pretty close to what he uses for his political notes: http://www.stallman.org/archives/2010-mar-jun.html >>> 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 > > > > _______________________________________________ > 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 Org Mode gets better all the time. Thanks again. - Terry