Quote:
Originally Posted by rdoca
Thanks by the fast answer.
Well, this is a manual solution that works.
But, I believe that is equal job make the headers in html texts.
|
As Kevin explained, there are very legitimate reasons why you should be using heading formatting in the first place--it's not "only" formatting or how something looks. Headings are STRUCTURAL. They are intended to provide guidance, to the device, the firmware, etc. about what's what.
No software has the ability to look at, say, 2700 paragraphs of text and magically pick out the relevant structural headings and from thence, create an NCX or Nav. You have to give it SOME help and honestly, this is typically done at the word processing stage (Word, AWP, LO, whatever); then simply exported to HTML with the appropriate HTML tags (h1, h2, etc.) and then, in Sigil, you can simply use that to build your own NCX or NAV (or both).
It's a critical part, really, of understanding how ePUBs work and all that. It's something that should be done regardless of the later intended use, especially around accessibility. It's also important around usability issues--if you have headings and all that, you can easily and with pretty much 2 clicks, break the ePUB file into separate XHTML files, to reduce the load on the reading device. Much more efficient, better rendering, and all that.
Yes, if you haven't already done it, it's a bit of work NOW, but if you use headings and Styles (word-processing-wise or markdown or whatever you're doing) during the writing/editing, this is all pretty much a snap. Not to mention all the good things it does for you during that word-processing stage, as well.
HTH
Hitch