Quote:
Originally Posted by Valloric
So you're saying it's easy to create an HTML parser because there are a lot of open source HTML parsers out there?
Do I need to respond to that? Or do you see how silly that sentence is?  |
Do I really need to point out the difference between parsers and parsing libraries to you?
Quote:
But you have to take into account the complexity involved with a full-fledged HTML parser. Portable device makers would really love it if they could just expect XHTML content in epub documents (and they should, because basic HTML is not supported by OPS) because then they could just use a lean, fast, lightweight parser. It would require less memory, CPU and power.
It's this "lets not get too religious about standards" attitude that makes that less likely to happen. So at the very least, don't recommend to other people that they flat-out ignore the standard and put HTML in source documents. XHTML is not that difficult to produce, and Tidy can convert the majority of HTML into conforming XHTML.
|
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.