From 0b28e88eb9285def35d2f1201a932014b717c3d3 Mon Sep 17 00:00:00 2001 From: Daniel Veillard Date: Wed, 24 Jul 2002 23:47:05 +0000 Subject: applied syntax patch from Rick Jones and rebuilt the web site. Daniel * doc/xml.html doc/*.html: applied syntax patch from Rick Jones and rebuilt the web site. Daniel --- doc/example.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/example.html') diff --git a/doc/example.html b/doc/example.html index 8e9b264e..c8eb55ad 100644 --- a/doc/example.html +++ b/doc/example.html @@ -203,14 +203,14 @@ DEBUG("parsePerson\n");
  • Usually a recursive parsing style is the more convenient one: XML data is by nature subject to repetitive constructs and usually exhibits highly structured patterns.
    • -
  • The two arguments of type xmlDocPtr and xmlNsPtr, +
  • The two arguments of type xmlDocPtr and xmlNsPtr, i.e. the pointer to the global XML document and the namespace reserved to the application. Document wide information are needed for example to decode entities and it's a good coding practice to define a namespace for your application set of data and test that the element and attributes you're analyzing actually pertains to your application space. This is done by a simple equality test (cur->ns == ns).
    • -
  • To retrieve text and attributes value, you can use the function +
  • To retrieve text and attributes value, you can use the function xmlNodeListGetString to gather all the text and entity reference nodes generated by the DOM output and produce an single text string.
    • -- cgit v1.2.1