From: tftorrey@tftorrey.com (T.F. Torrey)
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-orgmode@gnu.org, n.goaziou@gmail.com
Subject: Re: [new exporter] [html] Tables of Contents
Date: Wed, 06 Mar 2013 14:37:52 -0700 [thread overview]
Message-ID: <87fw08yztb.fsf@lapcat.tftorrey.com> (raw)
In-Reply-To: <874ngooht6.fsf@gmail.com> (message from Jambunathan K on Wed, 06 Mar 2013 17:34:37 +0530)
Hello Jambunathan,
Jambunathan K <kjambunathan@gmail.com> writes:
> Jambunathan K <kjambunathan@gmail.com> writes:
[... 13 lines omitted ...]
>> 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...
I'm not sure we are talking about the same issues. For one thing, you
are replying to yourself here. I did not suggest this. My request was
merely for valid XML ID's for tables of contents from the HTML exporter,
given that most of the XML tricks in my bag depend on valid XML input.
[... 11 lines omitted ...]
> 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".
I don't think these are related to my original concern, but they do
sound like interesting ideas that might be of use to me. They also
sound like a lot of work. Should this be taken up again after the 8.0
release?
Best regards,
Terry
--
T.F. Torrey
next prev parent reply other threads:[~2013-03-07 6:33 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
2013-03-06 21:37 ` T.F. Torrey [this message]
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=87fw08yztb.fsf@lapcat.tftorrey.com \
--to=tftorrey@tftorrey.com \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@gmail.com \
--cc=n.goaziou@gmail.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).