Quote:
Originally Posted by 1611mac
I never did close this issue so let me do so in case someone searches....
Evidently, some apps don't like the file/folder structure that is created by "Pages" epub output. A workaround is to place two covers as page one and two in Pages, defining page one as a cover on export, will give a cover in most all apps. Some apps see the actual cover, the others will use the second cover - (cover is named "cover.jpg" so it can be found.)
But... To actually fix the problem so Bluefire and other apps actually use a single "true" cover page I have to explode the epub and put all files (except the META-INF) at the root level. (Pages epub output has css folder, images, folder, the opt, and chapters in an OPS folder.)
So again, I put everything at root level and made appropriate path change in container file and covers worked fine.
|
So, what you are basically are saying that Apple managed to create ANOTHER program that do things to ePUB like they want. The more spec-following readers cannot handle the output of Pages. That makes is a faulty app in my book.