Since 1.9.10, text slightly cut off on very bottom line

[danskmacabre]

Ever since I got the 1.9.10 firmware I've noticed this when I have a full page ePUB.
Meaning if I have a line on the very bottom displayable line, the text on the bottom line is slightly cut off on the bottom part of the text, like it's trying to display the bottom bit of the text in a non-displayable area.

It's still readable tho, it's only about maybe 15% of the text cut off from only the very bottom line.

I've not noticed this until I got the 1.9.10 firmware, so I think it's a new bug.

[danskmacabre]

Interestingly, when I change the font from Georgia to Felbridge, the problem goes away.

[rjcroy]

Indeed! The Kobo Product Manager SameerH has acknowledged the bug and said it will be patched in a update following shortly.

See post here.

[danskmacabre]

Ah ok, thanks for the heads up!

I can live with it until it get patched shortly.

[rashkae]

If the epub in question is not Digital Restriction Management locked, you can use Calibre to add an 8pt border on the bottom of the page, which will prevent the issue for being visible. If you are reading an affected book, making any change in the appearance (margin, line height, font, etc), will reflow the pages properly for that session.

[danskmacabre]

Yeah I know, I do that and it works.
But it's beginning to be a pain to have to do that EVERY time I unlock my KT to read a book properly.
I really hope they get out a fix real soon.

[beautifulsoup]

I've experienced this, as well. I went to a smaller font size, and that's a decent enough adaptation to make for now, while waiting for the next update.


ETA: D'oh! That's exactly what Sameer suggested, in the link rjcroy posted; to change anything in reading settings.

[JSWolf]

Originally Posted by rashkae

If the epub in question is not Digital Restriction Management locked, you can use Calibre to add an 8pt border on the bottom of the page, which will prevent the issue for being visible. If you are reading an affected book, making any change in the appearance (margin, line height, font, etc), will reflow the pages properly for that session.

Changing the ePub via Calibre is a big no-no. You can end up with things not as intended. The best way to do it is to extract the CSS and add in an @page and under @page, put in the margin you want. Then put back the CSS and away you go.

[Donnageddon]

The above workarounds (changing fonts, font size, etc) does not consistently work for me. It may fix the page I am reading, but then the next page will have the same error. And it is often missing a complete line, not just a portion of the line.

I do hope they fix this very quickly. I am back to using my Sony 650 again.

[clegare]

When I turned off Show Margin Page Numbers in advanced settings it stopped cutting off the bottom line for some reason... maybe it'll work for others too?

[rashkae]

Originally Posted by JSWolf

Changing the ePub via Calibre is a big no-no. You can end up with things not as intended. The best way to do it is to extract the CSS and add in an @page and under @page, put in the margin you want. Then put back the CSS and away you go.

This is off-topic to this thread, but needs to be said somwhere.

Maybe instead of plastering your one man anti-calibre diatride crusade all over the place, you can provide specific examples of books that do not convert properly so that bugs can be fixed? I can assure you, that of the hundreds of books I've converted through Calibre, I've always ended up with fixing problems, not creating them. Certainly that's a better track record than encouraging non web design folk to open and edit CSS files. That's not to say that a book that doesn't work doesn't exist, and might need to be reverted, but a big no-no?

I've noticed that your haughty tone in posting often overshadows the value of your message.

[corona]

Originally Posted by danskmacabre

Interestingly, when I change the font from Georgia to Felbridge, the problem goes away.

Doesn't work for me (but I don't care that much either).

[nogle]

Originally Posted by rjcroy

Indeed! The Kobo Product Manager SameerH has acknowledged the bug and said it will be patched in a update following shortly.

See post here.

I must admit that after this post, I see no reason for the ongoing postings about how to code epub files etc. as the linked thread also explains a work-around until the patch comes out.

[danskmacabre]

Originally Posted by nogle

I must admit that after this post, I see no reason for the ongoing postings about how to code epub files etc. as the linked thread also explains a work-around until the patch comes out.

Except that workaround doesn't work for everyone.

[JSWolf]

Originally Posted by rashkae

This is off-topic to this thread, but needs to be said somwhere.

Maybe instead of plastering your one man anti-calibre diatride crusade all over the place, you can provide specific examples of books that do not convert properly so that bugs can be fixed? I can assure you, that of the hundreds of books I've converted through Calibre, I've always ended up with fixing problems, not creating them. Certainly that's a better track record than encouraging non web design folk to open and edit CSS files. That's not to say that a book that doesn't work doesn't exist, and might need to be reverted, but a big no-no?

I've noticed that your haughty tone in posting often overshadows the value of your message.

I do use Calibre for converting. I do like Calibre. It does a lot of things quite well. But it does some thing not so well. Conversion to PDB is one of the things done not so well. Converting ePub > ePub is a mixed bag. Take an ePub with an embedded font and convert it to ePub. You will find that every XML file now has the embedded font code instead of neatly once in the CSS.