thanks for the info..Is there a possibility that it' l come back? See I really like the new firmware but my problem is that without the greek keyboard I can't search for my greek books...and I wish I could do the amazing work that you do but I'm clueless...

Based on my cyrillic layout I have done a quick copy and paste with the greek template for the KA1. Can you check if it works for you?

A total noob question (I apologize if I've missed something glaringly obvious): how does one install individual patches, after installing the whole kobopatch in one bundle? Is it even possible?

If you're talking about adding a brand new patch (rather than just changing 'Enabled: no' to 'Enabled: yes'), you add the new code to the relevant .yaml file. I'm being a bit vague here because ...

Quote:

Originally Posted by Sirtel

And on that subject, how does one update the installed patches, when the new version of them is released? By doing the whole procedure all over again?

I suspect many kobopatch users (not you as a first-time Kobo user) are using it in exactly the same way they used the old patching system which involved typing their same customisations to the same distributed .yaml files every time there's a firmware upgrade. This is often a lot more work than necessary.

The most convenient way to use kobopatch is by

using kobopatch.yaml as 'Mission Control' to control the enabled status of all desirable patches from a single location

Then you use kobopatch.yaml to bring it all together. The *_custom.yaml files will travel with you from firmware to firmware. Many custom nickel patches can survive across multiple firmwares. Rather fewer customised libnickel.so.1.0.0 patches survive but still quite a few. The major upgrade from fw 4.15.12920 to 4.17.13694 probably had the fewest survivors ever.

I'm sure some users have already worked all this out by reading the help notes in the distributed barebones kobopatch.yaml file, but I could do a more detailed write-up about it when I have more time to spare, i.e. probably not for a few weeks but hopefully before the next fw update.

If you're talking about adding a brand new patch (rather than just changing 'Enabled: no' to 'Enabled: yes'), you add the new code to the relevant .yaml file. I'm being a bit vague here because ...

I suspect many kobopatch users (not you as a first-time Kobo user) are using it in exactly the same way they used the old patching system which involved typing their same customisations to the same distributed .yaml files every time there's a firmware upgrade. This is often a lot more work than necessary.

The most convenient way to use kobopatch is by

using kobopatch.yaml as 'Mission Control' to control the enabled status of all desirable patches from a single location

Then you use kobopatch.yaml to bring it all together. The *_custom.yaml files will travel with you from firmware to firmware. Many custom nickel patches can survive across multiple firmwares. Rather fewer customised libnickel.so.1.0.0 patches survive but still quite a few. The major upgrade from fw 4.15.12920 to 4.17.13694 probably had the fewest survivors ever.

I'm sure some users have already worked all this out by reading the help notes in the distributed barebones kobopatch.yaml file, but I could do a more detailed write-up about it when I have more time to spare, i.e. probably not for a few weeks but hopefully before the next fw update.

No, you were talking about advanced font control which allows you to adjust the weight of sideloaded epubs. The patch I’m talking about removes the higher font sizes from the font size selection and adds additional smaller sizes to allow you to fine tune the size.

Custom font sizes is the actual entry name for this patch.

You are totally right. Forgive me, it's the resulsult of my total noobness on these Kobo matters.

I've searched but didn't find what I was looking for so I'll ask: is it possible to have the header and footer change places? I want the chapter progress at the bottom like it was before this new update, and the name and progress of the book at the top. Is this doable?

I also would ask if, in case is possible, you could find values so to get:
- something between 10-30 minutes to use for stand-by
- something between 3-5 days (i.e. 72-120 hours) for power-off

I would just use these two values, the other options could be whatever.

Thanks.

Here is my modified version. I have first value as 26min and the second as 43min. I''ve tested the 26min sleep timer and it works perfectly. I too would like larger values such as 48, 72, and 96 hours.