emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: S5 export
Date: Thu, 03 Feb 2011 19:48:47 +0100	[thread overview]
Message-ID: <878vxx0x9s.fsf@Rainer.invalid> (raw)
In-Reply-To: 87oc6tf2x3.fsf@gnu.org

Bastien <bastien.guerry@wikimedia.fr> writes:
> I would welcome an approach where we factor out some elements of
> org-export-as-html, so that exporting to s5 would just require the 
> user to customize those elements.

Sorry for piggy-backing onto this topic, but I seem to remember the
mention of a "generic exporter" on this list, but I don't remember what
the outcome of that discussion was.  While looking at the table export I
realized that there is lots of duplicated code just for exporting the
tables, which seems wasteful (and error-prone in the longer term). Would
it seem reasonable to have a "generic export" function that parses the
org document into a structure of callbacks and lists and then only
define the callbacks for each backend?

+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf Blofeld V1.15B11:

  reply	other threads:[~2011-02-03 18:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04 14:31 S5 export Pierre de Buyl
2011-02-03 17:23 ` Bastien
2011-02-03 18:48   ` Achim Gratz [this message]
2011-02-11 11:22     ` Bastien
2011-06-01 12:41   ` [Orgmode] " Pierre de Buyl
2011-06-01 18:21     ` Pierre de Buyl
2011-06-01 21:31     ` Eric Schulte
2011-06-01 22:41     ` Eric Schulte
     [not found]       ` <AAB99C57-C1B0-4C78-90BD-3D9FE1E4958A@ulb.ac.be>
2011-06-03 11:38         ` Pierre de Buyl
2011-06-03 12:48           ` Eric Schulte
2011-06-03 13:45             ` Pierre de Buyl
2011-06-03 15:02               ` Eric Schulte
2011-06-03 13:15           ` Christian Moe
2011-06-03 15:05             ` Eric Schulte

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:

  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=878vxx0x9s.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \


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