emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sean O'Halpin" <sean.ohalpin@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>, emacs-orgmode@gnu.org
Subject: Re: [ANN] Merge of new export framework on Wednesday
Date: Sat, 9 Feb 2013 18:14:37 +0000	[thread overview]
Message-ID: <CAOXM+eWZ8SRW1trHmoUB3LBn4snb7Vd+ZBWPkaDT8eOXCCWUiQ@mail.gmail.com> (raw)
In-Reply-To: <871ucpegkf.fsf@gmail.com>

On Sat, Feb 9, 2013 at 1:56 PM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> Hello,
>
> "Sean O'Halpin" <sean.ohalpin@gmail.com> writes:
>
>> This raises another question which is more about Org document export
>> headers in general: why do we have specific document headers for LaTeX
>> and HTML? Because we need to able to insert raw markup at specific
>> points in the exported document. (We also have =html-preamble= and
>> =html-postamble= which act on every document.) But what about other
>> exporter back-ends? Say we get a native org to docbook exporter. What
>> would be the mechanism for inserting markup into the =<artheader>=?
>> Would there be a =#+DOCBOOK_HEADER=?
>>
>> Please forgive my meandering here. It's just struck me that we might
>> need a more general mechanism for document-level export directives
>> that will avoid multiplying the number of =#+HTML_= style directives
>> we already have. Perhaps something along the lines of:
>>
>>
>> #+BEGIN_SRC ORG
>> ,#+EXPORT html head <style .../>
>> ,#+EXPORT latex header \usepackage{xyz}
>> #+END_SRC
>>
>>
>> where =head= and =header= represent specific places in the exported
>> document that the exporter in question has defined as places you can
>> insert raw markup. So, Org would define the =#+EXPORT= protocol,
>> specific back-ends would define the names and places.
>
> Not every back-end has a concept of "head" (think about Markdown
> back-end). We don't need a general concept for something that isn't
> general.

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. The general concept is that we want
to communicate document level information to the back-end, in this
case, bits of text to insert at specific places which are dependent on
the specific back-end in question.

> Also, completely unifying every back-end is close to impossible, unless
> the same person writes every back-end[1]. Most of the options are
> shared, that's the goal of ox.el, but in the end, each back-end decides
> how it handles the others.

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

Perhaps I'm just expressing a preference for fewer buffer-level
keywords - feel free to ignore the suggestion.

Regards,
Sean

  reply	other threads:[~2013-02-09 18:14 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 [this message]
2013-02-09 18:49           ` Nicolas Goaziou
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=CAOXM+eWZ8SRW1trHmoUB3LBn4snb7Vd+ZBWPkaDT8eOXCCWUiQ@mail.gmail.com \
    --to=sean.ohalpin@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@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).