emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: "T.F. Torrey" <tftorrey@tftorrey.com>
Cc: emacs-orgmode@gnu.org, n.goaziou@gmail.com
Subject: Re: [new exporter] [html] Tables of Contents
Date: Thu, 07 Mar 2013 13:27:23 +0530	[thread overview]
Message-ID: <87ehfr3an0.fsf@gmail.com> (raw)
In-Reply-To: <87fw08yztb.fsf@lapcat.tftorrey.com> (T. F. Torrey's message of "Wed, 06 Mar 2013 14:37:52 -0700")


> My request was merely for valid XML ID's for tables of contents from
> the HTML exporter

I understand the request but I will not comment upon whether or not it
will be supported in the exporter because that would be Nicolas call.
He has to work out the details not only for HTML exporter but also for
other backends.  It will take time and you need to argue your case
convincingly. There are going to be questions stupid and intelligent
which you need to be willing to answer.

> given that most of the XML tricks in my bag depend on valid XML input.

Given the current limitation of HTML exporter and since you say that you
are comfortable with XSLT, I was merely asking whether or not you see
any problem with this.

   Final Document = Transform(Subtree-Export) + Transform(Subtree-export)

Each transformer can rewrite TOC IDs and you will valid HTML export.
You may or may not wish to answer my questions.

ps: I still think that duplicate TOCs was an error on your part, meaning
it was un-intentional.  Can you convince me that it was really
intentional.  HTML export is not intended for books and I still cannot
understand why two TOCs are needed.

Jambunathan K.

  reply	other threads:[~2013-03-07  7:57 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 [this message]
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=87ehfr3an0.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).