[KevinH]

Hi,
Then what is the point of the playorder? If you have an id on the body tag, and list the chapter preamble separately, then the user can choose to see or not see that material.

So that the Table of Contents would show the following

Chapter 1 Preamble
   Chapter 1
      Section1
      Section 2
      ...

And then the playorder would make sense as would the link locations.

Otherwise, your link locations or playorder would be incorrect no matter how it was built. You can't have both correct at the same time without this structure, can you?

KevinH

Originally Posted by Peter Ahlstrom

I'll give an example.

So, I have a book where each chapter has some introductory text at the top of the page, before the chapter title. The chapter title is what is listed in the Table of Contents, but if a user clicks on that entry, I want them to see the introductory text before the chapter title. So the link goes to the top of the page, not exactly to the chapter title header text.

Now, that chapter has 3 subheadings in it. If they click on the 2nd or 3rd subheading, they will go directly to that exact spot in the chapter. Great.

But the 1st subheading is directly under the chapter title. The reasons I have for wanting them to see the page's introductory text are just as valid for the first subheading as they are for the chapter title. So I want clicking on the first subheading in the TOC to also take them to the top of the page, just as clicking on the chapter title does.

So does that help?

I could work around this Sigil error by having multiple a id= tags up at the top of the page. But that would be a workaround, not a final solution.

The basic point is that Sigil's Table of Contents GUI editor in this case is taking valid input data and creating an invalid toc.ncx. So it's a bug in Sigil.