Ebook Format Wars: Adobe Disagrees
- Adobe’s RMSDK is difficult to access, even for licensed developers
- Kobo devices have a more advanced rendering engine for .kepub.epub files
- Epub 3.2 has made existing epubs non-conforming due to changes in HTML and CSS specs
The Buzz Score
The Internet’s Verdict: 70% Hyped, 30% Skeptical
Forum Voices
Developers and users are frustrated with Adobe’s handling of ebook formats. One developer notes:
Adobe has always been like this, too. They squandered an enormous marketshare with Flash because the alternative would’ve been spending a couple million on QA and they managed to unite all of the browser manufacturers in agreement that the web was better off without such an unreliable partner.
Another developer tried to access Adobe’s RMSDK, but found it impossible:
There is no way to get access to it. I don’t mean the licensing cost is prohibitively expensive for an indie dev although I understand that to be the case as well. There is no one to talk to. The email listed on their website does not respond to anything.
Alternative Solutions
Some users have found alternative solutions, such as using .kepub.epub files on Kobo devices or running epubs through kepubify before transferring them to their devices.
Focus Keyword: Ebook Format
