Best epub3 fixed format readers?

[odedta]

People would get it from amazon (KF8), when I did my tests it was through USB.

I meant AZW3 Hitch :/

[Hitch]

Originally Posted by odedta

People would get it from amazon (KF8), when I did my tests it was through USB.

I meant AZW3 Hitch :/

odedta:

I'm trying to understand if you're saying that you're uploading an ePUB3 file directly to a KFire, and observing the result, or if you mean that you created an AZW3 file with Calibre, and are loading that directly to the Fire? Because what I was trying to say, earlier, is that you cannot upload an ePUB3 file to the KDP, have it auto-magically convert to a KF8 mobi that plays audio (or video, for that matter). Nor, as far as I know, can you create a KF8 mobi with audio, that is uploaded to the KDP, that will play on a Fire. Nor anything else, post-KDP-publishing.

If you build a KF8 mobi, using KPreviewer, with audio, you can build a file that would work on an iPad, in the Kindle reader therefor. You're saying that you build ePUB3 files with audio, make a mobi, that it's uploaded via Amazon, and it's working, as a KF8 mobi, delivered from Amazon?

Hitch

[odedta]

I was talking about creating an EPUB3 Fixed Layout file, then have it convert to AZW3 and transfer to Kindle Fire directly.

[JSWolf]

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.

Might not work if the flavor of fixed-layout being used is not compatible with KF8.

[Hitch]

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

[JSWolf]

How would Kindlegen handle an iBooks FF (cannot call it ePub3 as it's not) eBook in converting it? It should fail big time making the Mobi part of the eBook and even if not, it would look awful.

[Hitch]

Originally Posted by JSWolf

How would Kindlegen handle an iBooks FF (cannot call it ePub3 as it's not) eBook in converting it? It should fail big time making the Mobi part of the eBook and even if not, it would look awful.

It doesn't. We get requests for htis type of service all the time--"can you JUST convert my FF iBooks book to Mobi?," and of course, it can't be done, certainly not with a push-button. I had a guy with a 2gig (yes, two gigs) book he'd done with iAuthor, full of video (cooking/wine, etc) that thought we could just "make it" because, of course...well, Mac user. Not the kind of Mac user that user none is; the other kind. Everything "just works." So you should have some type of magic Calibre-program that can convert iBooks FF to MOBI.

Yeah, right. It's nothing alike. Other than setting viewports. After that...all different. I mean, of course: html, CSS, etc., but nothing similar.

I'm asking odedta because I'm genuinely confused by his posts. I simply still don't understand what he's saying. In concrete terms.

Hitch

[JSWolf]

From what I've read, fixed layout is non-standard and what works with one program mayy very well not work with another. So odedta's search for that one magical FF layout eBook that will just work is a fantasy and full of wishful thinking and pipe dreams and rose colored glasses.

It just doesn't work that way and for now, it won't work that way for a long time to come (if in fact it ever works that way). So odedta, the solution is to take this magical eBook and custom fix it for all those programs you want it to work in. You have to manually edit it for all of them. There is no way you can get it to work in iBooks and on a Kindle (or any kind). There is no way it will work in ADE 4 and iBooks and with a Kindle and I can name more things this magical eBook won't work with without you going in and making the changes so it will work. But you cannot have ONE that works in most cases.

[DaleDe]

However there is only one ePub 3 fixed format. All the others are not ePub 3 compatible. Read about Fixed layout ePub in our wiki.

Dale

[JSWolf]

Originally Posted by DaleDe

However there is only one ePub 3 fixed format. All the others are not ePub 3 compatible. Read about Fixed layout ePub in our wiki.

Dale

This is true and any program that doesn't work with it is not ePub 3 compliant.

[odedta]

Hitch, i'm super busy with work right now, when I have more time i'll try to provide you with an example.

[Hitch]

Originally Posted by odedta

Hitch, i'm super busy with work right now, when I have more time i'll try to provide you with an example.

Thanks. I totally understand about being busy with work.

@DaleDe: well, that sounds really good on paper, BUT: people want what is saleable, not what is ideal. Whether or not it's ePUB3 compliant doesn't interest them IN THE LEAST, at least, not in my experience. They wouldn't--and don't--care if Kobo's version is non-compliant, nor Apple's; they simply want books that work, on the platforms where they may be sold. Of course--that would be my experience, all things considered.

I don't know GooglePlay's position, by the way (vis-a-vis the wiki), on self-pubbing FF to their portal. I think you can, by calling it an "app."

Hitch

[DaleDe]

Originally Posted by Hitch

Thanks. I totally understand about being busy with work.

@DaleDe: well, that sounds really good on paper, BUT: people want what is saleable, not what is ideal. Whether or not it's ePUB3 compliant doesn't interest them IN THE LEAST, at least, not in my experience. They wouldn't--and don't--care if Kobo's version is non-compliant, nor Apple's; they simply want books that work, on the platforms where they may be sold. Of course--that would be my experience, all things considered.

I don't know GooglePlay's position, by the way (vis-a-vis the wiki), on self-pubbing FF to their portal. I think you can, by calling it an "app."

Hitch

I don't understand the googlePlay comment but the OP specifically ask for ePub3 which is why I made the comment on the title of the thread.

Dale

[Hitch]

Originally Posted by DaleDe

I don't understand the googlePlay comment but the OP specifically ask for ePub3 which is why I made the comment on the title of the thread.

Dale

Oh, I just meant, there was something in the wiki about what entities did/didn't have self-pubbing portals for FF. I was simply noting that as far as I know, you can self-pub a FF ePUB3 file to GooglePlay (a self-pub portal, for FF, in other words), by calling the FF ePUB3 file an "app." My comment was in reference to your reference to the wiki--that's all. ;-)

Hitch

[DaleDe]

Originally Posted by Hitch

Oh, I just meant, there was something in the wiki about what entities did/didn't have self-pubbing portals for FF. I was simply noting that as far as I know, you can self-pub a FF ePUB3 file to GooglePlay (a self-pub portal, for FF, in other words), by calling the FF ePUB3 file an "app." My comment was in reference to your reference to the wiki--that's all. ;-)

Hitch

OK, anybody can fix the wiki if you have a better way to say something.

Dale