Consider Paul’s opinion to be widely shared. Adobe’s management of EPUB is a joke and it is eventually doing a lot of harm to the standard…

Because they –wrongly — thought EPUB could just be an export option, it is really really bad. And because it is bad, it has a huge impact on the whole ecosystem, with eReading apps developers having to deal with the unmanageable. As a matter of consequence, those devs have to alter styles, and in some cases, alter the entire file so that it is not unreadable.

InDesign even export styles that Adobe’s own RMSDK doesn’t manage. That is pathetic, especially as their RMSDK is used by the vast majority of apps, vendors, etc.
In other words, InDesign isn’t even adapted to the RMSDK which prevails while the same company is making both of them.

Adobe and its evangelists are boasting they offer the best tools? Concerning EPUB, they are just screwing the whole ecosystem.

And designers and publishers are not so much guilty in this case, they just don’t know. It’s Adobe’s fault because it is telling them there is no ebook problem, just export and voila. Well, it is definitely not, and ebooks have their own design requirements. Had Adobe’s been honest, it should have released an EPUB prod app with inDesign compatibility. And now, what are they doing? Building a bridge between InDesign EPUB and dreamweaver… It’s like admitting InDesign failed to manage EPUB but still making the bad decisions: ebooks are not an hybrid of print and web. Never.

So please Adobe, stop making harm and start being serious about ebooks. At the moment, you are just an insane problem which is pushing the EPUB standard to its long and winding death.