cxml-devel

Download

cxml-devel@lists.common-lisp.net

October 2011

4 participants
2 discussions

[cxml-devel] seeking suggestion for handling malformed attribute names
by Russell Kliese 29 Oct '11

29 Oct '11

I have been using closure-html and cxml to extract data from web pages. Up until now it has worked quite well, but I have come across a web page that has quite extraordinarily malformed html markup. I am looking for suggestions on how to continue parsing even when attribute names are malformed. Here is a self-contained example containing some of the offending markup: (require :closure-html) (require :cxml-stp) (defvar *html-str*) (setf *html-str* "<html> <body> <table> <tr><td vertical-align:=\"\" ;=\"\"></td></tr> </table> </body> </html> ") (chtml:parse *html-str* (cxml-stp:make-builder)) This example give CXML:WELL-FORMEDNESS-VIOLATION. I guess I could write a custom SAX handler to skip attributes with these errors, but is there a more simple solution? Should the chtml parser be patched to handle this case? Are there any other ways to make parsing more robust? Or is this markup beyond hope of repair? Regards, Russell

2 3

[cxml-devel] parsing from a http stream (no EOF at the end)
by Attila Lendvai 03 Oct '11

03 Oct '11

cxml:parse is stuck waiting for an EOF even after the last closing tag when parsing from a stream (in my case it's a http stream in a server entry point. the client waits for the server to react, the server waits for the EOF). looking at the code i get the impression that it was never meant to be used like this, an EOF is pretty much mandatory. could someone comment on this? was cxml ever meant to support such use-case, just noone really needed it yet? any plans for supporting this? any hints are appreciated, -- attila Notice the erosion of your (digital) freedom, and do something about it! PGP: 2FA1 A9DC 9C1E BA25 A59C 963F 5D5F 45C7 DFCD 0A39 OTR XMPP: 8647EEAC EA30FEEF E1B55146 573E52EE 21B1FF06

3 3