Quote:
Originally Posted by odedta
I was talking about creating an EPUB3 Fixed Layout file, then have it convert to AZW3 and transfer to Kindle Fire directly.
|
odedta:
That doesn't work. The fixed-layout elements for KF8 are completely and utterly different than the FF layout elements for ePUB3. If you make, for example, an HTML5/ePUB3 FF book now, for iBooks, (so, you have no page-flip animation, etc.) it will work there, Kobobooks, GooglePlay. BUT, you can't take that same code and make an Amazon FF book. While they have some similar DNA, that's about it. Not to mention, the aspect ratio is completely different as well.
I'm really confused by your posts on this. You stated that a KFire will display an ePUB3 beautifully "if you stick to the standards," but I still don't understand what you meant. Did you mean,
if you jailbreak a KF down to Droid, and use it as an
ePUB reader? If not, what did you mean? You told the OP that if she'd created an ePUB3 with an audio element, and it didn't play on the Fire, to report the bug to Amazon. I've yet to understand the "how" of how you are getting that ePUB3 file to a Kfire and playing it.
Because either the Fire was jailbroken, and you're viewing an actual ePUB3, in which case, this isn't relevant to Amazon, or, you're talking about an "AZW3" file, which is a Calibre-generated file, which has nothing to do with Amazon, OR, you meant a FF Amazon book--which can't be uploaded at the KDP. BUT:
Calibre doesn't support "conversion" on FF files, so...I honestly don't know how you are getting an audio-playing, working mobi (of ANY FLAVOR) onto a KFire device, in any fashion that has
any direct relevance to Amazon, or about which one could report a "bug." Particularly given that the KDP will strip any audio/video from
uploaded files.
Can you provide a sample mobi that does this? Or detail how you encoded the audio, and how you built the file? Using ePUB3 standards, as opposed to KF8-standards?
Hitch