Quote:
Originally Posted by PeterT
Not that it means a great deal, but I just created two test eBooks, identical save for the internal UUID and calibre-id fields, (well that is apart from the Titles!), added them to calibre, polished one, left one as raw work of art, sent them both via CC to a Nexus 7 with the Nook app. installed (and let me say that was fun getting it installed for a non US / UK IP address), and saw the cover's of both books within the Nook app.
The image for the cover in each book was flagged with the "cover" attribute, and the image was NOT referenced within an (x)HTML file.
After the polish, the cover was now referenced by an (x)HTML file which itself was flagged with the "cover" attribute, instead of the original image.
Attached find the two ePubs; maybe see what happens with these on the HD+. I've attached the ePub being polished in both it's raw and polished state.
|
Hi,
Peter thanks for the files. I sent your polished file to my Nook HD+ via Calibre Companion & the cover showed up. I then removed that file, loaded your unpolished file on my laptop, ran polish on it & sent it to the HD+. No cover image & the file looks untouched (eg just like the unpolished file.) It does not look like the Polish function is having any affect at all. I tried the same thing on my Nook Color. Same result. As mentioned I have Win 8 & the latest version Calibre. I know you sent the file to Calibre from your Nook app instead of direct as I did but I don't know if that makes a difference. I don't use the Nook app. This is what has been happening all along.
I don't think it's the Nook as the Nook accepted your Polished file fine. It's just not working when I try to use it on my laptop. Running Polish seems to have no affect on the file itself. This is not a "sometimes" thing. It looks on the computer like the cover was changed or added but goes "naked" when transferred. The only other program I'm using is MS Office, Chrome & IE. My antivirus is McAfee but I don't see where any of this would create a conflict.
It's still a mystery but it may be a software problem not a device issue.