kobopatch request thread

[Avimaker]

Hello all,
i am new here.
I decided to create an account so to ask you professionals, is it possible to create a patch which can change some of the prebuild UI languages in Kobo to Bulgarian?
I have Forma and Clara HD e-readers.
We use Cyrillic alphabet like Russians with some minor difference.

P.S. Sorry if this topic are commented in the past.
I tried to check for this topic but can not find anything.

[zaslowe]

Would it be possible to add full screen covers on the screensaver, minus the black bars on the left and right sides of the screen? I have seen this in KOReader.

Anyway, great job! Love the effort and work you put into this project.

[JSWolf]

Originally Posted by zaslowe

Would it be possible to add full screen covers on the screensaver, minus the black bars on the left and right sides of the screen? I have seen this in KOReader.

Anyway, great job! Love the effort and work you put into this project.

The covers are being shown in the correct aspect ratio.

Are you one of those who cannot stand black bars on your TV and have to set the TV to full screen thus distorting the picture?

[Deobulakenyo]

Originally Posted by zaslowe

Would it be possible to add full screen covers on the screensaver, minus the black bars on the left and right sides of the screen? I have seen this in KOReader.

Anyway, great job! Love the effort and work you put into this project.

You can resize the book cover in Calibre to fill up the whole screen

[zaslowe]

Originally Posted by JSWolf

The covers are being shown in the correct aspect ratio.

Are you one of those who cannot stand black bars on your TV and have to set the TV to full screen thus distorting the picture?

Just asking....

Jeez.

[Overtone9201]

Minor annoyance that I'm wondering if can be fixed

If I am reading a book and I hit the search icon, I want to search the book that I am reading. Instead, it defaults to "My Books" and I have to change to "Current read", then it seems like the current reading list always has to display five books, even if I'm just reading one, and it's almost never already on the book I'm currently reading, so I have to select it.

Could this be fixed with a patch? So the default search (at least when called up from within a book) is to search in currently reading books, and have the current read list only display what I'm actually reading?

[Tony556]

Hi! I was wondering if there could be a patch to essentially "match" the button controls of the Oasis on a Libra 2 (and other button-having Kobos).

I'm coming from an Oasis to a Libra 2 and I got really used to (and prefer) the layout of:

Portrait: Up - Next, Down - Previous

Landscape: Right - Next, Left - Previous

Thank you all for the amazing patches and tools!

[DNSB]

Originally Posted by Tony556

Hi! I was wondering if there could be a patch to essentially "match" the button controls of the Oasis on a Libra 2 (and other button-having Kobos).

I'm coming from an Oasis to a Libra 2 and I got really used to (and prefer) the layout of:

Portrait: Up - Next, Down - Previous

Landscape: Right - Next, Left - Previous

Thank you all for the amazing patches and tools!

Why bother with a patch? Just go into Setting => Reading settings and select the Inverted option for Button Controls.

[Jappy]

Hi.
Is it possible to have separate slider for Font Sharpness and Weight?
I like my fonts thin but sharp, and with one single slider the thinner the font the blurred the result.
Don't know if possible.
Thank you!

[MGlitch]

Originally Posted by Jappy

Hi.
Is it possible to have separate slider for Font Sharpness and Weight?
I like my fonts thin but sharp, and with one single slider the thinner the font the blurred the result.
Don't know if possible.
Thank you!

This used to be how it was many firmware versions ago. However I believe the best that can be done now is to use a patch to set the sharpness of the font so it doesn’t adjust along with the weight.

[Amon_Re]

Originally Posted by geek1011

- ✓ Enable Elipsa Markup for sideloaded KEPUBs (andrefrsousa, jonwest, AveryMensch, av_mtl, more):
---------DONE

Can anyone tell me if this patch still exists? I can't find it in 'src'

[rtiangha]

Question about the patches because I'm trying to understand how Find/Replace works.

I'll use one of jackie_'w's custom patches in post #844 as an example (NOT to pick on it).

One of the parts goes like this:

  # Part 1: Customise font-size of book Title
  - FindZlib: "HeaderSmallElidedLabel[localeName=\"zh-HK\"]," # default.qss (HeaderSmallElidedLabel)
  - ReplaceZlibGroup:
      Replacements:
        # Customise Title font-size from default 42px
        # add Storm-specific code by commandeering some code used only by Chinese-HK locale users
        - Find:    "HeaderSmallElidedLabel[localeName=\"zh-HK\"],\nHeaderSmallItalicLabel[localeName=\"zh-HK\"] {\n  font-family: Sans-SerifZH-Traditional, sans-serif;\n  font-style: normal;\n  qproperty-forceLeading: 5;\n}"
          Replace: "HeaderSmallElidedLabel[qApp_deviceIsStorm=true] {font-size:35px;}"

So my understanding is that it overwrites everything under the HeaderSmallElidedLabel[localeName=\"zh-HK\"] section on line 1386 in default.qss with HeaderSmallElidedLabel[qApp_deviceIsStorm=true] {font-size:35px;}.

But I noticed that there is already a HeaderSmallElidedLabel[qApp_deviceIsStorm=true] section in the file on line 1368. Specifically, it looks like this:

HeaderSmallElidedLabel[qApp_deviceIsStorm=true],
HeaderSmallItalicLabel[qApp_deviceIsStorm=true] {
  font-size: 42px;
  padding-left: 23px;
  padding-right: 23px;
}

and it's the only one.

If font-size is the value being targeted to be changed to 35px, would something like this:

  # Part 1: Customise font-size of book Title
  - FindZlib: "HeaderSmallElidedLabel[qApp_deviceIsStorm=true]," # default.qss (HeaderSmallElidedLabel)
  - ReplaceZlibGroup:
      Replacements:
        - Find:    "HeaderSmallElidedLabel[qApp_deviceIsStorm=true],\nHeaderSmallItalicLabel[qApp_deviceIsStorm=true] {\n  font-size: 42px;"
          Replace: "HeaderSmallElidedLabel[qApp_deviceIsStorm=true],\nHeaderSmallItalicLabel[qApp_deviceIsStorm=true] {\n  font-size: 35px;"

also work? That way, one wouldn't need to overwrite that entire zh-HK section.

[jackie_w]

Originally Posted by rtiangha

Question about the patches because I'm trying to understand how Find/Replace works.


If font-size is the value being targeted to be changed to 35px, would something like this:

<snip>

also work? That way, one wouldn't need to overwrite that entire zh-HK section.

Patching nickel CSS is not a particularly precise skill - lots of ways to skin a rabbit.

What you suggested would work, but you'd also be simultaneously changing the HeaderSmallItalicLabel item - which may, or may not, be a desirable thing. First you'd need to know where that item is used. There's no convenient documentation where you can find that out. Perhaps if you have decompilation skills (which I don't) ...

Your particular example is not too bad because there's only the potential for "unintended consequences" on one other item. If you look at Part 2, which customises Author and Subtitle using SmallElidedLabel, you'll see that a similar approach would simultaneously change font-size for 3 other items (PageLabel, SmallTouchLabel, SmallLabel).

Rightly or wrongly, I chose a consistent alternative approach which may inconvenience "zh-HK" locale users but no-one else. If this is a problem for someone I knew I'd easily be able to tweak the patch to change the target code to that used by locale "zh" or "zh-TW" or "ja".

Patching is often a struggle to find enough room to add extra code without breaking something else. The Chinese/Japanese code blocks are useful because they provide many characters to play with.

BTW I'm glad to see someone else taking an interest in the details of patching.

[rtiangha]

Originally Posted by jackie_w

BTW I'm glad to see someone else taking an interest in the details of patching.

One more question then:

Going with the patching zh-HK approach, both it and the original HeaderSmallElidedLabel section both have a font-size property; running the patch would mean it would appear twice in default.qss. Clearly, the patched one takes precedence (otherwise the patch wouldn't work in the first place), but in general, if the same situation were to occur, which version would take precedence? Whichever one appears later in the file? Or is it determined another way? I assume qss is similar to css in that the last instance overrides everything else before it, but I don't really know QT enough to be confident in how stuff works.

[jackie_w]

Originally Posted by rtiangha

I assume qss is similar to css in that the last instance overrides everything else before it, but I don't really know QT enough to be confident in how stuff works.

I also assume that later qss/css styles override similar code earlier in the same file. After several years doing this stuff I've had no reason to change that assumption.