From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Sean O'Halpin <sean.ohalpin@gmail.com>
Cc: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>, emacs-orgmode@gnu.org
Subject: Re: [ANN] Merge of new export framework on Wednesday
Date: Sat, 09 Feb 2013 19:49:44 +0100 [thread overview]
Message-ID: <87mwvdgw53.fsf@gmail.com> (raw)
In-Reply-To: <CAOXM+eWZ8SRW1trHmoUB3LBn4snb7Vd+ZBWPkaDT8eOXCCWUiQ@mail.gmail.com> (Sean O'Halpin's message of "Sat, 9 Feb 2013 18:14:37 +0000")
"Sean O'Halpin" <sean.ohalpin@gmail.com> 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 "<script.../>") ...), 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
next prev parent reply other threads:[~2013-02-09 19:21 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 19:00 [ANN] Merge of new export framework on Wednesday Nicolas Goaziou
2013-02-03 20:59 ` François Allisson
2013-02-04 9:17 ` Detlef Steuer
2013-02-04 13:49 ` David Bjergaard
2013-02-04 21:56 ` Suvayu Ali
2013-02-05 1:07 ` Eric S Fraga
2013-02-05 7:41 ` Suvayu Ali
2013-02-05 9:25 ` Eric S Fraga
2013-02-05 11:18 ` Suvayu Ali
2013-02-05 12:50 ` Eric S Fraga
2013-02-05 13:07 ` Suvayu Ali
2013-03-04 15:20 ` Suvayu Ali
2013-02-04 23:05 ` Bastien
2013-02-04 13:35 ` Rasmus
2013-02-05 16:30 ` org export Taskjuggler (was: Re: [ANN] Merge of new export framework on Wednesday - ) Giovanni Ridolfi
2013-02-05 17:59 ` org export Taskjuggler Nicolas Goaziou
2013-02-07 10:21 ` Christian Egli
2013-02-07 10:43 ` Jambunathan K
2013-02-07 13:13 ` Nicolas Goaziou
2013-02-07 0:14 ` [ANN] Merge of new export framework on Wednesday Jay Kerns
2013-02-08 15:53 ` Sean O'Halpin
2013-02-08 16:45 ` Sebastien Vauban
2013-02-09 13:20 ` Sean O'Halpin
2013-02-09 13:56 ` Nicolas Goaziou
2013-02-09 18:14 ` Sean O'Halpin
2013-02-09 18:49 ` Nicolas Goaziou [this message]
2013-02-09 20:55 ` Nicolas Richard
2013-03-02 18:14 ` Bastien
2013-03-02 21:11 ` Sebastien Vauban
2013-03-03 5:35 ` Bastien
2013-03-03 12:25 ` Sean O'Halpin
2013-03-03 17:09 ` Bastien
2013-03-04 1:50 ` Rick Frankel
2013-03-04 6:57 ` Bastien
2013-03-04 9:09 ` T.F. Torrey
2013-03-04 15:19 ` Mike McLean
2013-03-04 15:24 ` Nicolas Goaziou
2013-03-04 16:12 ` Mike McLean
2013-03-04 16:30 ` Nicolas Goaziou
2013-03-04 16:44 ` Mike McLean
2013-03-04 15:28 ` Suvayu Ali
2013-03-04 17:44 ` Bastien
2013-02-09 8:03 ` Achim Gratz
2013-02-09 8:21 ` Nicolas Goaziou
2013-02-09 9:26 ` Bastien
2013-02-09 10:33 ` Achim Gratz
2013-02-09 10:44 ` Nicolas Goaziou
2013-02-09 10:49 ` Bastien
2013-02-09 15:01 ` Jambunathan K
2013-02-09 17:16 ` compilation issues of new export framework Achim Gratz
2013-02-09 17:50 ` Nicolas Goaziou
2013-02-09 18:02 ` Achim Gratz
2013-02-10 10:44 ` Achim Gratz
2013-02-10 12:53 ` Nicolas Goaziou
2013-02-10 15:53 ` Nicolas Goaziou
2013-02-11 7:49 ` Achim Gratz
2013-02-11 20:18 ` Nicolas Goaziou
2013-02-11 20:30 ` Achim Gratz
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=87mwvdgw53.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=sean.ohalpin@gmail.com \
--cc=wxhgmqzgwmuf@spammotel.com \
/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).