Quote:
Originally Posted by KevinH
Again, as I wrote before, I created an epub3 using Sigil. I added a cover image file and properly manifested it and properly identified it in the opf metadata. No iTunesArtWork file exists.
This cover nicely shows in the Finder on macOS, and when I e-mailed it to my iPad and stored it in Books, the Books library shelf shows the cover. On the iPad Books read my epub the first time it was added and it created the iTunesArtwork file copying my epub's specified cover image. The same image file is there under two names. One the original image name manifested properly in the opf, and the second a iTunesArtwork file created and added to the epub to make accessing that image again and again much faster.
I tested this from scratch with my own epub created in Sigil on my macOS machine, and transferred to my iPad and opened in Books.
If you are seeing something else, then I am not sure how or why. The iTunesArtwork file is created based on what you tell it the cover image is, the very first time you load it in Books. Removing that file hurts nothing, as it will be properly recreated by Books the next time. If yours is not being recreated, then the issue is probably in the original epub missing something in the opf.
|
Caveat:
I COULD BE WRONG HERE and misremembering.
However, my recollection is that the iTunesArtwork file is the cover (the
marketing image, displayed on the iBooks website/app), that is uploaded by the publisher, with other metadata, the ePUB file, etc., via iTunes Producer and/or the in-browser upload to The App Formerly Known as iBooks.
And that
if there is an in-ePUB cover, in the usual ePUB2 way, and the iTunesArtwork cover, the
latter takes precedence for display on the bookshelf.
Anyway...I could SWEAR that's the thing here. And that you can then utterly ignore the iTunesArtwork file, if you simply manifest the "real" cover.
Tex? Are you around? Quoth? Ruben? One of these guys will know better than I, as my "mechanical" bookmaking days are a bit past. I mostly send emails these days, but...I could
swear that's what that is.
And BTW, we make ebook files with unmanifested iTunes crap all the time. Finish the ebook, slap it in there and Bob's-yer-uncle. Apple makes this nonsense unavoidable, esp. around fonts. (They swore, 6 years ago, "nooo, you don't need this for fonts to work any longer," but they (Apple) lie like Catholic school-age altar boys caught with the Sacramental Wine on their lips.)
Anybody else here remember this?
Hitch