View Single Post
Old 07-29-2016, 03:08 PM   #36
Faterson
pokrývač škridiel
Faterson ought to be getting tired of karma fortunes by now.Faterson ought to be getting tired of karma fortunes by now.Faterson ought to be getting tired of karma fortunes by now.Faterson ought to be getting tired of karma fortunes by now.Faterson ought to be getting tired of karma fortunes by now.Faterson ought to be getting tired of karma fortunes by now.Faterson ought to be getting tired of karma fortunes by now.Faterson ought to be getting tired of karma fortunes by now.Faterson ought to be getting tired of karma fortunes by now.Faterson ought to be getting tired of karma fortunes by now.Faterson ought to be getting tired of karma fortunes by now.
 
Faterson's Avatar
 
Posts: 1,525
Karma: 3300000
Join Date: Oct 2011
Location: Bratislava, Slovakia
Device: 3*iPad, SamsungNote & Tabs, 2*OnyxBoox, Huawei 8″, PocketBook
Exclamation

Quote:
Originally Posted by eschwartz View Post
I live to entertain.
Keep your day job, because you fail miserably in that regard.

Quote:
Originally Posted by ekbell View Post
I happen to like knowing how many 'page' turns particular book or chapter will have (how many times will I be paging forward?).
Of course – that's the common-sense, everyday reader's use of pages, not for the outlandish, geeky purpose of cross-referencing them to other layout settings, devices, apps, or platforms. But don't you dare use common sense here in MobileRead forums – it's the geeks' playground here, scratching each other's backs, and common sense is decidedly frowned upon here.

Quote:
Originally Posted by ekbell View Post
it would be nice to have a clear distinction between types of 'page' counts.
Exactly. I have nothing against the current pseudo-"page" count method in Marvin, as long as it's not the only one, because if it's the only available page-count option, it constitutes an in-your-face internal conflict within Marvin itself, in that it calls pages in chapters and pages in books the same thing, but calculates them in radically different manners, on the same reading device, using the same layout settings, within a single footer (!) on the same screen. Really, what could be more glaringly unacceptable, from the point of view of software consistency?
Faterson is offline   Reply With Quote