View Single Post
Old 07-31-2024, 11:40 PM   #9
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,518
Karma: 171313258
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Sirtel View Post
I'm pretty sure this wouldn't work. There have been lots of folks here over the years, asking the same thing, and I have never seen anything like that suggested by the calibre gurus here.
If you take a look at the Kobo forums, before he passed away, @davidfor backported newer Kobo devices into a modified driver called KoboTouch348. Others have since added other new Kobo devices to the code. There is a discussion of the KTE driver being modified to inherit from the KoboTouch348 driver instead of the standard KoboTouch driver to allow use of the on the fly generation of kepubs. See Kobo Touch Driver for calibre 3.48 for more about that driver.

In theory the same could be done for the Kindle driver and older calibre versions but so far the only person I'm aware of who was looking at doing so ended up moving to a new computer and the project got dumped into the bit bucket. As far as I recall, even the first step of backporting the driver from calibre 6.2's Python 3 to Python 2 hadn't been completed.
DNSB is offline   Reply With Quote