View Single Post
Old 09-28-2018, 07:57 PM   #6
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by kaworu1986 View Post
You guys are seriously awesome.

I'm going to give your solutions a shot as soon as I can.

A couple of questions for jcn363



How does that help? That is definitely not part of the epub standard.
Actually, it is part of the epub standard. They are flexible in how things are represented in properties. Some are general properties, and others are in specific namespaces. This is a calibre property. Everything else will probably ignore it. From my understanding, what you have defined is correct for epub3. The following defines which is the cover image:

Code:
properties="cover-image"
Quote:
I thought toc.ncx was deprecated in epub3 and one was meant to use nav.xhtml instead. Wrong?
The toc.ncx is deprecated in epub3, but, is still supported for backwards compatibility. There are still plenty of epub2 only devices and apps out there that need it. The RMSDK based epub renderer in the Kobo devices is one of them.
davidfor is offline   Reply With Quote