View Single Post
Old 02-18-2024, 12:48 AM   #7
AlanHK
Guru
AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.
 
AlanHK's Avatar
 
Posts: 681
Karma: 929286
Join Date: Apr 2014
Device: PW-3, iPad, Android phone
Quote:
Originally Posted by KevinH View Post
And the cover images for each epub are cached by Book.app (iBooks) the first time an epub with that unique identifer is imported into Books.app.

So delete that epub completely from Books.app. Fix the metadata to properly identify the cover xhtml file and fix the manifest properties to properly identify the cover image itself.
It's not so easy to completely delete from Books app. It retains the metadata and if you import a new version of the book, it may try to use the original metadata.

E.g. it will bookmark the last page you were on and try to reopen on that page. If you have renamed the files in the ePub, it can crash when it can't find it. And other weirdness. Apple's way of punishing you for not buying from them; it will just fail rather than use a sane fallback.

Always use epub3, with epub2 it will never update things like the TOC from new versions.

If it appears stuck with old metadata, change the unique ID of the new version.
AlanHK is offline   Reply With Quote