Quote:
Originally Posted by graycyn
Can I move the nav.xhtml file to the front matter of the book and style it or is it best left strictly alone at the end of the book where it is now?
|
You can move it anywhere you want, but since ePub3-itizer adds a
linear="no" attribute, users can't select it in epub3-compliant apps anyway. Theoretically you could also style it, however, many epub3 apps will ignore nav.xhtml styles.
Quote:
Originally Posted by graycyn
Does the nav.xhtml header *have* to say Table of Contents or can I change it to just *Contents* like the actual book had?
|
You can change it to any text you like.
Quote:
Originally Posted by graycyn
Also, for books that just have chapter numbers, is it possible to restyle the nav.xhtml as an unordered list or will that mess up navigation?
|
No. You'll need to use ordered lists. (You could use CSS pseudo elements (e.g. :before and counter-increment) to add numbers to TOC entries in TOC.xhtml.)
You might want to consider leaving nav.xhtml alone and style TOC.xhtml instead.
BTW, there are hardly any advantages in converting epub2 books to epub3 books, unless you want to take advantage of epub3-only features (e.g. scripting, MathML, HTML5/CSS3 etc.).