Quote:
Originally Posted by ibu
I looked at the nav.xhtml of the book "The forerunner" of the link you posted in the last #12. It's a bit far from minimal.
|
It might look a bit convoluted, but it contains just enough epub3 markup to pass epubcheck.
The easiest way to find out, what tags are required is to delete tags and run epubcheck afterwards. (If you use the
Sigil epubcheck plugin, you don't have to save files after deleting/adding tags, because the plugin will automatically grab the latest files.)
Quote:
Originally Posted by ibu
1 When the charset is declared in the xml element, is
necessary to declare it a second time in the meta element
|
AFAIK, they're optional.
Quote:
Originally Posted by ibu
2 Do we need to language declarations?
|
AFAIK, they're optional.
Quote:
Originally Posted by ibu
3 Do we need the CSS styles? Are the ebook devices not able to show a nice TOC without it?
|
CSS styles are not required and most epub3 apps will ignore them. (These styles are intended for epub2 apps.)
Quote:
Originally Posted by ibu
4 Should we place the heading "Table of content" inside the title element or in a h1?
|
Since
<title></title> tags are ignored by most epub apps, you might want to put
Table of Contents in a heading tag. BTW, heading tags (h1-h6) are optional in NAV docs.
Quote:
Originally Posted by ibu
5 For what are the attributes in the body and nav element useful?
|
Most of these attributes are mandatory in epub3 content docs. For details, see the
epub3 specs.