From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jambunathan K Subject: Re: [new exporter] [html] Tables of Contents Date: Wed, 06 Mar 2013 09:47:14 +0530 Message-ID: <87obexb1rp.fsf@gmail.com> References: <8738wauvt0.fsf@gmail.com> <87txopzjgz.fsf@lapcat.tftorrey.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:57302) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UD5nD-0001mN-25 for emacs-orgmode@gnu.org; Tue, 05 Mar 2013 23:17:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UD5nC-0000Qr-13 for emacs-orgmode@gnu.org; Tue, 05 Mar 2013 23:17:26 -0500 Received: from mail-pb0-f41.google.com ([209.85.160.41]:45695) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UD5nB-0000Qg-RW for emacs-orgmode@gnu.org; Tue, 05 Mar 2013 23:17:25 -0500 Received: by mail-pb0-f41.google.com with SMTP id um15so5456921pbc.28 for ; Tue, 05 Mar 2013 20:17:25 -0800 (PST) In-Reply-To: <87txopzjgz.fsf@lapcat.tftorrey.com> (T. F. Torrey's message of "Tue, 05 Mar 2013 13:21:00 -0700") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "T.F. Torrey" Cc: emacs-orgmode@gnu.org, Nicolas Goaziou 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 (
). 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? > 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. --