Quote:
Originally Posted by Rev. Bob
That may be 100% true, but it's also completely beside the point. The problem is the lack of a download button, remember?
|
What I was saying is that
at this time, official support for ADEPT DRM does not include any epub3 compliant renderers. Without removing the DRM, 3rd party epub3 renderers are going to have issues opening an ADEPT DRM protected file. An unprotected epub3 file is a different kettle of fish.
To quote from a Datalogics' Kevin McNeill: "Datalogics will be implementing this technology within the Adobe Reader Mobile SDK (RMSDK) framework so that our customers can deliver EPUB3 capable apps that work within the Adobe DRM ecosystem."
At this time, the delivery date has not even changed to "Real Soon Now".
You might also want to check an O'Reilly item from Feb. 2013 about the "joy" of moving to epub3. "double the metadata and double the fun" describing their epub2/3 compatible ebooks building process.
Quote:
Originally Posted by Rev. Bob
ETA: Also, since it appears that all new Orbit books are being built as EPUB3, this is not a problem that will simply go away. Kobo needs to fix their site, simple as that. Plus, the more big publishers/imprints start adopting EPUB3 (Orbit's part of Hachette), the more reason there is for readers to support it. Just saying "EPUB3 probably looks bad anyway" is completely unhelpful "sour grapes" thinking.
|
What I am saying is that an epub3 file making use of epub3's extended capabilities is not going to look good on an epub2 renderer. Yes, you can limit the use of epub3 capabilities but that removes most of the reasons for moving to epub3. This comment applies to non-DRMed publications. Given that no epub3 renderers currently support Adobe ADEPT DRM, opening an Adobe DRM protected publication is not an option.
For the heck of it, I purchased and downloaded two ADEPT DRM protected epub3 ebooks. Removing the DRM and examining the contents showed that other than the addition of the toc.xhtml navigation document and changing the version in the opf file to 3.0, the use of epub3's extended features was nonexistent. ADE/RMDSK displayed them in an acceptable fashion.
I then compared that to opening a sample epub3 book making use of fixed layout, text direction, Javascript, embedded WOFF fonts, audio, etc. It did not include the toc.ncx for optional epub2 compatibility and so the book lacked a table of contents when opened using ADE/RMDSK. On an Aura HD, renaming it to .kepub.epub to force use of the ACCESS renderer, the book looked pretty good though for some strange reason, the audio portion didn't play.
OTOH, on my iPad, everything seemed to work without needing to rename the file.
I am curious as to how you managed to condense my "I'd suspect that any epub3 ebook that makes heavy use of epub3 features is not going to look all that good when read using ADE or RMDSK based readers" to the "EPUB3 probably looks bad anyway" you enclosed in quotes. My comment is not "sour grapes" rather being, in my opinion, a demonstrable fact.
Regards,
David