Thread: [GUI Plugin] Modify ePub
View Single Post
Old 07-11-2015, 05:32 PM   #982
Rev. Bob
Wizard
Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.
 
Rev. Bob's Avatar
 
Posts: 1,760
Karma: 9918418
Join Date: Feb 2013
Location: Here on the perimeter, there are no stars
Device: Kobo H2O, iPad mini 3, Kindle Touch
Quote:
Originally Posted by JSWolf View Post
I've run Modify ePub on some ePub 3 that don't really use much in the way of ePub 3 features with no issues. I've not run Modify ePub on a full out ePub 3 as those aren't easy to come by and if they were, I'd not buy/download as I've no need for such.
I'm mainly concerned with how it works with the semantic EPUB 3 elements - SECTION and the like. Those are kind of "EPUB 2.5" books to me; a little more functionality, but nothing that breaks in an EPUB 2 application.

I wish I could think of a way to automatically detect and discard pointlessly-nested DIV elements. Several Baen books show this bug, in which the first chapter's contents are enclosed in one DIV, the next is wrapped in two DIVs, and by the end of the book, you've got thirty or more extraneous DIVs nested around the same kind of content. Removing them does no harm, and may improve performance in some situations.
Rev. Bob is offline   Reply With Quote