Quote:
Originally Posted by AcidWeb
EPUB2 is no-go. Kobo reader can't use full screen graphic there.
|
True, but it can display the book. But, I wasn't thinking of the Kobo for this. I was thinking that your tool claims to generate this and having a sample would allow people using other epub ereaders to get an idea of how it is displayed.
Quote:
Fun fact straight EPUB3 will not work too. I have template and generic CSS that work on Kindle and other readers but it fail to render properly in Kobo kepub reader. I had to include separate templates for Kobo output.
|
Again, I was thinking for of this for other ereaders. But, I was going to compare the epub 3 with the kepub. And I'm more interested in doing this now as I expected a straight epub 3 to work. Maybe not as well as the tweaked version you are producing as a kepub, but it should work. And I think the version of the RMSDK that the current Kobo firmware uses has some support of epub 3. I'm curious to see how that works.
Quote:
Logic of auto adding toc entries when proper toc is included escapes me.
|
It is stated in
https://github.com/kobolabs/epub-spe...f-contents-toc. That does make it look like it is only for epub 2, but it seems to be for epub 3. Or at least sideloaded epub 3. Maybe it is different if the epub 3 goes through the Kobo CMS.
I think this is done because the rendering, page calculation and time reading calculations are done at the internal file levels. The internal database has entries for each file in a kepub and stores some of these values against them.