Quote:
Originally Posted by bookman156
I honestly wonder how someone finds out useful information like that and what it's ramifications are. I used to think designing for web browsers was a pain but that's improved considerably and they're free to test in. Here it seems one has no idea what the terrain is really like without asking a stack of pointed questions of people who've been looking at it for a long long time.
|
An epub2 ebook must have a NCX document. Period. End of discussion. It's part of the epub2 specification.
Just as an epub3 ebook must have a NAV document. It's part of the epub3 specification. An epub3 ebook can have a NCX document for backwards compatibility but it is not required.
Sigil can automagically generate a NCX from the NAV document for when epub2 compatibility is needed.
As for web browsers? My experience has been that most web browsers are designed to attempt to work around non-standard code found on too bleeping many web pages. Our corporate web pages are filled with code designed to attempt to allow our web pages to look half decent on Windows, MacOSX, Linus, iOS/iPadOS, various flavours of Android and the mass of different web browsers running on those OS that our web pages are viewed with.