View Single Post
Old 01-13-2015, 02:31 PM   #15
pdurrant
The Grand Mouse 高貴的老鼠
pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.
 
pdurrant's Avatar
 
Posts: 74,010
Karma: 315160596
Join Date: Jul 2007
Location: Norfolk, England
Device: Kindle Oasis
Quote:
Originally Posted by JSWolf View Post
One reason Kindles don't have such a problem is that most KF8 eBooks are created from an ePub source. So since the ePub is made to the mobile specification, the KF8 eBook will be as well.
No, this won't do. That is not at all a reason that Kindles don't have this problem.

Kindles really don't have this problem at all, even for books that aren't split into nice sub-260KB chunks internally. The original Kindle didn't have this problem, and that used Mobi format files that were just one great big block of HTML 3.2ish text.

The Kindle rendering software has always been able to cope with rendering parts of large blocks of HTML, and that hasn't changed with the switch to AZW3 format.

Mind you, the same is now true, I think, of more recent versions of Adobe's RMSDK, so the 260JB limit only really affects older devices.
pdurrant is offline   Reply With Quote