Libra 2 Epub font problem in firmware 4.32.19501

[DNSB]

Originally Posted by Krios

Thank you, tried it just now, same problem as before, i think i will just downgrade to 4.30, and wait for the next update.

Have you looked at any of the threads about issues with the Bookerly font on Kobo devices and the suggested fixes?

I currently have the Bookerly version from Kindle firmware 5.14.3 installed on my Sage and have to do the usual diddling with FontForge to have it work properly.

[MGlitch]

Originally Posted by DNSB

Have you looked at any of the threads about issues with the Bookerly font on Kobo devices and the suggested fixes?

I currently have the Bookerly version from Kindle firmware 5.14.3 installed on my Sage and have to do the usual diddling with FontForge to have it work properly.

As fidgety as Bookerly may be, I’d be surprised if having a non modified version on the device went so far as to cause issues with using other fonts as Krios has indicated they do. As well as built in fonts without any sideloaded fonts.

What I would suggest doing is deleting the font.SQLite file from within the .Kobo directory of the root of your kobo when plugged into a computer.

I don’t know if this file might survive the various resets done but one sure way to make sure it’s rebuilt is deleting it. I’d suggest doing this without any sideloaded fonts first and then testing to see if the issue persists on 4.32 firmware. If it does report back here. If it doesn’t add one font at a time, testing each time. Note you’ll have to reboot your Kobo each time (I believe) to ensure they’re properly installed. If you don’t encounter the issue let us know it’s been resolved. If it does reoccur let us know what font and if you can recall where you got the font.

[JSWolf]

Originally Posted by MGlitch

As fidgety as Bookerly may be, I’d be surprised if having a non modified version on the device went so far as to cause issues with using other fonts as Krios has indicated they do. As well as built in fonts without any sideloaded fonts.

What I would suggest doing is deleting the font.SQLite file from within the .Kobo directory of the root of your kobo when plugged into a computer.

I don’t know if this file might survive the various resets done but one sure way to make sure it’s rebuilt is deleting it. I’d suggest doing this without any sideloaded fonts first and then testing to see if the issue persists on 4.32 firmware. If it does report back here. If it doesn’t add one font at a time, testing each time. Note you’ll have to reboot your Kobo each time (I believe) to ensure they’re properly installed. If you don’t encounter the issue let us know it’s been resolved. If it does reoccur let us know what font and if you can recall where you got the font.

When adding side loaded fonts, do not add Bookerly ss the first font. Try it as the third font added. But you will need to delete the fonts directory.

[Krios]

Originally Posted by MGlitch

As fidgety as Bookerly may be, I’d be surprised if having a non modified version on the device went so far as to cause issues with using other fonts as Krios has indicated they do. As well as built in fonts without any sideloaded fonts.

What I would suggest doing is deleting the font.SQLite file from within the .Kobo directory of the root of your kobo when plugged into a computer.

I don’t know if this file might survive the various resets done but one sure way to make sure it’s rebuilt is deleting it. I’d suggest doing this without any sideloaded fonts first and then testing to see if the issue persists on 4.32 firmware. If it does report back here. If it doesn’t add one font at a time, testing each time. Note you’ll have to reboot your Kobo each time (I believe) to ensure they’re properly installed. If you don’t encounter the issue let us know it’s been resolved. If it does reoccur let us know what font and if you can recall where you got the font.

Thank you, i tried all that after Peter T suggested there is also fonts database, it did not survive either factory or manual reset, and same thing is happening without sideloading any fonts. I have tried again to downgrade to 4.30 and 4.31 and there is no problems there, problem starts as soon as i update to 4.32, and only in epubs, kepubs work as intended.

[JSWolf]

Stop installing 4.31. You could be corrupting the database before you install 4.32.

[Krios]

Originally Posted by JSWolf

Stop installing 4.31. You could be corrupting the database before you install 4.32.

Maybe i'm dumb, but i'm not that dumb, i have also upgraded directly from 4.30 to 4.32, but even if i didn't, it shouldn't have matter because i have done both factory and manual reset after upgrading to 4.32.

[MGlitch]

Originally Posted by Krios

Maybe i'm dumb, but i'm not that dumb, i have also upgraded directly from 4.30 to 4.32, but even if i didn't, it shouldn't have matter because i have done both factory and manual reset after upgrading to 4.32.

Don’t mind Jon he’s like a dog with a bone. It doesn’t seem likely that this was ever the main database getting corrupted.

As to what is causing it I’m baffled. I presume you’ve tried different ePub books. I dunno what else there is that hasn’t been reset, or removed.

[rashkae]

Has anyone confirmed that this is *not* happening to everyone? The difference between the two sample images is only 5px between lines, which might be hard to spot on 300dpi devices.

[JSWolf]

Originally Posted by rashkae

Has anyone confirmed that this is *not* happening to everyone? The difference between the two sample images is only 5px between lines, which might be hard to spot on 300dpi devices.

It's not happening to me and I am reading ePub.

[Sirtel]

Originally Posted by JSWolf

It's not happening to me and I am reading ePub.

Me neither.

But we both use the 24 line spacing values patch. Perhaps that's the reason it's not happening to us.

[JSWolf]

Krios, would you mind installing 4.32 and trying the 24 line spacing values patch from the 4.32 patches?

[Sirtel]

Originally Posted by JSWolf

Krios, would you mind installing 4.32 and trying the 24 line spacing values patch from the 4.32 patches?

We also have the line-height values removed from the css. The alternative to that would be the "force user line spacing" patch, I think.

[JSWolf]

Krios, before trying to patch, can you install 4.32 and try the following eBook from the library here at MR?

https://www.mobileread.com/forums/sh...d.php?t=177182

[Krios]

I'm normally using "My 24 line spacing" and "Force user line spacing in ePubs" patches, so i have already tried that.

Originally Posted by JSWolf

Krios, before trying to patch, can you install 4.32 and try the following eBook from the library here at MR?

https://www.mobileread.com/forums/sh...d.php?t=177182

Tried, same thing happens in all epubs.

Could you please go in advanced font settings (where you change font Weight) and check if "Lorem ipsum dolor" text is written in font you are using or sans serif font?

[Lemons]

On the libra's I owned and before I gave up on the new devices, I had this
issue as well. No matter what I tried to do, no epubs worked at all, unless converted over to kepub instead. It was almost useless to read because it would skip 2-5 pages as well. The sage oddly never had this problem yet there was other problems with that one.