View Single Post
Old Yesterday, 10:16 PM   #11438
JimmXinu
Plugin Developer
JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.
 
JimmXinu's Avatar
 
Posts: 7,136
Karma: 5005503
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
New Test Version Posted

2025-11-02
- writer_epub: Only do svg check for epub3
- writer_epub: More epub3 - prefix & prop cover-image
- Don't include default_cover_image with use_old_cover with a different name.



Quote:
Originally Posted by slimcat View Post
I did notice one small issue: the manifest item for the actual cover image loses properties="cover-image" during update. This happens with both SVG and non-SVG covers.
That wasn't losing on update, so much as FFF never wrote it at all. Added.

Quote:
Originally Posted by slimcat View Post
*Minor technical note: I also noticed that the update process removes the calibre prefix from the package header. This triggers an 'Undeclared prefix' error in EPUBCheck. From my understanding, there's no real functional impact, but just wanted to mention it.
Added.

While testing these changes, I also found that if you had both default_cover_image and use_old_cover set, and injected a cover (changing the cover name), FFF was still downloading and including the default_cover_image, just without anything referring to it.
JimmXinu is offline   Reply With Quote