Quote:
Originally Posted by GeoffR
In the previous firmware version Kobo used footerMargin values of 15 for Glo/Aura, 20 for AuraHD/H2O and 40 for other devices. For this version Kobo changed the values to 170 for AuraHD/H2O and 105 for other devices. The example patches just preserve the values set by Kobo in case they are important for something.
It should be okay to use other fonts for the footer, but if the font has a long name then you will need to edit the first replace_string in the patch to make it fit. (those of you familliar with css might want to delete all the examples and just work with the first replace_string line by itself anyway.)
I suggest Avenir or Georgia because these fonts are used in other places in the UI, so they are probably already in the device's memory, but you will have to experiment and see what else works.
|
Ok, then it is "behind" this topic, but for some reason Kobo did change the footermargin values (is it idiot to think that it has something to do with the new function for "one handed" reading so it defines the place counted from bezel as border for the choice between back or forward ? ) so I think when it is important enough for them to do that, it better can be "not touched" ?
With my dislectic problem,I explained before I see pages or posts like pictures,it makes me read at a big speed.
But, I have problems with long strings of numbers, I have to device them into blocks of 2,same with telephone numbers,social security numbers,bank accounts,so I will never manage to edit those long strings
That is why I like the finetune things you made, because I now know how to handle, but the things like min-height and max-height interact with the long first replacestring ?? Because if I ever need to change the big string, I have always ask you for your help..