Quote:
Originally Posted by AppleTard
Hi, I'm sorry to resurrect this thread, but I thought it'd be better.
I've been using Calibre to create dual-mobi files for a while, in order to send KF8 files through the "Send to Kindle" app. When I download the book on my Kindle Voyager, it comes as an azw3 file.
The major issue with this approach (other than the missing covers) is that whatever Amazon seems to engage in some post-processing, and removes all "font-family" information. The problem is not with Calibre (I've inspected the file I sent, and the azw3 downloaded on the Kindle). I don't use embedded fonts or anything, just the occasional monospaced font.
Is this a known issue still, or am I doing something wrong?
|
Well, I'm really not quite sure what you're doing, as I don't use Calibre. I know that you
cannot load an AZW3 file at the KDP; don't really understand if you're
sideloading the file--the only way I know of to get an AZW3 file from Calibre on a Kindle--or if you only
think you are, and you're really sending the MOBI (effectively, a PRC file, non-dual MOBI) to the Kindle e-mail system, which then basically runs it through the KDP (like), and what you get out says it's an AZW3, but it's really a MOBI (prc) which doesn't support fonts.
Can you be more explicit? Here's what I can tell you:
even if you're doing it right, most folks will have their fonts stripped out at the KDP. Simply building files the usual way will result in stripped fonts. I don't think, from what you've described, that you are doing this the right way, as you can't load a dual-mobi made by Calibre at the KDP, as AZW/AZW3 isn't an acceptable upload format. So, I'm not comprehending a step here (due to my non-use of Calibre for conversion/loading). If you make it clearer, perhaps I can help.
Please clarify?
Hitch