Instructions for patching firmware 4.19.14123

[dmapr]

I don't really have a problem copy-pasting the patch from the previous set into the new one. And it is certainly less work (from where I stand) to run the patch to replace Georgia with Amasis than it is to rename Amasis to Georgia, especially now that the internal Amasis has all the glyphs I need and there's no reason to side-load it anymore. So if you say it's too niche then it's too niche

[Semwize]

The best option would be for Kobo to fix Avenir - for this is the font that is used to display the device menu. And there would be no problem.

Adding to the fonts folder and using the patch requires you to perform additional actions after each reboot of the device...

[afakler]

I have a problem with this patch on my Aura One. I normally read with the font slider approx. two third to the right. Under 4.19, the corresponding font size is suddenly much smaller than with 4.18. When i go now one step to the right, the font is not slightly bigger, it changes to a very large size.

I went back to 4.18 and everything is ok again.

Does any one else have this problem?

BTW, is a patch possible, that swaps the pages of the reading settings, so that it looks like in 4.18?

[ps67]

Originally Posted by afakler

I have a problem with this patch on my Aura One. I normally read with the font slider approx. two third to the right. Under 4.19, the corresponding font size is suddenly much smaller than with 4.18. When i go now one step to the right, the font is not slightly bigger, it changes to a very large size.

I went back to 4.18 and everything is ok again.

Does any one else have this problem?

BTW, is a patch possible, that swaps the pages of the reading settings, so that it looks like in 4.18?

Same problem here, also with Kobo Aura One, now I have no time for a screenshot because I disabled the patch. If I can I will post it tomorrow in the late afternoon (Greenwich time).

[Svens]

Originally Posted by afakler

I have a problem with this patch on my Aura One. I normally read with the font slider approx. two third to the right. Under 4.19, the corresponding font size is suddenly much smaller than with 4.18. When i go now one step to the right, the font is not slightly bigger, it changes to a very large size.

I went back to 4.18 and everything is ok again.

Does any one else have this problem?

BTW, is a patch possible, that swaps the pages of the reading settings, so that it looks like in 4.18?

I noticed the same problem using the patch "Custom font size". The situation is better when using the patch "Set font scale factor".

[afakler]

Originally Posted by Svens

I noticed the same problem using the patch "Custom font size". The situation is better when using the patch "Set font scale factor".

That really does help! for the hint

[pghaworth]

Originally Posted by Svens

I noticed the same problem using the patch "Custom font size". The situation is better when using the patch "Set font scale factor".

new at this... this only applies to custom fonts, correct? asking because I was using a Kobo Clara font and had the same issue after setting the other patch. went to read and it was all different so I tried to adjust and it was huge. took a good bit of tweaking to get it back where I needed it. I tried other Clara fonts and the issue persisted.

thanks

[dmapr]

Originally Posted by Semwize

The best option would be for Kobo to fix Avenir - for this is the font that is used to display the device menu. And there would be no problem.

Adding to the fonts folder and using the patch requires you to perform additional actions after each reboot of the device...

Yes, and I've submitted the request to Kobo, but who knows if they'll ever get to it. Plus I like replacing Georgia with Amasis

[geek1011]

I've released v57 with fixes for "Custom font sizes" and the aforementioned changes from jackie_w.

[Semwize]

Originally Posted by dmapr

It's Avenir that needs fixing now.

Yes, of course, Avenir. Corrected the post)

[jackie_w]

Originally Posted by dmapr

I don't really have a problem copy-pasting the patch from the previous set into the new one. And it is certainly less work (from where I stand) to run the patch to replace Georgia with Amasis than it is to rename Amasis to Georgia, especially now that the internal Amasis has all the glyphs I need and there's no reason to side-load it anymore. So if you say it's too niche then it's too niche

We'll see how it goes. If enough people keep asking for it, it can be made "official". I take your word that using the Kobo-improved Amasis instead of Georgia solves a GUI problem for Russian users. However, I wonder if it solves any problems for Vietnamese users?


Re: the copy-pasting. I'm never sure how many kobopatch users know this...

Using nickel.yaml as an example, are you aware that you don't need to copy your customised nickel patches out of one nickel.yaml into the next after each fw update?

You can put all your customised nickel patches into a separate file (e.g. nickel_custom.yaml, but can be any name) and change each patch name slightly in the custom file. Then tell your kobopatch.yaml file to read both nickel.yaml/nickel_custom.yaml. In this way you can leave the official nickel.yaml untouched and let your custom yaml files and kobopatch.yaml travel from one firmware to the next.

It can save a lot of work at firmware upgrade time, but it isn't 100% foolproof for all customisations. Kobo sometimes make changes which prevent an old custom patch working, which then requires comparing old nickel_custom.yaml version with new nickel.yaml version and replicating the new bits in the custom file.

I won't elaborate more in case you already know all this.

[pghaworth]

Originally Posted by jackie_w

I won't elaborate more in case you already know all this.

that main kobopatch.yaml file can be customized too, right? I guess you could keep a modified yaml and just overlay the important info each time too, right? does the kobopatch.yaml stay the same each time or does it change?

still so much to learn

[Semwize]

Originally Posted by jackie_w

using the Kobo-improved Amasis instead of Georgia solves a GUI problem for

Georgia font is fine, problems with Avenir, which lacks glyphs.

[tayseidel]

What is a simple and easy way to carry over my settings in the patches in the previous firmware to the current one?

EDIT: Read Jackie_W's post #101. Seems this topic was covered and I overlooked it.

I'll just go ahead and compare the old/new ones and enable/disable as I go just so there are no surprises when I do the upgrade and patch.

[jackie_w]

Originally Posted by pghaworth

that main kobopatch.yaml file can be customized too, right? I guess you could keep a modified yaml and just overlay the important info each time too, right? does the kobopatch.yaml stay the same each time or does it change?

There's no "One True Way". geek1011 has provided various options. Do what suits you best.

My kobopatch.yaml is used as Mission Control and gets used as-is from fw to fw. The only things that get changed (except when I'm doing beta testing) are:
- the 2 occurrences of firmware number up at the top
- when I want to add a brand new patch to my list of enabled patches.
- when I've decided to permanently disable a previously used patch

I never change Enabled: no to Enabled: yes in the other yaml files. All on/off control is done in kobopatch.yaml.

Some people like to keep a full list of all patches in their kobopatch.yaml but I prefer to restrict mine to just the ones I'm going to enable - mainly because there are already so many in there, without cluttering it up with ones I'm never going to use.