From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Re: S5 export Date: Fri, 11 Feb 2011 12:22:49 +0100 Message-ID: <87sjvux1bq.fsf@gnu.org> References: <28A74B24-4011-4F2D-AA51-7E18C4765669@chem.utoronto.ca> <87oc6tf2x3.fsf@gnu.org> <878vxx0x9s.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from [140.186.70.92] (port=58461 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Pnr5K-0002GT-Dc for emacs-orgmode@gnu.org; Fri, 11 Feb 2011 06:22:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Pnr5J-0000H2-0I for emacs-orgmode@gnu.org; Fri, 11 Feb 2011 06:22:46 -0500 Received: from mail-fx0-f41.google.com ([209.85.161.41]:44059) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Pnr5I-0000Gy-O2 for emacs-orgmode@gnu.org; Fri, 11 Feb 2011 06:22:44 -0500 Received: by fxm12 with SMTP id 12so2729748fxm.0 for ; Fri, 11 Feb 2011 03:22:44 -0800 (PST) In-Reply-To: <878vxx0x9s.fsf@Rainer.invalid> (Achim Gratz's message of "Thu, 03 Feb 2011 19:48:47 +0100") 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: Achim Gratz Cc: emacs-orgmode@gnu.org Hi Achim, Achim Gratz writes: > Bastien 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? There are now three generic exporters: - org-export-generic.el in contrib/lisp/ by Wes Hardaker - org-export.el (in EXPERIMENTAL/) - the one that Jambunathan and Lennart provide with the odt export I will document org-export.el -- don't hesitate to have a look. I will also take time to look more closely at the work Lennart did for the odt export to see whether we can refactor some org-parse.el with the parsing functions in org-export.el. This requires more time that I have everyday, expect this to happen after a long week-end! -- Bastien