[Psymon]

Originally Posted by RbnJrg

How did you declare your custom fonts in your .css stylesheet? Are you using those fonts in your SVG images? This is important because to see custom fonts in SVG images you need to do some extra steps.

Oh, my apologies, I guess I'd gotten off-topic here -- at least, from the original subject heading of this thread. The book that I'd been trying out in KP was my first book, where I use a fair number of full-page SVG images (but with no text overlaying them or anything). It's for my second book that I was trying to figure out how to do full-page images with text on top -- and hence this thread (how it started, anyway) -- but this point, if that won't degrade well in older/"plainer" versions of Kindle, I think I might just totally scrap that idea completely and just come up with something simpler for all my chapter titlepages. It's a shame, but it just seems too problematic. :/

To answer your question, though, I did use custom fonts in those full-page images with text on top (as you showed me how to do) and didn't insert any extra font-related code -- and my embedded font showed up just fine in them! At least, in iBooks and ADE -- I haven't looked at that file in KP yet. And there doesn't seem much point in bothering now, since no doubt those chapter titles simply won't work in mobi -- and my book would be pretty silly if all the chapters didn't have chapter titles. :/

Like I said, I think I'll just come up with a simpler way of doing those chapter titles up -- and with any luck it'll still be nice, of course.

SVG are not supported by old Kindle models; but those ones can show .jpg images, so still you have a chance in order that people with old Kindles can see your pictures.

Um, I know I can specify CSS classes and stuff to differentiate between kf8 and mobi devices, but surely there's not much that I can do about those full-page SVG images (even without text on top) so that they'll instead just be simple images inserted in the page?

If there is a way, I wouldn't know how to go about that. My full-page SVG images are reasonably hi-res (basically they're all 1200x1800 in size), but if I wanted them to show up in a "simpler" device, I suppose I'd then also have to include a smaller version as well? I really have no idea! I had pretty much resigned myself to those full-page images showing up nicely -- if not perfectly -- in iBooks, ADE and kf8, but not at all in mobi devices, and just figured that that was what I'd be stuck with.

The ".mobi" file generated by Kindle Previewer contains two types of files: a .kf8 (in order to be read for the modern models of Kindles) and a "properly" .mobi (the old kind of mobi) in order to be read for Kindle DX and the older Kindle devices.

Ah, okay! That explains why my mobi version was essentially twice the size (filesize-wise) as my epub version.

That, or to use Kindlegen to convert your .epub in .mobi. Both ways are correct.

Um, that's the same thing as just opening the file in KP, isn't it? When I do the latter, it says that it's converting it using KindleGen.

Yes, to me that is what you should do. But remember that all what you declare under "@media amzn-mobi" will be applied for Kindle DX and older Kindle models, NOT FOR KINDLE PAPERWHITE.

Oh, is Paperwhite kf8? Or something else? I still don't know why my embedded fonts weren't showing up in Paperwhite (in KP), since both you and Hitch said that they should have shown up.

Is there some code that I have to insert (like I had to in order for my fonts to show up in iBooks)?

Thanks again, Rubén!