View Single Post
Old 04-03-2008, 01:32 PM   #182
delphidb96
Wizard
delphidb96 ought to be getting tired of karma fortunes by now.delphidb96 ought to be getting tired of karma fortunes by now.delphidb96 ought to be getting tired of karma fortunes by now.delphidb96 ought to be getting tired of karma fortunes by now.delphidb96 ought to be getting tired of karma fortunes by now.delphidb96 ought to be getting tired of karma fortunes by now.delphidb96 ought to be getting tired of karma fortunes by now.delphidb96 ought to be getting tired of karma fortunes by now.delphidb96 ought to be getting tired of karma fortunes by now.delphidb96 ought to be getting tired of karma fortunes by now.delphidb96 ought to be getting tired of karma fortunes by now.
 
Posts: 2,999
Karma: 300001
Join Date: Jan 2007
Location: Citrus Heights, California
Device: TWO Kindle 2s, one each Bookeen Cybook Gen3, Sony PRS-500, Axim X51V
Quote:
Originally Posted by cmbs View Post
Ok. Mobipocket Reader was free. Cybook cost $350. I don't much mind page number bugs in free software. I do mind it in $350 devices.

Personally, I find it useless in it's present state; and the fact they have it leads one to believe it would be easy to add page numbers to the books since the numbers are already being calculated.
That's your opinion and you have the right to it, but I think most typical readers would find it to be invalid.

Quote:
A specific page begins with a specific line and ends with a specific line. The fact that you can place a link somewhere in the middle of the page and put that part at the top doesn't change the concept that it's the middle of the page, and further down a new page begins. A link to a specific page number (as in go to page number feature) should go to the top of the page. The number of fixed pages can (theoretically) be calculated, it has nothing to do with the fact that portions of two pages can be displayed at one time. This has never confused me, I don't see the problem.
What I think is happening is that Bookeen started developing their Boo Reader and, as they had a licensing arrangement with Mobipocket, asked for help on how Mobi software does things. And Mobi supplied the algorithm used for determining page positioning, etc. I'm pretty sure Bookeen implemented that way in order to be as compliant to Mobi's internal standard as they could. Well, in much of their implementation, doing so produced quality features. But in this instance - page determination - following Mobi's approach turned out to be, shall we say, 'flawed'?

Yet, here you are, on the one hand demanding they be as close to MobiReader as possible, and on the other hand, bitching and moaning because they are doing it exactly the same way - when doing so doesn't meet your ideals. Boo-hoo-hoo. Cry me a river.

Derek
delphidb96 is offline   Reply With Quote