From: tftorrey@tftorrey.com (T.F. Torrey)
To: Jambunathan K <kjambunathan@gmail.com>
Cc: n.goaziou@gmail.com, emacs-orgmode@gnu.org
Subject: Re: [new exporter] [html] Tables of Contents
Date: Wed, 06 Mar 2013 14:21:47 -0700 [thread overview]
Message-ID: <87k3pkz0k4.fsf@lapcat.tftorrey.com> (raw)
In-Reply-To: <87ip5495pl.fsf@gmail.com> (message from Jambunathan K on Wed, 06 Mar 2013 16:05:02 +0530)
Hello Jambunathan,
Jambunathan K <kjambunathan@gmail.com> writes:
> Is there a way your specific problem could be solved if we were to use
> CSS counters for numbering various things? Would you like to submit a
> patch to ox-html.el that uses CSS-based counters rather than counters
> computed with hand.
No.
I'm not sure I understand your motives here, but I think you would like
to make changes to ox-html.el that would address the bug report/feature
request I sent. If so, read on.
The problem is that in situations where the HTML exporter produces two
tables of contents, it gives them both the same ID. That makes the XML
invalid, breaks some linking, and tends to choke XSLT processors.
I suggested three different strategies for the ID:
1. A detailed schema (see original email)
2. Allowing user to designate the ID
3. Just adding a sequence number to the end
Of these,
1 would probably be the hardest to implement, but would
provide the most accessibility for users and post-processors.
2 would probably be the easiest to implement, but would have the problem
that users wouldn't know they had to do it until something didn't work.
3 is probably the easiest to implement, but with the lowest utility.
My personal choice would be for both 1 and 2 to be implemented, but as
I'm not doing the work, that might be too much to ask. Just doing 3
would make the XML valid again (in these cases), and would be good
enough for now.
So, if you're looking to implement a solution, 1 and 2 please, or 3 if 1
and 2 are too much work right now. If, on the other hand, you're just
trying to find a way to make my suggestions sound dumb, please see my
previous e-mail.
Best regards,
Terry
--
T.F. Torrey
prev parent reply other threads:[~2013-03-06 21:26 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
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 [this message]
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=87k3pkz0k4.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).