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 02:51:09 -0700 [thread overview]
Message-ID: <87r4jszwj6.fsf@lapcat.tftorrey.com> (raw)
In-Reply-To: <87obexb1rp.fsf@gmail.com> (message from Jambunathan K on Wed, 06 Mar 2013 09:47:14 +0530)
Hello Jambunathan,
Jambunathan K <kjambunathan@gmail.com> writes:
> Torrey
>
>>>> One small problem, though: I see that if there is a TOC at the top and
>>>> then one included later using #+TOC, the exporter gives them both the
>>>> same id (<div id="table-of-contents">). Duplicate ID's makes the XML
>>>> invalid.
>>>
>>> What do you suggest instead? id="table-of-contents-1" for the first
>>> #+TOC: keyword and so on?
>
> Why do you need two table of contents?
I don't, though some might. As was explained earlier in this thread, if
toc: options are set in the OPTIONS line, and a #+TOC is specified
later, two tables of contents are generated, and they have the same ID.
It is a feature of the new exporter, but duplicate ID's are not valid in
XML.
It is common for technical manuals to have a top-level table of contents
at the front of the manual and a detailed table of contents later on.
For instance, the GNU project Info manuals have that structure.
>> 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.
>
> I would recommend that you just specify just the use-case and leave out
> the "how"s of implementation.
>
> Put your user hat and set aside the developer's hat.
What a strange, semi-insulting thing to say.
And misguided, too, as I was suggesting a design, not its
implementation. As someone with all my own documents in Org and
extensive experience developing XSLT and lisp to process the XHTML
output of Org, I appreciate when the design of the HTML output is
logical and useful.
I would rather see a good design implemented in hacks than a poor design
implemented in beautiful code.
Regards,
Terry
--
T.F. Torrey
next prev parent reply other threads:[~2013-03-06 9:51 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
2013-03-07 7:57 ` Jambunathan K
2013-03-06 9:51 ` T.F. Torrey [this message]
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=87r4jszwj6.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).