View Single Post
Old 08-04-2013, 04:04 PM   #34
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 31,156
Karma: 60406498
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by ibu View Post
@theducks

Good hints, thanks.
I think, I prefer a text area free of an inline TOC.
I like it, when a TOC is accessable with the same command, in the same look, in every book.

Back to the cover:
Isn't it enough to have a cover.jpg inside the epub container to provide the cover at the right place in the kobo (or other modern readers)?
In other words: get rid of a an redundant cover.xhtml?
Modern?

Not all readers work the same.
If I did not have some sort of Cover page (Usually from Calibre: Jacket.xhtml), I would not see a cover. EVER
Other device won't display a cover unless the Image is also tagged as cover in the guide.
Back to KISS having a cover.xhtml AND image with Cover symantics set works in most cases.
Kobo would like you to think THEY were the only reader maker.
Apple thinks THEY are it Amazon say that both the others are wrong, WE are the Gorilla of ebooks

Pick your poison.
Working with the most devices seems to win over making the most lean and elegantly coded book
theducks is offline   Reply With Quote