Thread: Kepub format questions
View Single Post
Old 02-07-2019, 08:05 PM   #19
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by geek1011 View Post
It isn't so much what it doesn't do, but what it does do. It's more Calibre's fault than anything though (the extra stuff added). Also, the span logic in kepubify is slightly different, and seems to match up better.

Yes, I guess. My reasoning was that it does a lot more than needed for converting epub to kepub. One of my biggest pet peeves is the HTML and CSS mods calibre does, along with the additional calibre contributor[role=bkp] and calibre_user_meta_map (or something like that) stuff it adds to the OPF.
Most of that sounds more like a conversion than the driver. The driver should only touch the CSS except to add things that are in kepub and the hyphenation options. The changes to the HTML should only be the spans, and a wrapping div or two. The formatting of the code might change a little, but I don't think it runs a pretty print or anything over it.

Adding the custom column metadata is done anything that updates the metadata in the book. It's not pretty if you open the OPF, but it is well within the standards.
Quote:
Last time I checked, ebook-convert didn't work right from the command line with kepubs. Also, it doesn't play well when using it with many other small tools (it cannot use an arbitrary location as the kobo path, it cannot take css from the output of another tool).
I'll admit to not doing much scripting using calibre, so I haven't hit that. But, I'll have a look at the conversion to see what's up. But, this doesn't use the driver, it is using the input and output plugins.

The file path for the input and output can be specified, so I'm not sure what you mean there. And an extra CSS file can be supplied as a parameter.

But, a conversion is not what you want to do if you want complete control over the result.
Quote:
I'm aware of that; I've read the source code a few times before. I'm just simplifying it for the benefit of the average reader.
The hassle with that is there is confusion over the necessity of the KoboTouchExtended driver. Some people seem to think it is necessary, install it and then complain about what it is doing.
Quote:
I've never once seen the epub3 series metadata in the wild (but I've seen calibre series metadata, as it's almost a standard).
I haven't looked for the epub3 series metadata, but I'll have to look at the ones I have from Kobo and see if they are using it. And yes, the calibre series metadata is the closest thing to a standard for epub2. I tried to convince Kobo to read it some time ago, but they weren't interested. With the epub3 support, it might be time to try again.
davidfor is offline   Reply With Quote