Quote:
Originally Posted by NIRC
Thanks for the suggestions. I think I got partway to solving the problem by converting the epub (where the embedded fonts are about half the size of the originals, so I am guessing they are "obfuscated") to AZW. I then convert that to mobi by opening it in Kindle Previewer 3. When I export it and send it to my Kindle Fire, it displays perfectly. (I would add that it makes no difference if I choose "publishers fonts" or not.)
|
FWIW, that--that you didn't need to turn on Publisher Fonts--leads me to believe that you've embedded the font in such a way that it's forced on the reader--that they can't turn it off. If that's the case, you'll have to fix that before you upload it to KDP.
Quote:
|
When I then open that exported file in Kindle Previewer 3, it also displays correctly, though with the error message that it was "created with an older version of Kindle Generator that will not be supported in the future."
|
Yes, because, Calibre.
Quote:
So far, so good. But when I try to load it into the KDP internet site, it is rejected with the error message: "There was a problem processing your file." I repeated the generation process from scratch and tried again. Same results. (I would add that the size is well within the 650 megabyte limit.)
Any ideas?
|
Yes, but not one that's helpful, unfortunately. That's the message you get with a file that has a corruption or bad code issue and there's no simple error-message to deal with it.
It's likely the font, because despite your luck with it, obfuscated fonts cannot be used at KDP/Kindlegen. They won't build properly and whilst your earlier result seemed to indicate some success (not sure how), if the fonts ARE obfuscated, it won't/can't work. Now, it's entirely possible that they're not in fact obfuscated, but subset, but the bottom line is, you're guessing.
You're guessing, and we are, because you're using a process that does not get inside the code. This is the problem with how you're working--you're using InDesign, which tells you nothing, really; then you're using Calibre, which is "push button" without you having to know anything and now you have a result that doesn't tell you anything.
I'm sorry, but you're asking us all to play Pin the Tail on the Troubleshooting. Can't be done like this.
Hitch