kobopatch-patches VS avo

Yes, this is a problem for books with long titles and subtitles. I use kobopatch to increase the width available for book titles in the booklist https://www.mobileread.com/forums/showpost.php?p=4239375&postcount=844. Here are pics of some patches that I use.

NickelMenu kobopatch

https://pgaskin.net/kobopatch-patches/ click download, read instructions, download the thingy. Select which patched you want and finish the process.

There’s KoboPatches, Nickel Menu, and Koreader.

Once I started using the (relatively verbose) OED, I also found it useful to enable the patch in KoboPatch which increases the usable reading area in the dictionary pop-up.

Here are some resources if you are finding trouble : https://pgaskin.net/kobopatch-patches/ https://www.mobileread.com/forums/showthread.php?t=297338https://youtu.be/bq4l5pkEDpE

Regarding the "light" look, I think that's a function of the firmware you were on. Did upgrading to the Glo firmware fix it? I highly recommend checking out the patch on pgaskin's site too, because it will let you tweak so much of the interface and make it look even sharper. You can find the patch info here: https://pgaskin.net/kobopatch-patches/

I downloaded kobopatch_4.10.11591.zip from https://github.com/pgaskin/kobopatch-patches/releases/tag/v73

I wonder whether avo could have been useful here?[1] I mention it because it came up the last time we were talking about AVX operations in go.[2]

1 = https://github.com/mmcloughlin/avo

2 = https://news.ycombinator.com/item?id=34465297

I thought the /r/golang comments on this post were pretty useful[1]. They also introduced me to avo[2], a tool for generating x86 assembly from go that I hadn't seen before. There are some examples listed on the avo github page for generating AVX512 instructions with avo.

1 = https://www.reddit.com/r/golang/comments/10hmh07/how_to_use_...

2 = https://github.com/mmcloughlin/avo

For writing AVX512 from scratch avo is a much better alternative.

Avo is a library that simplifies writing complex go assembly, I found it very useful to figure out how instructions map onto Go's asm syntax. But you could definitely do the translation directly, it's what c2goasm did (couldn't get it to work reliably unfortunately).

Curious if you're looking at using avo to write the assembly

You can use github.com/mmcloughlin/avo for generating the assembly use Go.

For normal and "better" mode I am using avo to generate different encoders for different input sizes, with and without Snappy compatibility. That currently outputs about 17k lines of assembly.

You could perhaps just have the Go compiler generate the assembler for your code:

go tool compile -S file.go > file_amd64.s

Then you could verify it doesn't change over time, and choose to begin maintaining by hand if it makes sense.

If you do want to go the route of rolling it yourself, I'd suggest looking into something like Avo: https://github.com/mmcloughlin/avo

If you have to go with Assembly, try Avo https://github.com/mmcloughlin/avo