View Single Post
Old 06-14-2022, 10:44 AM   #178
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,172
Karma: 148951761
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by icallaci View Post
I'm reading kepubs on a patched Ellipsa. The spaces within words using geometricPrecision are much subtler than with optimizeLegibility, but the spaces are definitely there. The most noticeable cases occur immediately before a span (not necessarily a kobospan; italics or bold also cause the problem). I'm satisfied with the way geometricPrecision handles it, so I won't be delving into it any further. I'd rather read.
I convert italics and bold that are done with spans into <i> and <b>. Could this be why I am not seeing this spacing irregularity?

The KePub I am reading now, I've made no changes to since the KTE driver converted it.
JSWolf is offline   Reply With Quote