View Single Post
Old 08-23-2018, 02:54 AM   #15
slowsmile
Witchman
slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.
 
Posts: 628
Karma: 788808
Join Date: May 2013
Location: Philippines
Device: Android S5
@Doitsu...Yes, I use bk.id_to_href() all over the place in my plugin to get file names.

But I tried an experiment. In a valid epub, I changed the cover file refs from "cover" to "noddy" in the metadata, manifest and spine. And when I ran Epubcheck the epub passed without any problems at all which surprised me. The point I'm making here is that those cover ids can really be anything you like -- they don't have to be "cover" and as long as those cover ids -- any cover id from any doc-to-epub converter -- are implemented in the metadata, manifest and spine then your epub will be valid. This also means that epub converters can indeed use other cover ids besides "cover" in the epub if they want. Like I said, this surprised me because searching for the metadata cover ref using "cover" does not seem to satisfy the maxim "in all possible test instances".
slowsmile is offline   Reply With Quote