Quote:
Originally Posted by JSWolf
Do you think converting from ePub > KePub and visa-versa might solve the problem with a bad book?
|
Converting epub->epub is more likely to fix it, as that rewrites a lot of the epub structures from scratch. However since we don't know what's causing it, there's no way to know if either conversion path would fix it.
If it turns out it's embedded javascript doing it, I don' t think either of these conversions removes it.
Do you have a book that you are sure is causing a drain?
It occurs to me that since we can do things like run shell scripts on the device, it should be possible to look and see if there is something chewing cpu and directly test this.