emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Olivier Schwander <olivier.schwander@chadok.info>
To: emacs-orgmode@gnu.org
Subject: Re: [ANN] Org to Atom, revisited
Date: Wed, 16 Jun 2010 15:10:14 +0200	[thread overview]
Message-ID: <20100616131014.GA21525@pomerol.lix.polytechnique.fr> (raw)
In-Reply-To: <87ocfcdyt3.wl%dmaus@ictsoc.de>

Le 15 Jun 2010 18:51, David Maus a écrit:
> 
> The Org to Atom exporter I've preliminary announce some weeks ago
> entered a state I consider to be stable and consistent enough to be
> included into Org mode.

Great work, I work it will really improve web publishing ability of
org-mode.

Some remarks below:

> [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.

> * 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.

> * Documentation

> Table of Contents
> =================
> 1 Exporting an Org file to Atom

There is no Install section here, but there is one in the online
version.

> 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.

> 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.

Cheers,

Olivier

  parent reply	other threads:[~2010-06-16 13:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-15 16:51 [ANN] Org to Atom, revisited David Maus
2010-06-15 20:48 ` Scot Becker
2010-06-15 23:06 ` Matt Lundin
2010-06-16  4:02 ` T.F. Torrey
2010-06-16 13:10 ` Olivier Schwander [this message]
2010-06-18 16:03   ` David Maus
2010-06-20  8:54     ` T.F. Torrey
2010-07-07  5:38 ` Scott Jaderholm
2010-07-09  5:55   ` David Maus

Reply instructions:

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100616131014.GA21525@pomerol.lix.polytechnique.fr \
    --to=olivier.schwander@chadok.info \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).