Quote:
Originally Posted by pepak
That's easy! Unlike computers, e-book devices don't use the powerful CPUs and loads of memory. The splitting allows them to process a small amount of data at a time, which should require less CPU power and less memory.
|
Well, see, that is a valid argument - but appears not to be true. I calculated the average speed of ebook processors to be 355MHz, none of which had less then 64MB RAM. See, that doesn't seem handicapped to me. None should have the problem of not fitting a book into RAM.
...but then I figured out why it must be; when content is reflowed, ie by changing font size, that must all be applied. That would take some time. And so the limit makes a bit of sense - although I dearly wish it was larger.
But what I was also asking was where I should split them. Having a split in the middle of a chapter would be annoying, but for best responsiveness, I might want to make a file a chapter. That would also simplify the ToC. Hell, maybe it should have been written into the standard like that.
What are your thoughts?