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? > 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. --
