Thread: What plugin(s) would you like to see?
View Single Post
Old 12-14-2015, 11:28 AM   #3
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 79,763
Karma: 145864619
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by KevinH View Post
Hi JSWolf,

How would you want it to handle the following:

nav document - keep it or discard it?

html5 specific tags - these don't exist in xhtml1.1 - keep or strip out, or comment out?

epub3 specific attributes such as data-* and epub-type and ...

smil, pls accessibility features - how would you deal with those?

javascripts - how should those be dealt with?

etc.

As you can see it is much easier to go from valid epub2 to epub3 since 3 is generally a superset of 2, but going the opposite way will be quite hard and could easily end up losing lots of pieces and functionality. I am not sure it can be done in any rational way unless the epub3 book used no new features over the epub3 set.

KevinH
There are a lot of ePub being made by publishers that would work as ePub 2 no problem. These are the ones I want to convert. You dump the NAV, edit the metadata so it's compliant, edit the OPF, remove <section> tags and basically, that's most of the work done. If it is a true ePub 3, then the plugin can say so.
JSWolf is offline   Reply With Quote