Quote:
Originally Posted by Jim Chapman
Fair enough - though that's not the case with most ebooks on the market, which is why my general expectation that I'd want to simplify/ignore some formatting, in the interest of readability on PDAs/phones. Obviously the right thing is to let the device user make the decision between "how faithfully do I want to see the author's intended text" and "how much do I want the book to look like a block of flowing text, filling my PDA screen". As I refine the program, I'd expect to introduce options of that kind.
|
Hmm, an advanced option would be a good idea, maybe. Just like the sub-folder thingie. I know I wouldn't want those empty lines on my 2.4" HTC phone, but I do want them on my 3.4" PDA.
Quote:
Originally Posted by Jim Chapman
Not arguing with you there. My aim was not to implement a fully-capable and standards-compliant renderer (at least, not in version 0.9 of the program). Rather, I was aiming to produce something simple and robust that would at a minimum put the author's words on the page, and have a reasonable stab at some kind of formatting. And for my initial release, I've focussed mainly on producing intelligible rendering of a reasonable number of ePubs that are actually out there and being published by the Gutenberg project, Feedbooks, and suchlike.
Thanks for your interest, and please do continue to share your ideas.
Jim
|
Oh, you succeeded in make it simple and robust! It's light and easy to use. Just implement the CSS support and it'll be installed on my HTC before you can say "go"...
But I'm a web developer myself and I always shudder when I see inline formatting code that isn't styles based... Can't help it when somebody mentions XHTML and align in the same sentence
