Quote:
Originally Posted by shalym
Ok...so I guess I'm just dense, because I still don't quite understand. Is it because there is no actual conversion happening when your driver "transforms" an epub to a kepub, just a name change? Does this mean that I could get the same effect if I just changed the name of the book and dragged it over to the Kobo?
|
The extended driver doesn't just rename the file. It makes changes to code inside the file. But, it doesn't do this in the same way that a conversion in calibre does. It "simply" wraps each sentence in the book in a span with a specific id.
Doing a conversion to kepub will also do this, but it also does a lot more. The conversion will rebuild the ToC, split files inside the book, modify CSS and a lot more. It does all the things a conversion to epub would do, plus adding the spans.
The result is not the same. They might look the same when reading, but if you open the book code and compare them, they are very different.
Because of the above, I don't like using the word "convert" when talking about what the extended driver does. Calibre has a well defined conversion process, and the extended driver doesn't use it.
Renaming an epub to ".kepub.epub" will have it treated as a kepub. And it will open and probably look the same. But, the reading position and bookmarks won't work properly. The spans with ids are needed for this.