Thread: [Device Plugin] Kobo Touch Extended Driver
View Single Post
Old 04-07-2016, 10:00 AM   #1487
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 patrik View Post
Exactly.

As can be seen in this video I made last time I asked about it here.
https://dl.dropboxusercontent.com/u/...ghlighting.mp4
That video tells me what is going on. Or at least one reason the highlights are disappearing.

If you look at the underline while the menu is displayed, the space before the sentence is selected. That's the problem. The kepub format has spans wrapping each sentence. But, the space between sentences isn't included. When selecting text, if start or end of the selection is at a different level of the spans, the highlight won't get saved. In this case, the space is outside the spans and that causes a problem.

I remember this being discussed some time ago, and I thought it had been fixed in the driver. It might not be all that is going on, but it is probably a contributing factor.
Quote:
I'm using Georgia.
Is there a way to see exactly which font size I'm using?

Usually like this, or one step smaller:
The simplest way is to look in the config file on the device. Look for the line with "readingFontSize". But, that is roughly what I am using.
Quote:
I will test more, but I'm guessing around 8-12 highlights before the problem arises again.
OK.

Another thought is to look for a stack dump on the device. This will be in the .kobo directory and have the name "stack_nn.log" where "nn" is two digits. These can be produced by the firmware when there is a problem. If there is one, it can give a hint of what is going on, but we can also give it to Kobo to look at.
davidfor is offline   Reply With Quote