> If anyone wants REAL pain, then we should go back to BNF... Ironically, if one wants to implement a SVG reader they have to use the BNFs provided in the spec

> If anyone wants REAL pain, then we should go back to BNF... Ironically, if one wants to implement a SVG reader they have to use the BNFs provided in the spec (for paths and whatnot). Though the SVG 1.1 DTD is pretty nice to work with, I've built a SVG DOMish generator for both c++ and python (which takes forever to compile) so one, err...me, doesn't have to deal with all the underlying XML craziness. One of these days I'll get around to finishing the path parser, color parser, transform parser, &etc...