Firmware 4.45.23640

[DNSB]

If you go into More => Settings =>Reading Settings and remove the checkmark from Show Adobe EPUB page numbers that should get rid of the extra page numbers.

[sherman]

Originally Posted by jackie_w

Yes, I can confirm this patch no longer works.

However, is it possible that this patch is no longer required? I've just opened a kepub and an epub (both previously unread) on my Libra Colour with 4.45.23640 and the font-size appears the same in both.

It would be good if someone else could confirm/deny this potential good news.

It looks like someone at Kobo might have finally read my patch notes, because I think they have indeed fixed it.

I loaded this firmware into Ghidra, and it appears that Kobo are now using the ( font_size / 15.0 ) * 96 formula my patch was trying to replicate with different numbers.

EDIT: I am very rusty with this though, so take this as a grain of salt... And the problem was always device dependent depending on the devices screen DPI.

[DrChiper]

Originally Posted by DNSB

I've seen that when I've set the font size to small enough and the maximum column width gets exceeded when using RMSDK (ePUb). It does not happen with the Readium based renderer for kepubs.

Yes, I discovered that later. I had to crank up the font size a lot for my ePUB in order to read it as I was used to. Font sizing seems now to behave like the KEPUB viewer.

The "About KLC" page is called "eLabel", and is only loaded (on manually updating) when connected via WiFi. Otherwise you get an error massage stating the document cannot be found and you must sync.

[Maxrem]

Originally Posted by DNSB

Remote where the wake up turned on both WiFi and Bluetooth.

That is my KLC experience as well.

[jackie_w]

Originally Posted by sherman

It looks like someone at Kobo might have finally read my patch notes, because I think they have indeed fixed it.

I loaded this firmware into Ghidra, and it appears that Kobo are now using the ( font_size / 15.0 ) * 96 formula my patch was trying to replicate with different numbers.

EDIT: I am very rusty with this though, so take this as a grain of salt... And the problem was always device dependent depending on the devices screen DPI.

Thanks for adding your second opinion, @sherman.

I agree that the problem was always restricted to certain models but I never did know exactly which models were affected and which were not. I believe my KA1 was in the "no problem" camp but I'm fairly sure that my Libras and Claras did have the problem unless your 'Unify' patch was applied.