02-07-2024, 12:52 PM | #46 | |
Samurai Lizard
Posts: 14,285
Karma: 66698846
Join Date: Nov 2009
Device: NookColor
|
Quote:
Something to consider: Rather than page numbers, why not just use a percentage of the entire book? That way where would be consistency when it comes to where parts of the book fall. As an example, Chapter 7 might begin at around 60% of the book and that will not change despite changes in the books formatting. |
|
02-07-2024, 01:09 PM | #47 | |
Bibliophagist
Posts: 35,964
Karma: 145678910
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Forma, Clara HD, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
Quote:
As for percent over page numbers? I prefer percent but people complain that percent does not give you an idea of how much longer to finish the book. Say you are 60% completed in War and Peace and 60% completed in The Old Man and the Sea, it is going to take a titch longer to read 234,915 words compared to 10,800 words. |
|
02-07-2024, 01:15 PM | #48 |
Grand Sorcerer
Posts: 10,282
Karma: 225099840
Join Date: Jan 2014
Location: Estonia
Device: Kobo Sage & Libra 2
|
A correctly made TOC in epub will allow you to go to chapters, sections et al also. And it's trivial to make a correct TOC with Calibre.
|
02-07-2024, 08:38 PM | #49 | |
Samurai Lizard
Posts: 14,285
Karma: 66698846
Join Date: Nov 2009
Device: NookColor
|
Quote:
Using War and Peace as an example, if formatted for printing on a standard sheet of typing paper using 10 pitch Courier New with 1 inch margins works out to 585 words per page (assuming an average word length of five characters plus a space). That, in turn, works out to about 402 pages for the entire book. However, reduce the size of the type to 12 pitch and it works out to 702 words per page, with the total number of pages being 335 pages for the entire book. Of course, most e-book screens are smaller than that and I doubt that people would actually print the book using the formatting I described (I used it because the numbers were easy to figure out), but the same principle would work. I sure that to many readers a screen and a page are the same thing when it comes to reading. To me, both would be easy to understand. It would be like (using the first format example above) "I'm on screen/page 305 and so I've got 97 screens/pages left in the book." It's a simple and easy-to-explain method of showing progress through a book, one that could be easily added to the e-book software as an option. |
|
02-07-2024, 10:29 PM | #50 |
Bibliophagist
Posts: 35,964
Karma: 145678910
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Forma, Clara HD, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
Looking at War and Peace on Amazon.ca, I checked a random selection of 4 paperback and 4 hardcover editions. The print editions show page counts of 1831 pages, 1440 pages, 1296 pages and 734 pages for the paperback editions and 1392 pages, 1399 pages, 1140 pages and 928 pages for 4 hardcover editions. Tell me about the ONE TRUE PAGE NUMBERS again...
As for your screen/page 305 and 97 screen/pages to go? That depends on many options though if you are reading on a Kobo, it does show the book and chapter page counts which for a kepub is close to a screen per page. It is not really transferable to another device since someone else may be using a different font, different line heights, different margins, etc. even when reading the same edition of the ebook. That is the only good item I find with Adobe's Synthetic Page Numbers algorithm where page 259 is page 259 regardless of formatting choices. |
02-07-2024, 10:50 PM | #51 |
Grand Sorcerer
Posts: 10,282
Karma: 225099840
Join Date: Jan 2014
Location: Estonia
Device: Kobo Sage & Libra 2
|
One number to rule them all...
Another day, another argument discussion about page numbers on MR... |
02-08-2024, 01:32 PM | #52 | |
Gentleman and scholar
Posts: 11,070
Karma: 108646675
Join Date: Jun 2015
Location: Space City, Texas
Device: Clara HD; Nook ST w/Glowlight, (2015) Glowlight Plus, Paperwhite 3
|
Quote:
I don't understand why a typical table of contents in ePub or one of the other ebook formats doesn't do exactly what you need? I've never had trouble navigating to a chapter regardless of any changes made to the size of the text. |
|
02-09-2024, 11:35 AM | #53 | |
Samurai Lizard
Posts: 14,285
Karma: 66698846
Join Date: Nov 2009
Device: NookColor
|
Quote:
I've tried other formats a few times and I didn't like the results. As an example, I had an e-reader that was supposed to support RTF files, so I tried it. Unfortunately, it gave me unpredictable results (such as being unable to get it to display a serif typeface). Likewise with EPUB I sometimes get formatting issues such as widows and orphans that I just have to live with. |
|
02-09-2024, 01:01 PM | #54 |
Bibliophagist
Posts: 35,964
Karma: 145678910
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Forma, Clara HD, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
My basic ePub stylesheet includes widows: 1; and orphans: 1;—do not use 0 as that is undefined and in many cases, using 0 will use to whatever the renderer default is (2 or 3 are common).
|
02-09-2024, 02:41 PM | #55 | |
the rook, bossing Never.
Posts: 11,325
Karma: 85874895
Join Date: Jun 2017
Location: Ireland
Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper11
|
Quote:
A setting of 0 (or any CSS error) can cause some renderers to ignore all the CSS. |
|
02-09-2024, 03:23 PM | #56 | |
Resident Curmudgeon
Posts: 74,349
Karma: 129333690
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
|
|
02-09-2024, 03:26 PM | #57 |
Resident Curmudgeon
Posts: 74,349
Karma: 129333690
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Using ADE/RMSDK, 0 is the same a 1. I used to use 0. Now I use 1. No difference. But since 1 works, I'll stick with it in case I'm ever using a different program that make not like 0.
|
02-09-2024, 03:27 PM | #58 |
Resident Curmudgeon
Posts: 74,349
Karma: 129333690
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
ADE/RMSDK being a stickler for correct CSS does not cause a problem with widows and orphans to 0. It works the same as setting them to 1.
|
02-10-2024, 10:41 PM | #59 |
Gentleman and scholar
Posts: 11,070
Karma: 108646675
Join Date: Jun 2015
Location: Space City, Texas
Device: Clara HD; Nook ST w/Glowlight, (2015) Glowlight Plus, Paperwhite 3
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
page (screen) turning by random lengths.. | Thirteen OBD | Viewer | 17 | 01-14-2021 08:17 AM |
Going Crazy Turning The Page | Lordblacknail | Amazon Kindle | 13 | 12-24-2014 03:02 PM |
Glo Page turn goes crazy | arturg | Kobo Reader | 7 | 03-03-2014 07:18 AM |
Electronic books and printed different lengths | jbcohen | Reading Recommendations | 13 | 04-21-2012 05:01 PM |
List of countries and there copyright lengths | thinkpad | Upload Help | 0 | 10-08-2010 01:55 PM |