Glo FW 2.5.2 Features, bugs, fixes

[AnemicOak]

Originally Posted by DNSB

For epubs using Adobe's more or less standard page calculation, each page is 1024 bytes of compressed data within the chapter files. If there are less than 1024 bytes left at the end of the file, that counts as a page as well.

IIRC this is true unless the publisher does a page map, in which case you get page numbers that correspond to a specific print edition like you do with Kindle page numbers. Or maybe I'm remembering wrong.

[DNSB]

Originally Posted by AnemicOak

IIRC this is true unless the publisher does a page map, in which case you get page numbers that correspond to a specific print edition like you do with Kindle page numbers. Or maybe I'm remembering wrong.

There's also pageList which has the advantage that it does not make your epub flunk validity tests. OTOH, it has the disadvantage that it is not implemented in any application or ereader that I am aware of.

[speakingtohe]

Originally Posted by FJames

This feature you speak of does not seem to exist, at least for epubs in firmware 2.5.1. The library lists do not show any page numbers, and a touch-and-hold to display options for a book in the Library list (not very intuitive) does not display any page number.

Personally I don't find the page slider very useful. It's too insensitive to get to a specific point in the book, and I can't think of any occasion on which I have wanted to go to a non-specific point (normally +/- 20 pages from the nominal position I am trying to drag the slider to). A specific page number entry would be much more useful. Normally I want this feature because a glitch in the book or an accidental touch has skipped 20-30 pages and I need to go back to the specific page I was reading.

murg once suggested rolling your finger as opposed to tapping the slider. It is not perfectbut is better than tapping and will get you to within 3 or 4 pages usually or better. Still the slider is embarrasingly inadequate compared to other sliders on other devices.

Helen

Not really sure if this is the right thread for it, but has anyone noticed if the kepub renderer has any sort of font kerning enabled? Sometimes the wide letter spacing between pairs such as Yo and AV can be a little distracting

[kaufman]

Originally Posted by davidfor

But the added title was mentioned by the OP, so your post did not add any information to the thread.

I beg differ. The OP said, "yes, I've read about the book title", which was vague enough that I didn't know what it meant. JS Wolf included enough information that I decided to skip the update.

[taming]

JS Wolf is a lovely fellow who has never owned a Kobo device. This does not mean that posts from him have no value. You may want to read the opinion of others, as well.

[kaufman]

Well, I do own Aura HD and I don't know any of the people in this thread. I do know that I hate the idea of more non-book lines on the screen and whatever anyone thinks of anyone else on this thread, I got an important piece of information form JS Wolf that I didn't get from the OP. PeterT might have thought it was just stirring the pot, and for all I know, that's why JS Wolf posted it, but, for me, It was the most important piece of information in the entire thread.

[PeterT]

The reason I said what I did is that piece of information is present on maybe a zillion threads here already.

[kaufman]

Originally Posted by PeterT

The reason I said what I did is that piece of information is present on maybe a zillion threads here already.

Maybe, but the first one I came to was this one. Surly the fact that the new firmware was adding the title line to ePubs was an important piece of information in a thread called "FW 2.5.2 Features, bugs, fixes".

As I said, even though the the OP referred to it in the title, I didn't know what he was talking about until I got to JS Wolf's post.