|
Real ebooks don't have javascript. It's only needed for Interactive.
Google are totally fine with epub2.1 and AFAIK only do anything to the ebook if you ask for DRM. DRM is evil and doesn't stop commercial pirates. Only limits regular users and creates nasty walled gardens.
If you can't do a good ebook in epub 2.1 that seems nearly identical on KF8 Kindle then either you are doing it wrong or should use a framework and create iOS and Android apps. Certainly anything more than static text + static images needs an app. The epub3 and HTML5 is too limited and also awkward to distribute as you don't know how compatible any epub3 app or Browser might be.
If something seems to go wrong at Google, then you are doing something to clever or wrong.
Run the two checkers in the Calibre Editor.
Upload epub2 to Smashwords and see if it meets standard for Premium Catalogue.
Upload epub 2 to Amazon KDP and see if it passes.
You can set release date nearly a year away on both and then cancel (gives a bad rep) or unpublish later if you want.
Google is practically the least fussy, though they do check. They'll spot invalid ISBNs. I've never seen evidence of Google changing the ebook, but I don't know how they add DRM. Likely that just encrypts it without changing anything, but we NEVER request DRM, so I don't really know. The ONLY thing ever I've seen with Google is complaints about the metadata.
|