Quote:
Originally Posted by KevinH
That makes sense. If you look at KindleUnpack debug output run an azw3 (KF8) that uses an svg with image inside an xhtml file, you will see that Amazon has pulled out the svg into its own section. It always does this. This creates an artificial page break. The KindleUnpack code has to find the extracted svg and put it back inside the xhtml file when trying to unpack to epub from an azw3.
|
Our experiments--not in the depth of Kevin's, of course--indicate that this is right, also--always breaks after an SVG. It's sort of put us off using SVG for interior graphics for KF8 books. Bummer.
Why we were looking at it:
Spoiler:
We've had a BIZARRE graphic issue this past week, with screenshots from a specific website just degrading dreadfully in MOBI/KF8/7. It's befuddling all of us. It's not the image--works fine in ADE, of all things, iBooks, etc. We suspect that something is going amiss with the KDP compression settings, maybe. We've tried re-taking the screenshots, reprocessing them, using everything from JPG to GIF to PNG to PNG8 to...blabbety, hell, even tried TIFF, changing the compression settings, and NOTHING is working. Thus, we really wanted to think about SVG, but...not with the page-breaking issue.
Hitch