Quote:
Originally Posted by jackie_w
This is where my 'can of worms' sensor went off...
|
Quote:
|
... seems to allow for auto-incorporating what would normally be applied via a patch.
|
Yes, for the full screen patch, but many people were irrationally afraid of patching. You should see some email discussions I had... As for the CSS inlining, this cannot be fixed in a patch.
Quote:
|
... seems to be a prime candidate for conflicting with the 'Modify CSS' option in the KT/KTE drivers and the Hyphenation option in KTE.
|
You do realize kepubify is originally made to be used standalone without Calibre. Just because kepubify has a feature doesn't mean I'll expose it to the Calibre plugin.
Quote:
|
If there are a well-defined set of problems with a source book why fix the kepub? Why not fix the source instead? That's what the Modify Epub (ME) and Quality Check (QC) plugins were supposed to be for.
|
A few reasons:
1. Some only affect the Kepub renderer
2. Too many people complained (I'm looking at you, self-closing title/script tags...)
3. Clearing up those issues during conversion helps eliminate them as sources of issues
4. Many people are lazy/don't know how/can't fix or recognize these issues
Quote:
|
... again, if there is MS/ADE/iBooks cruft in the source why not remove it from the source using ME or QC or even a new bespoke Kobo-centric epub modifying plugin?
|
Again, those don't need to be included as an option in the plugin, and kepubify is meant to be used standalone.
Quote:
|
For the "calibre cruft" (very subjective), won't the calibre send-to-device process put it all back in again in the on-device kepub? If you're talking about removing it only from the calibre library kepub then that might be useful if you wanted to manually edit the kepub because the OPF file is very unwieldy with all the custom metadata included in there. OTOH only a masochist would want to manually edit a kepub because of all those KoboSpans - even if you could open a .kepub file extension in the calibre Editor - which currently you can't via the GUI.
|
I'm crazily nitpicky about extra metadata/CSS classes/elements/nonsense in my ebooks, but that's just me.