Quote:
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.