September 2006 - cxml-devel - mailman3.common-lisp.net

[cxml-devel] Re: & in file parsed by CXML
by David Lichteblau 17 Sep '06

17 Sep '06

Hi Mitch, I have just checked in a fix for the bug you reported on the LispWorks mailing list. Please update to current CVS and try again. Thanks, David

2 1

[cxml-devel] CDATA doesn't preserve whitespace
by Sunil Mishra 16 Sep '06

16 Sep '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I've noticed the following in ACL7 on the attached document: CL-USER(115): (cxml:parse-file "C:\\graph.xml" (rune-dom:make-dom-builder)) #<RUNE-DOM::DOCUMENT @ #x212c5a82> CL-USER(116): (dom:map-document (cxml:make-namespace-normalizer (cxml:make-octet-stream-sink *standard-output*)) *) <svg xmlns="http://www.w3.org/2000/svg">
 <script type="text/css">
 
 
 
 </script>
</svg> #<MULTIVALENT stream socket connected from localhost/3813 to localhost/3817 @ #x205003d2> Now, it appears that this doesn't seem to be a problem for the javascript processor in firefox. It still seems to process lines and quotes and so on that have been thus escaped correctly. The XML 1.1 proposal in its description of CDATA states that the only markup that will be recognized by the XML processor is the CDATA end: ``Within a CDATA section, only the CDEnd string is recognized as markup, so that left angle brackets and ampersands may occur in their literal form; they need not (and cannot) be escaped using "<" and "&". CDATA sections cannot nest.'' Can cxml please correctly follow this requirement? Thanks, Sunil -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFC03QjRnqWMAEf1cRAoCLAKC0ZSIqVYeOHEimdQwdLTNsCgdrJgCdECue DAdGZCA+vOYOBDBcI5FRH8g= =5NkM -----END PGP SIGNATURE-----

2 2

[cxml-devel] Escape characters in first tag cause well-formed error
by Mitch Berkson 16 Sep '06

16 Sep '06

When I parse a file containing escape characters (& or <) in the first tag, CXML:parse-file gives the error message: "Error: Document not well-formed: entity not defined: amp". Including the characters in other tags works fine. Is this the expected behavior? Example: Case 1 (escape character in first tag): REPL> (with-open-file (s "example.xml" :direction :output :if-exists :supersede) (write-string "<test a='b&'><child/></test>" s)) --> "<test a='b&'><child/></test>" REPL> (cxml:parse-file "example.xml" (cxml-xmls:make-xmls-builder)) --> Error: Document not well-formed: entity not defined: amp Context: Line 1, column 16 in file://+ Case 2 (escape character in second tag): REPL> (with-open-file (s "example.xml" :direction :output :if-exists :supersede) (write-string "<test a='b'><child a='b&'/></test>" s)) --> (cxml:parse-file "example.xml" (cxml-xmls:make-xmls-builder)) ("test" (("a" "b")) ("child" (("a" "b&")))) Edi Weitz suggests that ENSURE-DTD may be called too late in the P/DOCUMENT function. Thanks for any help. Mitch

1 0

[cxml-devel] Latest CVS checkout is broken
by Ralf Mattes 13 Sep '06

13 Sep '06

This is on GNU/Linux Intel with SBCL: CL-USER ý (require :cxml) ; compiling file "/LISP/cxml/xml/xml-name-rune-p.lisp" (written 13 SEP 2006 05:45:04 PM): ; in: LAMBDA NIL ; (RETURN T) ; ==> ; (RETURN-FROM NIL T) ; ; caught ERROR: ; return for unknown block: NIL The function CXML::WHILE is undefined. [Condition of type UNDEFINED-FUNCTION] Restarts: 0: [RETRY] Retry performing #<ASDF:COMPILE-OP NIL {B5AAAA9}> on #<CXML-SYSTEM::CLOSURE-SOURCE-FILE "xml-name-rune-p" {AFD6801}>. 1: [ACCEPT] Continue, treating #<ASDF:COMPILE-OP NIL {B5AAAA9}> on #<CXML-SYSTEM::CLOSURE-SOURCE-FILE "xml-name-rune-p" {AFD6801}> as having been successful. 2: [ABORT-REQUEST] Abort handling SLIME request. 3: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread" {AE16669}>) Backtrace: 0: ("bogus stack frame") 1: ((LABELS CXML::LETTER-RUNE-P) 0) 2: ((LABELS CXML::NAME-RUNE-P) 0) 3: ((LABELS CXML::PREDICATE-TO-BV) #<FUNCTION (LABELS CXML::NAME-RUNE-P) {B817DA5}>) 4: (NIL) 5: (SB-INT:EVAL-IN-LEXENV (FUNCALL (COMPILE NIL (QUOTE #))) #<NULL-LEXENV>) 6: (READ-PRESERVING-WHITESPACE #<SB-SYS:FD-STREAM for "file /LISP/cxml/xml/xml-name-rune-p.lisp" {B6B6161}> NIL #<SB-SYS:FD-STREAM for "file /LISP/cxml/xml/xml-name-rune-p.lisp" {B6B6161}> T) 7: (READ-PRESERVING-WHITESPACE #<SB-SYS:FD-STREAM for "file /LISP/cxml/xml/xml-name-rune-p.lisp" {B6B6161}> NIL #<SB-SYS:FD-STREAM for "file /LISP/cxml/xml/xml-name-rune-p.lisp" {B6B6161}> NIL) 8: (READ #<SB-SYS:FD-STREAM for "file /LISP/cxml/xml/xml-name-rune-p.lisp" {B6B6161}> NIL #<SB-SYS:FD-STREAM for "file /LISP/cxml/xml/xml-name-rune-p.lisp" {B6B6161}> NIL) 9: (SB-C::READ-FOR-COMPILE-FILE #<SB-SYS:FD-STREAM for "file /LISP/cxml/xml/xml-name-rune-p.lisp" {B6B6161}> 242) 10: (SB-C::SUB-SUB-COMPILE-FILE #<SB-C::SOURCE-INFO >) 11: ((LAMBDA NIL)) 12: (SB-C::%WITH-COMPILATION-UNIT #<CLOSURE (LAMBDA NIL) {B6B5295}>) 13: (SB-C::SUB-COMPILE-FILE #<SB-C::SOURCE-INFO >) 14: (COMPILE-FILE #P"/LISP/cxml/xml/xml-name-rune-p.lisp") Hmm, file xml/xml-name-rune-p.lisp, line 110 has a 'while' -- where is this supposed to be defined? HTH Ralf Mattes

2 1

[cxml-devel] skipping the DTD decl. when `validate' is `nil'
by Sean Champ 09 Sep '06

09 Sep '06

Hello, I've noticed that the function CXML::P/DOCUMENT calls the function CXML::P/DOCTYPE-DECL whether or not CXML::P/DOCUMENT has received a non-nil VALIDATE argument. I'd thought to try and make a patch about that, myself, but I'm not sure how to address the matter. If the input stream is not being validated, the contents of the doctype decl should not matter, for anything -- need not be put, in any part, as an argument to CXML::XSTREAM-OPEN-EXTID. Yet, when the parser is validating, the text of the doctype decl. still must be 'skipped' by the parser. Looking at CXML::P/DOCTYPE-DECL, I'm not sure how to make the parser skip the text of the decl, or what it could possibly return when skipping it. I could appreciate advice on the matter. Thank you -- Sean Champ

2 4

[cxml-devel] documentation string on `sax:start-element'
by Sean Champ 09 Sep '06

09 Sep '06

Hello, I was trying to make some documentation about CXML, then in regards to the SAX API made avaialable with CXML. I noticed the following, in the documentation string for the generic function SAX:START-ELEMENT : The attributes parameter is a list (in arbitrary order) of instances of the `attribute' structure class. The for their namespace-uri and local-name properties, the same rules as for the element name apply. Additionally, namespace-declaring attributes (those whose name is "xmlns" or starts with "xmlns:") are only included if *namespace-prefixes* is non-nil. Having CXML loaded, but I was not able to find a variable named *NAMESPACE-PREFIXES*, in any package. I have noticed that there is the variable SAX:*NAMESPACE-PROCESSING*. My looking briefly at the CXML source text of a method to SAX:START-ELEMENT, it appeared that that would be the name of the variable to which the documentation string would now refer. I've made a diff for the matter. The name of the variable in that documentation string is revised, in the diff, and any end-of-line whitespace is removed from the file. XEmacs automaticaly pruned the whitespace, when I wrote the file -- using the 'nuke-trailing-whitespace' lib, here. Danke -- Sean Champ

2 1