Thanks, Hitch and Rubén, for your replies! I'll respond to both your comments here, below...
Quote:
Originally Posted by Hitch
Did you say you'd viewed it in Kindle? Regular e-ink, or have they removed that now from Kindle Previewer?
|
I presume that's been removed. In KP, when I choose "Kindle e-ink" as my device, it gives me two options: Kindle Paperwhite and Kindle DX.
Quote:
|
Also: your embedded font should work on Paperwhite, if it's working on the Fire Devices. Fire and Paperwhite are K8.
|
None of my fonts show up in Paperwhite -- not in KP, anyway. I don't have any "real" Kindle devices myself, though, so I don't know what differences there might be between the previewer and the real thing.
On to Rubén's response...
Quote:
Originally Posted by RbnJrg
Yes, in Kindle Fire, Kindle Paperwhite, Kindle Touch, Kindle 4 No Touch and Kindle 3, your ebook should display very well (that is, because all those models support the .kf8 format). And Kindle Paperwhite should show the fonts you embedded. Something must be wrong with the procedure to do that (the custom fonts you are using, are they being employed in the SVG images?). Also you should see the ornaments in Kindle Paperwhite; again something should be bad with the used code.
|
I have absolutely no idea -- as I mentioned above, my fonts don't show up at all in Paperwhite (in KP, at least). If something went wrong, well, that's probably because I'm clueless!
All I did to convert the my book was open my epub in KP and it did the conversion to mobi for me. If there's any "tweaking" that should be done to the file(s) after that, I have no idea what those should be.
I remember that when I first made my original epub, I had to manually insert a "com.apple.ibooks.display-options.xml" file in there in order to get the embedded fonts to display in iBooks -- do I have to do something similar for Kindle, too?
Quote:
Yes, you can do that by using "media queries". It will take you a bit of work but you can achieve that things degrade gracefully. All styles you want to be used by modern Kindle devices, you must enclosed them between:
@media amzn-kf8 {
...
Here must be all styles for kf8.
...
}
And styles you want to be used by old Kindle devices must be enclosed between:
@media amzn-mobi {
...
Here must be all styles for mobi.
...
}
|
Interesting, I'll keep that in mind -- thanks! Rather reminds me of browser detection in web design.
I don't think the issues I'm having are with styles so much, though, but rather with figuring out how to deal with whether the fonts embed... or not. That shouldn't be too difficult to deal with, but what I'm not sure how to deal with at this point is the various full-page SVG images that I have. As my book is, I have a nice page giving credit for the illustrations -- "Illustrated with the paintings of Lucie LeBel". That page shows up just fine -- it's just plain ol' HTML -- but naturally it won't make sense to people if they then don't actually see any of those paintings!
Mind you, as I was writing this last paragraph, it occurred to me that perhaps you gave a solution that might work. With regard to those full-page SVG images, do they work in kf8, but don't work in mobi? Mind you, what I'm previewing here is a ".mobi" file -- I'm not sure if I get this.
But anyway, if that's the case, then I suppose I could include a class so that that line -- "Illustrated with the paintings of Lucie LeBel" -- is basically just hidden from view in mobi devices, and then people won't wonder why they don't see them.
Does that sound like a good -- and workable -- solution?
Quote:
Your ebook will work almost perfectly (with some adjustments proper for that kind of devices will work perfectly) in modern Kindle devices. Problems appear when you want to adapt the book for older devices  There, you can't have all the things you can have in the .kf8 format. But with media queries you can make the book perfectly readable for both types of devices
|
Quite happily -- and much to my surprise -- my book seems to come out pretty much perfectly in all the various Kindle devices (based on what I see in KP, that is), apart from the two e-ink devices (Paperwhite and DX). For these latter, I guess I just need to tweak my HTML/CSS files in order to get them to work/look okay.
With regard to converting my original epub (designed essentially for iBooks/ADE), is the only thing that I really need to do just simply to plop that file in KP and let it convert it, and that's basically it? Because if that's the case, then I wonder if I could just have my original CSS file (which would effectively fulfil that "@media amzn-kf8" need) and then add in that "@media amzn-mobi", with whatever adjustments are necessary.
Wouldn't I then have one, single epub file (as a "base" file) -- and not a whole bunch of different files/versions -- that I could upload to iBooks, etc. as well, and then easily convert for Kindle?
Know what I mean? Hope that makes sense.