![]() |
#1 |
Enthusiast
![]() Posts: 19
Karma: 10
Join Date: Dec 2007
Location: Bulgaria
Device: Gen3(brick)/NOOK/NOKIA E52
|
Page numbers, AGAIN
A week ago I've changed my mobile to a smart one (symbian) and installed a MobiReader on it just in case.
What a surprise when I see page numbers in PRC files. Numbers reflow as expected when changing font size. Now do you see any obstacles for having such feature in cybook. Especially when they use "mobi" source code for their reader. See attached screen captures from the phone |
![]() |
![]() |
![]() |
#2 |
eBook Enthusiast
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 85,544
Karma: 93383043
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
|
This really shouldn't surprise you. All versions of the Mobi reader except the Gen3 display page numbers.
The problem is, they are useless for finding your place in a book. Try this little experiment: 1. Go to the start of the book. 2. Page forward a page at a time until you get to a recognisable page in the book (eg the start of a chapter). Make a note of the displayed page number. 3. Go back to the start of the book, do a "Goto Page" and enter the page number you noted. Are you at the same place in the book that you were before? I think you'll find that you aren't! Jumping to a page number in a Mobi book takes you to a wildly different location from paging through it a page at a time, and therefore cannot be used to note pages that you'd like to return to. This inaccuracy of page numbers makes that effectively useless (IMHO) and I entirely understand why Bookeen made the decision not to display them. |
![]() |
![]() |
Advert | |
|
![]() |
#3 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,229
Karma: 543210
Join Date: Feb 2008
Location: Gatlinburg, Tennessee
Device: Kindles: Paperwhite Signature Ed., Oasis 2, Voyage
|
|
![]() |
![]() |
![]() |
#4 |
Fanatic
![]() ![]() ![]() ![]() ![]() Posts: 527
Karma: 470
Join Date: Sep 2007
Location: The Netherlands
Device: Kindle Oasis
|
And of course there is this other 'little' problem even if page numbers themselves were acurate You make a note of an important part of your book. You remember it was on page 246. You go on reading and after a while you find it is a bit to dark and you increase the font size or change the font type (I do that all the time) When you want to go back to the 246 you'll end up in a totally different part of the book.
|
![]() |
![]() |
![]() |
#5 | |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 4,395
Karma: 1358132
Join Date: Nov 2007
Location: UK
Device: Palm TX, CyBook Gen3
|
Quote:
But, if you don't change fonts while reading a book (I never do), it would be an improvement over what we have now. |
|
![]() |
![]() |
Advert | |
|
![]() |
#6 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,229
Karma: 543210
Join Date: Feb 2008
Location: Gatlinburg, Tennessee
Device: Kindles: Paperwhite Signature Ed., Oasis 2, Voyage
|
They would be -- if they worked. Which they don't in Mobipocket Reader on any platform that I have used it on. Since they don't, I'm fine with the progress bar alone.
|
![]() |
![]() |
![]() |
#7 | |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 7,452
Karma: 7185064
Join Date: Oct 2007
Location: Linköpng, Sweden
Device: Kindle Voyage, Nexus 5, Kindle PW
|
Quote:
FBReader has working page number. Also what is needed most is not page number for accurate referencing but some measurement that can be used to accuately indicate how much of the total lengt of the work you have read, |
|
![]() |
![]() |
![]() |
#8 | |
Sir Penguin of Edinburgh
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 12,375
Karma: 23555235
Join Date: Apr 2007
Location: DC Metro area
Device: Shake a stick plus 1
|
Quote:
A lot of its behavior is based on its arbitrary page size, and I've found that very annoying. |
|
![]() |
![]() |
![]() |
#9 |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 7,452
Karma: 7185064
Join Date: Oct 2007
Location: Linköpng, Sweden
Device: Kindle Voyage, Nexus 5, Kindle PW
|
Yes and that is why it is working. Maybe we shoud call it "progress number" and not "page number" to avoid confusion.
|
![]() |
![]() |
![]() |
#10 | |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,229
Karma: 543210
Join Date: Feb 2008
Location: Gatlinburg, Tennessee
Device: Kindles: Paperwhite Signature Ed., Oasis 2, Voyage
|
Quote:
|
|
![]() |
![]() |
![]() |
#11 |
eBook Enthusiast
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 85,544
Karma: 93383043
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
|
Perhaps the "answer" is to do what the Kindle does, which is to display a "number" which isn't related to "pages", but simply to a position in the file. IIRC, the Kindle numbers in units of 128 bytes.
|
![]() |
![]() |
![]() |
#12 |
Connoisseur
![]() ![]() ![]() ![]() ![]() ![]() Posts: 51
Karma: 514
Join Date: Mar 2008
Device: Bookeen Cybook
|
If Pagenumbers don't work, why does it have to be a progress "bar".
You can't go to the exact location in a text with just a bar without searching quite a bit. Why can't it be a percentage number instead ? e.g. 23,57 % The device could just count all the letters of a text and then calculate the percentage for the first letter of a page. Then the font size wouldn't matter very much with this method. If rounded to 2 digits after the decimal point you could exactly differ between 10.000 pages. Even if you are using a very large font size you would be only a few pages of mark. |
![]() |
![]() |
![]() |
#13 |
frumious Bandersnatch
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 7,542
Karma: 19001583
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
|
To give a bit more information, it could say something like:
23,57% of ~357 pp. Where the percentage is calculated byte-wise or character-wise, or whatever. And the total number of pages is calculated according to the amount of text shown in the current page (so, it would change even with every page turn). |
![]() |
![]() |
![]() |
#14 | |
Fanatic
![]() ![]() ![]() ![]() ![]() Posts: 527
Karma: 470
Join Date: Sep 2007
Location: The Netherlands
Device: Kindle Oasis
|
Quote:
I can imagine that you cannot simply count the number of bytes divided by something for positioning in the file. That will give you a problem when there are pictures in the book. It will give you things like 1..2..3..10234..10235. Of course you can program around it, but I rather have that the concentrate on searching in the library, a one button bookmark and programmable buttons so I can assign buttons to the funtion that I like. I couln'd care less about pagenumbers, I never use them, the bar is good for me. |
|
![]() |
![]() |
![]() |
#15 |
Resident Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 78,930
Karma: 143098300
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Look, you bought a device that has a reader on it that is known to have issues with page numbers. Get over it. The chances of Mobipocket fixing page numbers in your Gen3's lifetime is not going to happen.
If page numbers really mean that much to you, then go get a Sony Reader. ![]() |
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
page numbers in pdf | jacktanner | Calibre | 2 | 10-08-2011 08:11 PM |
Page numbers | Fincary | Astak EZReader | 4 | 02-18-2010 03:06 PM |
page numbers | nenad | Amazon Kindle | 2 | 12-19-2009 09:01 AM |
DX, PDF, and Page Numbers | tklaus | Amazon Kindle | 1 | 06-28-2009 08:20 PM |
Page numbers (again) | Prospect | Workshop | 50 | 04-10-2008 02:19 AM |