Quote:
Originally Posted by kovidgoyal
Do I really need to point out the difference between parsers and parsing libraries to you?
|
No.
My point is that those libraries contain code, and that code has it's own level of complexity. You're not diminishing complexity by using someone else's code, you're just diminishing the amount of work you as the programmer need to perform. And I'm not worried about the work involved, but the resources consumed.
Quote:
Originally Posted by kovidgoyal
Umm in a standard that has support for SVG images and XHTML rendering you're worried about the overhead of HTML parsing? And just to make it clear note I said *rendering* and not parsing.
|
SVG is a good point. That I concede.
But supposing one creates an XHTML parser + renderer that doesn't support SVG, one could support the vast majority of epub books out there (I'm not saying this in and of itself is a good thing). Lenient HTML parsing is non-trivial.
And it's not just the resources. Do we really need the agony of different rendering with different Reading Systems if people start using HTML? Look at the modern web. You know that any designer worth his salt has to check each any every goddamn browser out there for incompatibilities, quirks etc. And it's not just because of IE. Do we really want that for ebooks?
How about we stick to the prescribed standard for once? Let's try that out and see how it goes. And to get there, the
mentality has to change. People need to start
caring about standard compliance.
Let's at least try to.