View Single Post
Old 07-13-2025, 06:26 AM   #3319
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,500
Karma: 8065348
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by Gorcsev View Post
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.
chaley is offline   Reply With Quote