Quote:
Originally Posted by silkpag
Yeah, but there is nothing in the .epub specification which requires the division of text. It's certainly possible; anyone who's lived with Sony has done it, but it's not in the spec and by definition not the fault of the content provider. This need to divide should be properly labeled, and other open-source programmers (like DAISY, if they still care about .epub) should be informed.
Come on, we're talking text. Just... text. In 2008. Compare the hardware in the average smartphone to the hardware in a typical PC running Windows 95...
/Aside, ever noticed that books from the Sony store by major publishers appear not to have any divisions or tables of contents whatsoever? I'm probably not the only one who will resent this attitude...
|
Yes, I fully agree with you regarding the specs. It is an issue that should be discussed within IDPF. I think that the main problem here is that IDPF designed ePub as both a source format and an end-user format.
From a source format perspective, there's no reason to discuss these sort of issues. But from an end-user perspective, you really need to think about these sorts of problems.
Pagination can be a real resource hog: ask Kovid for example, when he wrote his LRF viewer. That's also one of the reasons why LRF books are pre-processed on the desktop if you use Sony's software to transfer books to your PRS.