Quote:
Originally Posted by droopy
1a. What's the fastest/easiest/recommended/best/automatic way of figuring out which epubs are poorly constructed or malformed?
|
Idunno about best, but the easiest is to try to open it and worry when it takes more than 4 seconds.
[QUOTE]
1b. What's the easiest/fastest/best/automated way to fix a poorly constructed or malformed epub?
[/QUOTE
Except for javascript, the calibre conversion process seems to fix almost all of the problems that I've seen.
Quote:
|
2. I assume that javascripts in epubs are useless, yes? Epubs are static documents and javascripts are dynamic stuff that are not supposed to be in epubs/ebooks in the first place, right?
|
I don't know why javascript makes the kobo crash. It shoudln't be running it. It should just ignore it. Maybe the parser can't handle it or something, or maybe it is trying to execute it.
Quote:
|
2a. What's the fastest/easiest/recommended/best/automatic way of figuring out which epubs have javascript in them?
|
I would think quality check could do that, but I don't know if it does.
But it's almost faster to just run the tools to delete it.
Quote:
|
2b. What's the fastest/best/easiest way of removing (automatically, preferably) javascripts from all epubs?
|
I might be mistaken but I think both Polish Books and Modify Epub have options to remove it. But I seem to sometimes find embedded javascript even after running those and end up removing it by hand.
Most epub's don't have javascript in them. But if you build an epub from a web page, more than likely, it does.