View Single Post
Old 02-04-2022, 09:45 PM   #143
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,918
Karma: 6240958
Join Date: Nov 2009
Device: many
This thread is about ideas to help general users of Sigil and should not include things better done in a plugin, or outside Sigil as was stated in the thread.

Specific changes should be requested that help **multiple** users, not just things specific to your unique work flow.

Sigil will not be duplicating functionality of existing plugins. And all plugin code is available to be modified as needed, if you want changes.

The nav is updated by Sigil when Sigil is used to rebuild the Table of Contents, when semantics are added, etc. The Nav must be kept machine readable and follow the nav spec closely at all times. That said, heading tags and Sigil's Edit ToC tools can be used to make headings generate the Nav you want. Headings are always to right place to make changes for Accessibility reasons and any TOC (Nav, NCX) should be rebuilt from them.

Last edited by KevinH; 02-04-2022 at 10:15 PM.
KevinH is offline   Reply With Quote