View Single Post
Old 07-08-2009, 08:31 AM   #32
zerospinboson
"Assume a can opener..."
zerospinboson ought to be getting tired of karma fortunes by now.zerospinboson ought to be getting tired of karma fortunes by now.zerospinboson ought to be getting tired of karma fortunes by now.zerospinboson ought to be getting tired of karma fortunes by now.zerospinboson ought to be getting tired of karma fortunes by now.zerospinboson ought to be getting tired of karma fortunes by now.zerospinboson ought to be getting tired of karma fortunes by now.zerospinboson ought to be getting tired of karma fortunes by now.zerospinboson ought to be getting tired of karma fortunes by now.zerospinboson ought to be getting tired of karma fortunes by now.zerospinboson ought to be getting tired of karma fortunes by now.
 
zerospinboson's Avatar
 
Posts: 755
Karma: 1942109
Join Date: Mar 2008
Location: Local Cluster
Device: iLiad v2, DR1000
Quote:
Originally Posted by HarryT View Post
That has nothing whatsoever to do with the file format. If your particular book has double-spaced paragraphs, it's because that's what the creator of that book specified, just as he could have done with a PDF. It's certainly not inherent in the format.
The mobipocket reader for PC displays the book with no separation between "paragraphs", whereas the iLiad renders the exact same file with 2-3 full lines of white.
My point isn't whether it's inherent in the format, my point is that the way the same file is rendered is inconsistent across different platforms, and non-user-specifiable. (and secondly, that the way the iLiad renders it is sub-optimal)
And that has everything to do with the file format, because non-reflowable texts do not suffer from this problem (as it isn't so much the inconsistency that annoys me, but the fact that there is so much white space between obviously-meant-to-be-contiguous 'paragraphs')

Last edited by zerospinboson; 07-08-2009 at 08:35 AM.
zerospinboson is offline   Reply With Quote