Quote:
Originally Posted by RbnJrg
As I told you before, doesn't matter if you use or not svg for a cover; anyway Kindle won't use it (AS COVER). Another thing is to use svg INSIDE the ebook. In this last case, the modern Kindle format (.kf8) will use svg but the old Kindle format (.mobi) won't. So, if you want that your ebook will be compatible with the .mobi (the old .mobi, for Kindle 1, Kindle 2 and Kindle DX) format, then you'll have to write a fallback in case you employ svg (and .svg is more, much more than a wrapper  ). |
The problem is, really:
How does it get there from here? If we are discussing COVER images, then you have a whole other issue, which is the supplanting of the (designed by the perfectly competent book designer) cover PAGE and image with the cover image that is uploaded by the user at the KDP. That's where the mascara hits the fan, because the "coverpage.html" page (for a quick description) goes bye-bye. Thus, where goeth all that good ol' SVG coding, she wondered???? Sadly, it goes to code-heaven, where perfectly good coding goes to die.
If we are discussing images in the book file itself, then, yes, you can use SVG, but as Ruben mentions, you gotta use a fallback, and width=100% absolutely is
not it. (And if you really want to see why, open any book with that coding on Kindle for PC or K4Mac on a honking big monitor, and go single-column/page. THAT's a real
doozy of an experience. Particularly if you're talking something wee, like a fleuron for chapter ends, or what-have-you.
Let me tell you: image use is something we're discussing rather heavily around here, ever since Apple came out a few months ago with its latest dictates, which forces the images to break (across pages) on ADE and many other devices (yes, I'm talking to you, Kobo!). The refusal of the vendors to adhere to ANY BLOODY REGULARIZED STANDARDS at all is just...headache city. And the whole, "cover-image as SVG" issue is one of them (the headaches).
Hitch