From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [ANN] Merge of new export framework on Wednesday Date: Sat, 09 Feb 2013 19:49:44 +0100 Message-ID: <87mwvdgw53.fsf@gmail.com> References: <876229nrxf.fsf@gmail.com> <86d2wau54f.fsf@somewhere.org> <871ucpegkf.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:41083) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U4Fyu-0004M4-8U for emacs-orgmode@gnu.org; Sat, 09 Feb 2013 14:21:01 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U4Fys-0006hn-UT for emacs-orgmode@gnu.org; Sat, 09 Feb 2013 14:21:00 -0500 Received: from mail-wi0-f174.google.com ([209.85.212.174]:50358) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U4Fys-0006hg-Nm for emacs-orgmode@gnu.org; Sat, 09 Feb 2013 14:20:58 -0500 Received: by mail-wi0-f174.google.com with SMTP id hi8so1976142wib.1 for ; Sat, 09 Feb 2013 11:20:58 -0800 (PST) In-Reply-To: (Sean O'Halpin's message of "Sat, 9 Feb 2013 18:14:37 +0000") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Sean O'Halpin Cc: Sebastien Vauban , emacs-orgmode@gnu.org "Sean O'Halpin" writes: > I haven't made myself clear. I'm not suggesting a general concept of > "head". What I am suggesting is that the back-ends handle these > back-end specific concepts themselves, rather than add more buffer > keywords for every new exporter. Each back-end adds its own keywords, define them, document them and interpret them. So, basically, backends handle these concept themselves, don't they? > This would not require unifying every back-end at all. In fact, quite > the opposite. All you would need would be for the generic exporter > framework to provide the back-end a dictionary of key value pairs, > such as ((:head "") ...), which the back-end would > interpret. This is exactly what is happening. > You would avoid having to add document level keywords such as > HTML_STYLE and MAN_CLASS_OPTIONS for new exporters. It would be the > back-end's responsibility to validate and document these options. My > suggestion is really not so different from what the new exporter does > anyway. Where we now have =#+HTML_LINK_UP: "..."=, I'm suggesting we > have =#+EXPORT: html link-up "..."=. Honestly, besides the syntax, I don't see any difference. Regards, -- Nicolas Goaziou