@pluma:
If you look at commercial epub3 books, you'll notice that almost all of them use separate html files for each chapter. This might be a leftover from a time when eInk readers didn't have much available RAM, but it'll also ensure a better performance on most modern eInk readers and ePub apps.
There are very few ePub3 capable eInk readers available at this time and the most frequently used epub3 app is most likely iBooks. I.e., if you limit your choice to epub3 books, only a limited number of readers will be able to read your book.
Also note that Sigil doesn't support nested sub-folders and'll automatically flatten them. That leaves only Calibre Editor, which
usually doesn't break ePub3 books, but doesn't have any dedicated epub3 features either.
As for the section tag, it's an epub3-only feature. AFAIK, only some epub apps for visually impaired readers actually use it.
Quote:
Originally Posted by pluma
Furthermore I am confused by the linking syntax which is a bit counter intuitive:
Code:
<section epub:type="chapter" aria-label="chapter" id="c01">
|
The section tag does not have a special "linking syntax,"
epub:type="chapter" is merely a
semantics attribute. Of course, you could link
to the section tag from the nav document or a regular HTML TOC.
Quote:
Originally Posted by pluma
I'd appreciate if somebody could provide a working example.
|
Have a look at the official
IDPF epub3 sample books. For example,
Shared Culture uses sections.