Quote:
Originally Posted by FrustratedReader
What difference is the regular driver and explicitly using the kepub output conversion plug in? Maybe time saving if you have a number of Kobo ereaders? Any other difference apart from the Extended Driver CSS option? I mean do both methods create the same kepub? Maybe not if one is using an existing epub as source and the other is going direct from docx / RTF / HTML etc, though maybe Calibre creates an epub first, I've not used the kepub output conversion plug in.
|
Firstly, the only CSS option in the extended driver is actually part of the built-in KoboTouch driver. There is a small change in how it works, but only in where it can get the extra CSS file from.
As to changing the book to kepub, the extended driver mainly wraps the text of the books in spans with the appropriate classes and ids. The conversion runs the full calibre conversion pipeline. That means it can change just about anything. But, it should be roughly the same as doing an epub-to-epub conversion followed sending the book to the device using the extended driver. It won't be identical, but I don't think the differences will be important.