[Device Plugin] Kobo Touch Extended Driver

[JSWolf]

Originally Posted by Gorcsev

In the KoboTouchExtended (KTE) plugin, users had the ability to customize how the 'kobo spans' were managed. Could you kindly point me to where this functionality is handled in the KoboTouch driver now that the KTE "functionality" have been integrated?

thank you

Go to Preferences > Output options Select KEPUB output. The options you want are on the right side.

[DNSB]

Originally Posted by JSWolf

Go to Preferences > Output options Select KEPUB output. The options you want are on the right side.

If you meant Preferences => Conversion => Output Options? None of the options there seem to match with what @Gorcsev was asking about for controlling the span locations.

I suspect that since part of the design of the kepubify code for calibre was to give as close a match as possible to Kobo generated kepubs, those options did not make the cut.

[PeterT]

I wonder if the option Prefer improved text justification to proper highlighting might be appropriate?

[chaley]

Originally Posted by Gorcsev

In the KoboTouchExtended (KTE) plugin, users had the option to change the Python code to control how "kobo spans" were handled (for example, deciding whether each paragraph or each node should get its own span, and how spaces were managed, trailng leading span adjustments).
Now that these features have been added into the main KoboTouch driver, could you point me to the part of the code where this functionality is currently being controlled?

thank you

If you want to change the code in calibre itself, it is in src/calibre/ebooks/oeb/polish/kepubify.py. You will be responsible for propagating your changes whenever you update calibre.

If what you want to do is sufficiently generic, you might consider submitting the changes along with the options to control them to Kovid. In this case your code must not only make the changes but also be able to remove them.

[JSWolf]

Originally Posted by DNSB

If you meant Preferences => Conversion => Output Options? None of the options there seem to match with what @Gorcsev was asking about for controlling the span locations.

I suspect that since part of the design of the kepubify code for calibre was to give as close a match as possible to Kobo generated kepubs, those options did not make the cut.

That is how spans are managed. in the KEPUB output options there is an option for Prefer improved text justification to proper highlighting. That does dictate how spans are managed.

As far as a recall, there wasn't an option in the KoboTouchExtended driver on how the spans are managed. If I am wrong, please let me know.

[Terisa de morgan]

Originally Posted by JSWolf

As far as a recall, there wasn't an option in the KoboTouchExtended driver on how the spans are managed. If I am wrong, please let me know.

Yes, please, I don't remember it either, and checking the oild configuration file, I don't find information about it either.

[theducks]

Originally Posted by JSWolf

That is how spans are managed. in the KEPUB output options there is an option for Prefer improved text justification to proper highlighting. That does dictate how spans are managed.

As far as a recall, there wasn't an option in the KoboTouchExtended driver on how the spans are managed. If I am wrong, please let me know.

↑ ↑ ↑ ✔
(I tend to accept them as they worked. Not knowing all their usages is a good reason to not muck about)

[compurandom]

Originally Posted by JSWolf

Go to Preferences > Output options Select KEPUB output. The options you want are on the right side.

The option wanted is "Prefer improved text justification to proper highlighting" in the above changes how spans are inserted for kepub.. This is most likely what you are looking for.

[JSWolf]

Originally Posted by compurandom

The option wanted is "Prefer improved text justification to proper highlighting" in the above changes how spans are inserted for kepub.. This is most likely what you are looking for.

You are repeating what's already been posted.

[jiembe]

KoboTouchExtended option:

Use Template for kepubification
_________________

My Win7 PC can't be upgraded. Anyway, it's my hob for all multimedia in the house and work perfectly well. Why changing what is not broke.

And I don't need the last version of Calibre.

[JSWolf]

Originally Posted by jiembe

KoboTouchExtended option:

Use Template for kepubification
_________________

My Win7 PC can't be upgraded. Anyway, it's my hob for all multimedia in the house and work perfectly well. Why changing what is not broke.

And I don't need the last version of Calibre.

Why can't you upgrade your Windows 7 to Windows 10?

[DNSB]

Originally Posted by JSWolf

Why can't you upgrade your Windows 7 to Windows 10?

Jon, Jon, Jon, just in case you didn't notice this before, Windows 10 has different minimum hardware requirements than Windows 7 did. There was a good chunk of older Windows 7 hardware that did not meet the minimum requirements for Windows 10 at it's release.

Heck, I've seen computers running early version of Windows 10 that can't update to Windows 10 22H2 due to their CPUs no longer being on the supported list.

[PeterT]

Originally Posted by jiembe

KoboTouchExtended option:

Use Template for kepubification

That option is still in calibre 8 and above.

It's found in the Configure this device menu of the driver, on the tab labelled Collections, covers and uploads and is labelled Template to decide conversions. The help for the field reads

Enter a template to decide if an EPUB book is to be auto converted to KEPUB.

If the template returns false or no result, the book will not be converted to KEPUB. For example to only kepubify books that have the tag as_kepub, use the template:

{tags:str_in_list(\,,as_kepub,true,false)}

or to only convert books that do not have the tag as_epub, use the template:

{tags:str_in_list(\,,as_epub,false,true)}

If no template is specified conversion to KEPUB is controlled only by the setting above to use the Kobo viewer.

Note that the setting above must be enabled for the template to be checked.'

[Gorcsev]

Originally Posted by Gorcsev

users had the option to change the Python code to control how "kobo spans" were handled

I’d like to clarify that it wasn’t simply a matter of checking or unchecking a box.
As I mentioned earlier, we could modify the Python code to manage the Kobo spans differently if we wanted to. For me, one of the main differences was keeping entire paragraphs in one span rather than splitting them into smaller chunks. Those of us who made the code changes chose this approach because we were not satisfied with the formatting of the original spans.

Similarly, the leading and trailing spaces within the spans were managed in my code with the aim of improving the overall formatting and making it cleaner and more polished. As far as I know, this wasn’t implemented in kePubify.

Given the new approach, is there any way I can use parts of my old code to achieve this?

[chaley]

Originally Posted by Gorcsev

I’d like to clarify that it wasn’t simply a matter of checking or unchecking a box.
As I mentioned earlier, we could modify the Python code to manage the Kobo spans differently if we wanted to. For me, one of the main differences was keeping entire paragraphs in one span rather than splitting them into smaller chunks. Those of us who made the code changes chose this approach because we were not satisfied with the formatting of the original spans.

Similarly, the leading and trailing spaces within the spans were managed in my code with the aim of improving the overall formatting and making it cleaner and more polished. As far as I know, this wasn’t implemented in kePubify.

Given the new approach, is there any way I can use parts of my old code to achieve this?

I answered your question in this post: https://www.mobileread.com/forums/sh...10#post4524410