From: Jambunathan K <kjambunathan@gmail.com>
To: "T.F. Torrey" <tftorrey@tftorrey.com>
Cc: emacs-orgmode@gnu.org, Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: [new exporter] [html] Tables of Contents
Date: Wed, 06 Mar 2013 17:34:37 +0530 [thread overview]
Message-ID: <874ngooht6.fsf@gmail.com> (raw)
In-Reply-To: <87k3plb0w4.fsf@gmail.com> (Jambunathan K.'s message of "Wed, 06 Mar 2013 10:06:11 +0530")
Jambunathan K <kjambunathan@gmail.com> writes:
>>> This gives a significant advantage in that authors can link to the
>>> various instances just by knowing their own usage. For instance, if
>>> they provided a top-level toc at the beginning of their book, and a
>>> deeper-level toc later on, they could link to each separately by id by
>>> knowing this plan.
>>
>> This seems like a valid use-case.
>
> Brainstorimg here: Why not export a subtree (with displaced section
> numbers) and splice the exported strings together to produce the
> compelete document.
>
> Subtree export of headline 1, but with section numbers starting at 1.
> Subtree export of headline 2, but with section numbers starting at 2.
> Splice them together.
Considering that HTML exporter can export a subtree, I believe you can
do some XSLT magic so that the individual HTML generated by Org is
transformed before being spliced.
Do you really want this to be supported within the scope of the Org
exporter? Are you sure you have explored all the tricks in your bag
before raising this request. Just wanted to confirm, because you seem
to be the HTML expert among the three of us...
> ----------------------------------------------------------------
>
> There are books where each chapter could be written by different
> authors. The chapters are later spliced together to produce the master
> document. In case of OpenDocument, such files have *.odm extension. I
> can look up what the OpenDocument spec says or LibreOffice does.
>
> ----------------------------------------------------------------
Or
Allow a subtree to take EXPORT_TOC property. (There should be a way to
specifiy where this TOC will end up in - beginning of that chapter or
end of the chapter)
Similarly, one could introduce EXPORT_ENDNOTES property whereby each
chapter can have it's own self-contained "End Notes section".
next prev parent reply other threads:[~2013-03-06 12:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 19:57 [new exporter] [html] Tables of Contents T.F. Torrey
2013-03-04 20:30 ` Nicolas Goaziou
2013-03-04 23:10 ` T.F. Torrey
2013-03-05 7:53 ` Nicolas Goaziou
2013-03-05 20:21 ` T.F. Torrey
2013-03-06 4:17 ` Jambunathan K
2013-03-06 4:36 ` Jambunathan K
2013-03-06 12:04 ` Jambunathan K [this message]
2013-03-06 21:37 ` T.F. Torrey
2013-03-07 7:57 ` Jambunathan K
2013-03-06 9:51 ` T.F. Torrey
2013-03-06 10:10 ` Jambunathan K
2013-03-06 20:59 ` T.F. Torrey
2013-03-06 22:42 ` Bastien
2013-03-07 0:27 ` Jambunathan K
2013-03-07 9:10 ` Bastien
2013-03-07 9:24 ` Jambunathan K
2013-03-10 5:20 ` Samuel Wales
2013-03-10 5:42 ` Jambunathan K
2013-03-10 9:35 ` Bastien
2013-03-07 0:33 ` Jambunathan K
2013-03-06 10:35 ` Jambunathan K
2013-03-06 21:21 ` T.F. Torrey
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=874ngooht6.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
--cc=tftorrey@tftorrey.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).