Hello Lex and Dan Thank you very much for your answers and explanations!
Yes, I can imagine very well that it is very tricky to handle this use case, but it is still a pity that AsciiDoc is not able to handle text which is explicitly marked as a :toc: Element anywhere in the hierarchy. For us, it's not at all a "well-established semantic" :-) We use it in technical documents when a table is the best solution to describe contexts and if we would like to have table lines listed in the :toc:, so that the reader is able to see that they exist and easily can find them. This offers us to have two advantages: the benefits of the toc and the advantages of the table. Of course, any table can be transformed into a sequential text, but then we lose the overview and readability. At least, this is a somewhat ugly workaround (the readers will ask us why we didn't have created a table). Thanks a lot for your support, kind regards, Thomas -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
