Quote:
Originally Posted by FrustratedReader
I'd not dream of doing that!
So you think the dual format file works on all kindles?
I've looked at Kindle Previewer and KindleGen on a win7 desktop a few weeks ago.
1) I only use Linux day to day now for the last 2+ years.
2) I use a Kindle Keyboard and a Kindle Paperwhite 3 to 'Preview', I have used a Kindle DXG and a Kindle Touch (1?) in the past. I also use Calibre ebook viewer. I check epubs on phone apps, 2 x Kobos, a Nook and a Sony as well as the Calibre viewer.
3) The Amazon tools don't seem very good and their own upload processing of doc & docx produces a substandard old mobi and kf8/azw files. I have the two kindles on separate Amazon accounts, on separate browsers to separate countries to test what Amazon deliver, as well as download of the 'preview mobi' file for Kindle from KDP upload page. I'm not sure why they suggest emailing that to the kindle rather than USB transfer.
4) Uploading an epub2 from Calibre gives perfect mobi and AZW downloads. I convert in Calibre via Save As 'MS docx' import from LibreOffice Writer (5x or 6x makes no difference) results in epub files that look the same as original Writer document (edited & saved in odt). The resultant Amazon azw files are looking the same as epub publisher mode, and mobi look like a dumb font version.
|
I'm not sure you understand what's happening here. And I'm not sure, when you say "MOBI" (the "dumb font version") which version you mean, on what device.
As you seem to know, inside each MOBI are three files, basically; a copy of the source, whether that's an HTML zipped folder, or an ePUB, etc.; a KF7 mobi and a KF8 mobi. When you order a file from Amazon, what is downloaded to your device is what Amazon matches to the device. That's all.
Quite simply, your KK--which was, as far as I know, one of the last generation of eInks (not including the DX) that was strictly KF7 and was not updated to KF8--is showing you the KF7 mobi, period. That's why you don't see fonts or the like.
In terms of what you see, the TYPE of "conversion you see" can also be impacted by the mode you take to get it to the device. If you sideload it, you will probably see a more-advanced appearing file. If you send it via email, there's an excellent chance that it's going through the old PDS system, and rendering a KF7 only MOBI, although I thought Amazon had updated that. I've recently tested and seen differences between the two, still.
Moreover, if you're loading DOCX files to Amazon, you will NOT get fonts, at all. DOCX can't "carry" fonts for processing; to do that, you have to have embedded fonts in an HTML environment, whether that's ePUB or a zipped HTML folder with the font files. You're skewing the results by testing two completely different systems. If you load properly prepared files to Amazon--like an ePUB--you'll get the same high-quality mobis that you want. But loading a docx file to Amazon won't get you that, and comparing a docx-created file, from Amazon, to an ePUB/MOBI created by Calibre, is apples and oranges.
This entire conversation is moot, really. You can't upload AZW or AZW3 files to KDP. You can load docx or zipped HTML or ePUBS or MOBI files. In terms of Smashwords, given that they're already using the Calibre API, they'll process the file just as if you'd made it yourself.
BTW, if your ePUBs do not have embedded fonts, you won't get those, either. Just calling a font, in an ePUB, won't embed it. Same with mobi source files.
So, as I said, your divergent testing method is creating the "dumb font version" yourself. It's not Amazon's doing. It's yours.
Hitch