Firmware 4.18.13737 released

[JIPG-reader]

It is curious how we deal with page numbers. Nobody complies if you have the same paper book in "pocket edition" or "deluxe edition" and they have a different numbering in the pages (obviously due to different type and size of letter and way of composition), but we do with ebooks.

For me, I prefer to know how many pages are left (real page turns) with my actual letter size, as it is was I was used to with paper books.

Regarding the page numbering, out of curiosity, I have taken a look in a number of paper books, and the majority of them have then page numbering in the bottom part of the page, and a big percentage centered (though some were right justified).

The title on top of the page is not usual in paper books, specially in "pocket" editions, although is some "deluxe" editions is not so difficult to find them. I have found very few books with the chapter title or page number on the top.

Just my two cents about how we deal with paper and electronic books.

Anyway, after some time reading with my kobo, now I like the composition with the tile on top and page number (or percentage or time remaining on request with a tap), Not having the possibility to select this composition make me reluctant to update.
If I update (still waiting for the 24 values line space patch), I will patch to have only the total page number bottom side.

[ratinox]

Originally Posted by MGlitch

It's your assertion that one is more important than all the others, my assertion is this is entirely subjective and should be as much in the hands of the user as it possibly can be.

No, and I apologize if I gave you that impression. My assertions are that what goes where is based on arbitrary criteria and that this should not be in the hands of the user. The former because for our thousand-odd years of print books there is no uniform standard, no "this is the one true best way". The latter because it is unnecessary complexity in the UI, unnecessary complexity in the code underneath that needs to accomodate all combinations of all options, and unnecessary complexity in testing all of the combinations with sufficient representative samples.

If you cannot demonstrate a practical reason for having these options, if the sum of your argument amounts to "because some users might want to do it", then this remains in the realm of the purely cosmetic.

[MGlitch]

Originally Posted by ratinox

No, and I apologize if I gave you that impression. My assertions are that what goes where is based on arbitrary criteria and that this should not be in the hands of the user. The former because for our thousand-odd years of print books there is no uniform standard, no "this is the one true best way". The latter because it is unnecessary complexity in the UI, unnecessary complexity in the code underneath that needs to accomodate all combinations of all options, and unnecessary complexity in testing all of the combinations with sufficient representative samples.

If you cannot demonstrate a practical reason for having these options, if the sum of your argument amounts to "because some users might want to do it", then this remains in the realm of the purely cosmetic.

Well we agree on everything other than it being in the users hands. Which will ultimately be a matter of opinion and somewhat pointless to go back and forth on. Obviously neither option is right or wrong it’s just different both have their pros and cons.

[ZodWallop]

Originally Posted by issybird

Except that it doesn't, frequently, as I indicated in my comment. Just this morning, I picked up my downstairs reader and opened it, and it didn't sync to where I left off with my nightstand reader. Both devices always have WiFi on; both are on the same network.

To me it sounds like Kobo should do better at syncing.

Except a screen is not a page as a fixed entity, as it needs to be for both navigation across devices and for time estimates. When I make a font bigger or smaller while reading, the page numbers change. When I switch to a larger or smaller device, the page numbers change. And I'll do both in the course of reading a book. I know approximately how long an ADE page takes me to read, as an ADE page is a constant. The shifting Kobo pages? How the heck can I know?

If you read a nice illustrated edition of Lord of the Rings at home and a paperback edition on the go, you have the same problem.

There are other downsides to kepub: the font rendering and layout aren't as nice as ePubs. But I put up with that because the one screen/one page is worth it.

For someone who reads on one device and never changes font size, your method works. For anyone else, it's a killer.

Though the words weren't said, I'm guessing your statement could also be translated as "for the majority of Kobo readers, the kepub method works. For anyone else, they should use ePub."

[geek1011]

For those who have been asking for a header/footer swap patch, I just figured out how to do it efficiently. Here is the patch, which will be in the zips for v54 in a week (jackie_w and I are still taking a break): https://github.com/geek1011/kobopatc...19c58338406a31.

[teija]

Apologies if this has already come up somewhere on the thread but it is possibly going to take me hours to locate it if it has...

Yesterday I updated my Kobo Aura HD to the latest version available in Canada (not sure which affiliate it is linking through). I am already wishing I didn't!

Has anyone else had an issue with their files now showing the oldest items as "recent"? And any issues with the backlight not switching off when they put it into standby??

I have a feeling I'm going to have to look up how to revert to an older version if that is even possible.

[rashkae]

Originally Posted by geek1011

For those who have been asking for a header/footer swap patch, I just figured out how to do it efficiently. Here is the patch, which will be in the zips for v54 in a week (jackie_w and I are still taking a break): https://github.com/geek1011/kobopatc...19c58338406a31.

That one looks like it will be... fun, to maintain between versions.. you are legend,, not only for figuring this out, put putting it out

[John F]

Originally Posted by geek1011

For those who have been asking for a header/footer swap patch, I just figured out how to do it efficiently. Here is the patch, which will be in the zips for v54 in a week (jackie_w and I are still taking a break): https://github.com/geek1011/kobopatc...19c58338406a31.

If convienent, could someone do a screen dump with this patch enabled, with header and footer disabled, and the reading menu active? Is the chapter progress shown when the menu is active with this patch?

I really like the no header/footer, with the chapter progress being or two taps away while reading.

Thanks.

[ratinox]

Originally Posted by teija

Has anyone else had an issue with their files now showing the oldest items as "recent"? And any issues with the backlight not switching off when they put it into standby??

In before JSWolf is an ass about illumination, again.

There are known problems on Aura HD with this firmware (and possibly all of the 4.18 and 4.17 firmwares). Lights turn on from power off and cannot be adjusted without toggling the light button. I cannot quite reproduce the no off problem you describe but it does take a few seconds for the light to turn off (it takes several seconds to fade out). What I see on both my Aura HD and my Forma is that when I sort by Recent it lists recently read/finished first then unread stuff so it's not by source file timestamp. I don't recall if that is the previous behavior because I don't use Recent sort.

[DNSB]

Originally Posted by ratinox

What I see on both my Aura HD and my Forma is that when I sort by Recent it lists recently read/finished first then unread stuff so it's not by source file timestamp. I don't recall if that is the previous behavior because I don't use Recent sort.

That behaviour is what I've seen for quite a while. Recent as the most recent time stamp whether accessed, created or modified. So taking an old book and opening it, moves it to the top of the recent list.

[daldred]

Originally Posted by davidfor

Can you post a link to the book in the Kobo store?

Here it is: https://www.kobo.com/gb/en/ebook/bri...trated-edition

When a kepub is opened the first time, a word count is calculated for each chapter in the book. And with the change to show a full book page count based on the rendered pages, it is probably a large book would take to long to render. In this case, I'm a little surprised the device doesn't reboot due to a hung process.

In fact it does. I'd obviously been too impatient when restarting it manually - when left alone it did restart itself.

I'm basing this guess on the slowness to open a book I've been reading. This is only 88K words, but, it has a single internal file with 18 chapters. When I opened it, the device would appear to hang, but would come to life after about 10 seconds.

While trying to work out what was going on I have opened a number of other large books today. One also led to a hang and restart, but on a second attempt opened successfully. A factor the two have in common is a very large TOC, which may also be relevant. These compendiums of stories are good value, but enormous.

I have reported all this to Kobo, and have a ticket number which has been referred to the development team. It was a very long chat conversation with their support people, trying a lot of options, but coming to the conclusion that something was definitely wrong!

It might help to turn off the footer. This might prevent the page count from being calculated for the book. It might also be necessary to turn off the progress bar as that is calculated for the full book as well.

For the moment I've used Calibre to save a plain epub (not kepub) version and the device has opened that successfully - but crashed again once when I went back to the table of contents, increasing my suspicion that the size of the TOC may be a factor.

Thanks for your thoughts!

[JSWolf]

Originally Posted by MGlitch

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

Congratulations on being WRONG Jon.

You have been WRONG at every step on this discussion, every single time you moved the goal posts to try and be right, you were still WRONG.

To review

Jon claimed page numbers were always at the bottom of a page in books - WRONG! They appear at the bottom and top in physical books, some even have the numbers on the side though it's less common.

Jon then claimed every ereader displayed page numbers only at the bottom. WRONG! ADE page numbers appear at the side.

Jon then tried to claim ADE page numbers have always appeared at the bottom. WRONG! Also slightly concerning since ADE page numbers being on the side of the screen was what made his previous statement of fact wrong.

How are you going to try and move the goal posts this time to try and not be so terribly WRONG Jon?

Sorry, but it's you who is so far out in left field, even the Hubble telescope cannot see you.

ADE has ALWAYS had page numbers at the BOTTOM. Yes, old versions did ALSO have page numbers at the right side. But they ALSO had page numbers at the BOTTOM. On a Kobo, the side page numbers are an option. They can be displayed or turned off. But the page numbers at the BOTTOM are still there. And as for pBooks, Readers are not pBooks and ALL Readers have page numbers at the BOTTOM.

I've used the very first version ADE on a Sony Reader PRS-505 and it had page numbers at the BOTTOM as well as the side. But, the Sony LRF/:RX reading software had the page numbers at the BOTTOM. All versions ADE have page numbers at the BOTTOM.

Please stop being WRONG. It's just so WRONG.

[rashkae]

Originally Posted by davidfor

Can you post a link to the book in the Kobo store? When a kepub is opened the first time, a word count is calculated for each chapter in the book. And with the change to show a full book page count based on the rendered pages, it is probably a large book would take to long to render. In this case, I'm a little surprised the device doesn't reboot due to a hung process.

It's quite possible, (I would say likely) that an oversized internal file will cause problems like this. But it's probably not the book size or book whole book progress that causes the problem. I just tested with a 1700000 word book, and the Kobo did not even seem to notice or pause on anything.. (I was expecting a longer Import on disconnect, since that's where the individual file sizes used to estimate pages would be calculated, but that zipped right by.)

[MGlitch]

Originally Posted by JSWolf

Sorry, but it's you who is so far out in left field, even the Hubble telescope cannot see you.

ADE has ALWAYS had page numbers at the BOTTOM. Yes, old versions did ALSO have page numbers at the right side. But they ALSO had page numbers at the BOTTOM. On a Kobo, the side page numbers are an option. They can be displayed or turned off. But the page numbers at the BOTTOM are still there. And as for pBooks, Readers are not pBooks and ALL Readers have page numbers at the BOTTOM.

I've used the very first version ADE on a Sony Reader PRS-505 and it had page numbers at the BOTTOM as well as the side. But, the Sony LRF/:RX reading software had the page numbers at the BOTTOM. All versions ADE have page numbers at the BOTTOM.

Please stop being WRONG. It's just so WRONG.

Oh Jon Jon Jonny boy, you’re so close to admitting it now you’re providing the evidence against yourself.

You claimed the page numbers were only at the bottom in each instance up until now. Yet you’re now moving the goal posts yet again to say “oh they’re also at the bottom”. Yes that’s rather the whole point Jonny, the page numbers were in multiple locations regardless of if it’s a physical book or ebook. Which means your claim that they have only ever been at the bottom was and still is wrong. No one cares that you used a Sony reader with the first version of anything because it’s not relevant what that reader did Jon. What is relevant is your claim that page numbers for every ereader have always only been at the bottom of the screen. A claim which has been so soundly refuted you’re even admitting it yet you’re trying to deny being wrong.

By the way I never denied page numbers have been at the bottom of the screen. I said they haven’t only ever been there. And as you now freely admit page numbers have been at the side of the screen you’ve admitted I was right even though you want to live in denial.

Seriously Jon, at this point it’s just sad. You were wrong and someone called you out on it, demonstrated that you were wrong, continued to show you were wrong every step of the way. You have constantly tried to move the goal post to try and be right and it’s failed every time.

[JSWolf]

Originally Posted by MGlitch

Oh Jon Jon Jonny boy, you’re so close to admitting it now you’re providing the evidence against yourself.

You claimed the page numbers were only at the bottom in each instance up until now. Yet you’re now moving the goal posts yet again to say “oh they’re also at the bottom”. Yes that’s rather the whole point Jonny, the page numbers were in multiple locations regardless of if it’s a physical book or ebook. Which means your claim that they have only ever been at the bottom was and still is wrong. No one cares that you used a Sony reader with the first version of anything because it’s not relevant what that reader did Jon. What is relevant is your claim that page numbers for every ereader have always only been at the bottom of the screen. A claim which has been so soundly refuted you’re even admitting it yet you’re trying to deny being wrong.

By the way I never denied page numbers have been at the bottom of the screen. I said they haven’t only ever been there. And as you now freely admit page numbers have been at the side of the screen you’ve admitted I was right even though you want to live in denial.

Seriously Jon, at this point it’s just sad. You were wrong and someone called you out on it, demonstrated that you were wrong, continued to show you were wrong every step of the way. You have constantly tried to move the goal post to try and be right and it’s failed every time.

I didn't think you could be any more wrong. But you are even more wrong then before. You are so wrong I don't know if it's possible to be any more wrong. But I think you'll probably surprise me and be even more wrong yet again. The level of wrongness you are showing is staggering.

Anyway, page numbers are much more efficient at the bottom. When you change the page, most of the time you look at the top of the screen. So if you want to see the number of screens left in the chapter or the time or the %, it's there at the top where your eyes are looking. At the bottom, you then have to shift your view back to the bottom and then back to the top to continue reading.