Replace KA1 header

[shalym]

Originally Posted by davidfor

As I said, the extended driver doesn't add the kepub to the library. But, if there is no suitable format to send to the device, calibre does a conversion when you send the book. The second screenshot shows the list of formats you are allowing to send to the device. As that doesn't include epubs, whenever you send an epub, it will be converted to the first format in that list. That format is kepub. Hence, every time you send a new epub to the device, it is converted to an epub, saved in the library and then sent to the device. And because you are converting the books kepub, you aren't actually using any of the features of the extended driver. Or at least none I can think of.

Ok...so I just tried sending a book that was already in epub format, and it didn't save a kepub in my library, even though it sent a kepub to the device. When I send a book that is in .azw3 format, however, it saves a kepub in my library every time.

Shari

Shari

[davidfor]

Originally Posted by shalym

Ok...so I just tried sending a book that was already in epub format, and it didn't save a kepub in my library, even though it sent a kepub to the device. When I send a book that is in .azw3 format, however, it saves a kepub in my library every time.

Which means your list of formats for the device has kepub at the top, includes epub and doesn't include AZW3. The epub is transformed to kepub by the extended driver and sent. The AZW3 is converted to kepub as it is the top in the list. Then the driver sends the converted book.

[JSWolf]

delete post

[shalym]

Originally Posted by davidfor

Which means your list of formats for the device has kepub at the top, includes epub and doesn't include AZW3. The epub is transformed to kepub by the extended driver and sent. The AZW3 is converted to kepub as it is the top in the list. Then the driver sends the converted book.

Yes...and it also saves the kepub in my library. According to you, it shouldn't be doing that.

Shari

[davidfor]

Originally Posted by shalym

Yes...and it also saves the kepub in my library. According to you, it shouldn't be doing that.

Wanna bet?

And to state explicitly what will happen:

If the driver is configured to send both epubs and kepubs, if you have an epub and no kepub, the extended driver will transform the book to kepub during the send and not save it in the library.

If you send a book that doesn't have a format in the supported list in the driver, it will be converted to kepub (or the first on the list) and then sent. The driver is not involved in this except to specify the formats. The kepub will be saved in the library as the conversion happens first, then it is sent to the device. For this, it doesn't matter whether you are using the extended driver or the built-in KoboTouch driver. And all the other devices work the same way with the formats they support.

If you have a kepub in your library, it is there because a conversion happened, not because the extended driver did something.

[shalym]

Originally Posted by davidfor

Wanna bet?

And to state explicitly what will happen:

If the driver is configured to send both epubs and kepubs, if you have an epub and no kepub, the extended driver will transform the book to kepub during the send and not save it in the library.

If you send a book that doesn't have a format in the supported list in the driver, it will be converted to kepub (or the first on the list) and then sent. The driver is not involved in this except to specify the formats. The kepub will be saved in the library as the conversion happens first, then it is sent to the device. For this, it doesn't matter whether you are using the extended driver or the built-in KoboTouch driver. And all the other devices work the same way with the formats they support.

If you have a kepub in your library, it is there because a conversion happened, not because the extended driver did something.

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?

Shari

[davidfor]

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.

[trekk]

Originally Posted by davidfor

As I said, the extended driver doesn't add the kepub to the library. But, if there is no suitable format to send to the device, calibre does a conversion when you send the book. The second screenshot shows the list of formats you are allowing to send to the device. As that doesn't include epubs, whenever you send an epub, it will be converted to the first format in that list. That format is kepub. Hence, every time you send a new epub to the device, it is converted to an epub, saved in the library and then sent to the device. And because you are converting the books kepub, you aren't actually using any of the features of the extended driver. Or at least none I can think of.

Thanks for the explanation. You are absolutely right, I must have unchecked epub without thinking about the consequences. I have extended the list of formats allowed to be sent to the device to epub and kepub. Now no more kepubs are added to the Calibre library.