View Single Post
Old 06-29-2008, 12:10 PM   #11
tompe
Grand Sorcerer
tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.
 
Posts: 7,145
Karma: 4315826
Join Date: Oct 2007
Location: Linköpng, Sweden
Device: Nexus 7, Nexus 5, iPad 2, Kindle PW
Quote:
Originally Posted by JSWolf View Post
The problem is that the Kindle's eBook format AZW is just a slightly modified Mobipocket format. And thus you have the issue of old technology developed for screen of a small size such as PDA and cell phones. So images tend to be small when dealing with a 6" eink screen. I was looking at Winston Churchill's books on WWII and found the images to be way too tiny to be of any use.
Since Amazon has full control and can update the readers the format can do anything they want. There is no reason for an awz file to have small images since it does not have to be built for many devices.

Quote:
What really needs to be done is for Mobipocket to come out with a new version of their reader that is written fresh from the start. The way it's written, it has a host of bugs that cannot be fixed unless what we have now is scrapped and started over. This would also give them a chance to fix the image issues and make sure that any new eBooks have large enough images.
The reader is not the problem. The format specification is. So they have to introduce a new format in the same way that Amazon has introduced a new format.

Quote:
Most of the bugs/flaws are due to a 64k block limit when going forward/backward in the eBooks. Thus, they have to limit the physical size of the images otherwise it breaks this block size. They break the eBooks up into 64k blocks supposedly for speed.
They do it because the specification says it should be done. The blocks do not matter if the specification defines images that can be saved in more than one block.

Quote:
But what good is speed if it causes too many issues. If they did away with that, they could have larger images and working page numbers among other fixes.
Page number problems have nothing to do with block size.
tompe is offline   Reply With Quote