View Single Post
Old 11-27-2011, 09:06 PM   #13
1611mac
eWanderer
1611mac ought to be getting tired of karma fortunes by now.1611mac ought to be getting tired of karma fortunes by now.1611mac ought to be getting tired of karma fortunes by now.1611mac ought to be getting tired of karma fortunes by now.1611mac ought to be getting tired of karma fortunes by now.1611mac ought to be getting tired of karma fortunes by now.1611mac ought to be getting tired of karma fortunes by now.1611mac ought to be getting tired of karma fortunes by now.1611mac ought to be getting tired of karma fortunes by now.1611mac ought to be getting tired of karma fortunes by now.1611mac ought to be getting tired of karma fortunes by now.
 
Posts: 523
Karma: 1441998
Join Date: Jul 2010
Location: NC, USA
Device: iMac,iPad3,iPhone5-Kindle Fire,Touch,PaperWhite
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.
1611mac is offline   Reply With Quote