From mboxrd@z Thu Jan 1 00:00:00 1970 From: tftorrey@tftorrey.com (T.F. Torrey) Subject: Re: [new exporter] [html] Tables of Contents Date: Wed, 06 Mar 2013 14:21:47 -0700 Message-ID: <87k3pkz0k4.fsf@lapcat.tftorrey.com> References: <87ip5495pl.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:40846) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UDLqm-000331-IG for emacs-orgmode@gnu.org; Wed, 06 Mar 2013 16:26:15 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UDLqj-0005VY-My for emacs-orgmode@gnu.org; Wed, 06 Mar 2013 16:26:12 -0500 Received: from relay4-d.mail.gandi.net ([217.70.183.196]:41447) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UDLqj-0005Up-FS for emacs-orgmode@gnu.org; Wed, 06 Mar 2013 16:26:09 -0500 In-Reply-To: <87ip5495pl.fsf@gmail.com> (message from Jambunathan K on Wed, 06 Mar 2013 16:05:02 +0530) 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: Jambunathan K Cc: n.goaziou@gmail.com, emacs-orgmode@gnu.org Hello Jambunathan, Jambunathan K 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