View Single Post
Old 01-18-2018, 05:54 AM   #31
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by cramoisi View Post
I agreed with that (the streching of the nbsp, i even post 2 links stating this).
Sorry, lost track of where we were up in the thread.
Quote:
My second screenshot only shows that where one's could think the space wrongly stretch in kepub, it's normal since they are normal spaces where it's should not.

And in the screenshot above (the third and fourth) I use a narrow-non-breaking-space and it stretches too. So there is no solution for that regarding kepub.

(I edit my post when you were writing your answer, could you recheck ?)
It's hard to see the difference in the the last photo. I'm also surprised the desktop application has gotten it right. My understanding is that it shares a lot of code with the firmware, and I would have expected the rendering engine to be one of them. Maybe the problem is in the underlying widget used to display the page.

And no, it doesn't look like there is a solution until someone convinces Kobo to fix it.
davidfor is offline   Reply With Quote