Glo Problem with typegenius

[traycold]

hi all,
after upgrading to 3.11 I discovered that I don't have any more "sharpness" into typegenius, for any font (see attached screenshot). Is it just mine problem, or it's a general bug of kobo?

[DNSB]

Originally Posted by traycold

hi all,
after upgrading to 3.11 I discovered that I don't have any more "sharpness" into typegenius, for any font (see attached screenshot). Is it just mine problem, or it's a general bug of kobo?

It's not really a bug. There's only been a single slider for a couple of firmware revisions so call it a design decision.

[davidfor]

This changed at least two firmware versions ago. From memory, Kobo stated that people found the interface confusing and had difficulty getting good results. The single slider adjusts sets both weight and sharpness in the config file. I'm not sure how it decides on the two values, but it might be a predefined list.

[jackie_w]

Originally Posted by traycold

hi all,
after upgrading to 3.11 I discovered that I don't have any more "sharpness" into typegenius, for any font (see attached screenshot). Is it just mine problem, or it's a general bug of kobo?

Unless something changed in v3.11, even though there is only a Weight slider when you make a change to Weight the Sharpness is also changed. You can see this if you look in the .kobo/Kobo/Kobo eReader.conf file. It's just that now Kobo makes the decision about what Sharpness goes with which Weight. Whether they are good decisions, I don't know

ETA: David beat me to it, as usual!

[GeoffR]

Since firmware version 3.2.0 the separate weight and sharpness sliders have been replaced by a single slider that adjusts weight and sharpness at the same time.

The weight and sharpness values for each font are stored in the .kobo/Kobo/Kobo eReader.conf file, and since firmware 3.3.0 the values are in a human-readable format (sharpness values range from -0.4 to 0.2, weight values range from -0.2 to 0.8), so it is possible to set them manually by editing this file.

(In Windows, use an editor that understands unix line breaks such as Notepad++ to edit the file, don't use Notepad.)

Edit: DNSB davidfor and jackie_w beat me to it :-)

[DNSB]

Originally Posted by GeoffR

(In Windows, use an editor that understands unix line breaks such as Notepad++ to edit the file, don't use Notepad.)

But it's so much fun editing with a text editor that changes the single lf eol to a cr/lf pair. It leads to those moments.

[JSWolf]

Originally Posted by DNSB

But it's so much fun editing with a text editor that changes the single lf eol to a cr/lf pair. It leads to those moments.

But the default for notepad++ is to use cr/lr when you hit return. So in order to edit these Kobo text files you'll need to change the default cr/lf to the Unix line endings.

[davidfor]

Originally Posted by JSWolf

But the default for notepad++ is to use cr/lr when you hit return. So in order to edit these Kobo text files you'll need to change the default cr/lf to the Unix line endings.

Not here. Notepad++ seems to pay attention to what is used in the file and uses that. But, there might be an option to tell it to do that.

[DNSB]

Originally Posted by JSWolf

But the default for notepad++ is to use cr/lr when you hit return. So in order to edit these Kobo text files you'll need to change the default cr/lf to the Unix line endings.

Here it seems as if Notepad++ defaults to whatever is used in the file you open for editing. If the file is using lf as the eol, it continues that usage. So if I open a Windows text file, the EOL conversion shows Windows Format as greyed out with Unix/OSX or Old Mac Format as clickable while opening a Unix text file, the Windows and Old Mac Formats are clickable.

[traycold]

thank you all for the clear explanation. I missed this "improvement" by Kobo