Thread: suggestion - kepubify: optimize spans for compatibility with text-modifying plugins
View Single Post
Old 05-16-2025, 05:02 AM   #4
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: 46,608
Karma: 169712392
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by JSWolf View Post
What you are doing is not Intellireading. It's actually Bionic Reading. https://bionic-reading.com and Bionic Reading is pure BS. It doesn't work. It just makes it harder to actually read.

If you want to use Bionic Reading, have the plugin do the modification to an ePub eBook and then use calibre to convert to KePub from there. Problem solved.
Reading his original message, what he wants is for Kovid to add special case logic to hand the mass of <b>....</b> that are added to the code. He claims that those extra spans added around the <b>s are causing out of memory errors and slow chapter turning. I did test his plugin with an ~1.4M word omnibus and could see little difference in performance when I send any of the 4 variants I generated to my Sage. According to running free -m from NickelMenu, none of the 4 variants caused even close to an out of memory issue.
DNSB is online now   Reply With Quote