Added TODO, desactivated memory debug, ran make tests, daniel.

TODO

@@ -2,23 +2,50 @@
            TODO for the XML parser and stuff:
 	   ==================================
 
-URGENT:
+TODO:
-=======
+=====
-- Support for UTF-8 and UTF-16 encoding
+
-  => added some convertion routines provided by Martin Durst but I didn't
+- extend validity checks to go through entities content instead of
-     try to glue them in. I plan to keep everything internally as UTF-8
+  just labelling them PCDATA
-     this is slightly more costly but more compact, and recent processors
+- add support for the trick from Henry conf/sun/valid/empty.xml
-     efficiency is cache related. The key for good performances is keeping
+- Correct standalone checking/emitting (hard)
-     the data set small, so will I.
+  2.9 Standalone Document Declaration
-  => the new progressive reading routines call the detection code which
+- URI checkings (no fragments) rfc2396.txt
-     need to be enabled, then thest the ISO->UTF-8 stuff, and add more
+- Better checking of external parsed entities TAG 1234
-     charset conv routines.
+- Find way of representing PERefs in the Dtd so that %entity; can
+  be saved back.
+- Go through erratas and do the cleanup.
+  http://www.w3.org/XML/xml-19980210-errata ... bummmer 
 
 TODO:
 =====
 
-- Tools to produce man pages from the SGML docs.
+- Get OASIS testsuite to a more friendly result, check all the results
+  once stable.
+  http://xmlsoft.org/conf/result.html
 
+- Optimization of tag strings allocation.
+
+- maintain coherency of namespace when doing cut'n paste operations
+  => the functions are coded, but need testing
+
+- function to rebuild the ID table ?
+
+- Parsing of a well balanced chunk
+
+- dynamically adapt the alloc entry point to use g_alloc()/g_free()
+  if the programmer wants it
+
+- Validity checking problems for ENTITY ENTITIES attributes
+
+- Validity checking problems for NOTATIONS attributes
+   
+- Check attribute normalization especially xmlGetProp()
+
+EXTENSIONS:
+===========
+- URI module: validation, base, etc ...
+- Tools to produce man pages from the SGML docs.
 - Finish XPath
   => attributes addressing troubles
   => defaulted attributes handling
@@ -40,37 +67,12 @@ TODO:
      parsing one in-there should not be too hard. Key point is to get
      XSL to transform all this to something decent ...
 
-- Add regression tests for all WFC errors
-  => did some in test/WFC , not added to the Makefile yet.
-
-- Optimization of tag strings allocation.
-
-- Language identification code, productions [33] to [38]
-
-- Conditional sections in DTDs [61] to [65]
-  => should this crap be really implemented ???
-
-
-- Allow parsed entities defined in the internal subset to override
-  the ones defined in the external subset (DtD customization).
-  => This mean that the entity content should be computed only at
-     use time, i.e. keep the orig string only at parse time and expand
-     only when referenced from the external subset :-(
-     Needed for complete use of most DTD from Eve Maler
-
-- maintain coherency of namespace when doing cut'n paste operations
-  => the functions are coded, but need testing
-
-- function to rebuild the ID table ?
-
 - extend the shell with:
    - edit
    - load/save
    - mv (yum, yum, but it's harder because directories are ordered in
      our case, mvup and mvdown would be required)
 
-- Parsing of a well balanced chunk
-
 - Add HTML validation using the XHTML DTD
   - problem: do we want to keep and maintain the code for handling
     DTD/System ID cache directly in libxml ?
@@ -83,16 +85,49 @@ TODO:
 
 - Add output to XHTML in case of HTML documents.
 
-- dynamically adapt the alloc entry point to use g_alloc()/g_free()
-  if the programmer wants it
-
-- I18N: http://wap.trondheim.com/vaer/index.phtml is not XML and accepted
-  by the XML parser, UTF-8 should be checked when there is no "encoding"
-  declared !
 
 Done:
 =====
 
+- Save Dtds using the children list instead of dumping the tables,
+  order is preserved as well as comments and PIs
+- Wrote a notice of changes requires to go from 1.x to 2.x
+- make sure that all SAX callbacks are disabled if a WF error is detected
+- checking/handling of newline normalization
+  http://localhost/www.xml.com/axml/target.html#sec-line-ends
+- correct checking of '&' '%' on entities content.
+- checking of PE/Nesting on entities declaration
+- checking/handling of xml:space
+   - checking done.
+   - handling done, not well tested
+- Language identification code, productions [33] to [38]
+  => done, the check has been added and report WFness errors
+- Conditional sections in DTDs [61] to [65]
+  => should this crap be really implemented ???
+  => Yep OASIS testsuite uses them
+- Allow parsed entities defined in the internal subset to override
+  the ones defined in the external subset (DtD customization).
+  => This mean that the entity content should be computed only at
+     use time, i.e. keep the orig string only at parse time and expand
+     only when referenced from the external subset :-(
+     Needed for complete use of most DTD from Eve Maler
+- Add regression tests for all WFC errors
+  => did some in test/WFC
+  => added OASIS testsuite routines
+     http://xmlsoft.org/conf/result.html
+
+- I18N: http://wap.trondheim.com/vaer/index.phtml is not XML and accepted
+  by the XML parser, UTF-8 should be checked when there is no "encoding"
+  declared !
+- Support for UTF-8 and UTF-16 encoding
+  => added some convertion routines provided by Martin Durst
+     patched them, got fixes from @@@
+     I plan to keep everything internally as UTF-8 (or ISO-Latin-X)
+     this is slightly more costly but more compact, and recent processors
+     efficiency is cache related. The key for good performances is keeping
+     the data set small, so will I.
+  => the new progressive reading routines call the detection code
+     is enabled, tested the ISO->UTF-8 stuff
 - External entities loading: 
    - allow override by client code
    - make sure it is alled for all external entities referenced

include/libxml/xmlmemory.h

@@ -8,7 +8,7 @@
 #ifndef _DEBUG_MEMORY_ALLOC_
 #define _DEBUG_MEMORY_ALLOC_
 
-/* #define NO_DEBUG_MEMORY */
+#define NO_DEBUG_MEMORY
 
 #ifdef NO_DEBUG_MEMORY
 #ifdef HAVE_MALLOC_H

result/valid/xhtml1.xhtml

@@ -58,7 +58,7 @@ table.exceptions { background-color: rgb(255,255,153); }
 </div>
 <div class="head"><p><a href="http://www.w3.org/"><img class="head" src="w3c_home.gif" alt="W3C"/></a></p>
 
-<h1 class="head"><a name="title" id="title">XHTML</a><sup>&quot;</sup> 1.0:
+<h1 class="head"><a name="title" id="title">XHTML</a><sup>&#x2122;</sup> 1.0:
 The Extensible HyperText Markup Language</h1>
 
 <h2>A Reformulation of HTML 4.0 in XML 1.0</h2>
@@ -70,7 +70,7 @@ http://www.w3.org/TR/1999/PR-xhtml1-19991210</a> <br/>
 (<a href="xhtml1.ps">Postscript version</a>,
 <a href="xhtml1.pdf">PDF version</a>,
 <a href="xhtml1.zip">ZIP archive</a>, or
-<a href="xhtml1.tgz">Gzip&apos;d TAR archive</a>)
+<a href="xhtml1.tgz">Gzip'd TAR archive</a>)
 </dd><dt>Latest version:</dt><dd><a href="http://www.w3.org/TR/xhtml1">
 http://www.w3.org/TR/xhtml1</a></dd><dt>Previous versions:</dt><dd><a href="http://www.w3.org/TR/1999/WD-xhtml1-19991124">
 http://www.w3.org/TR/1999/WD-xhtml1-19991124</a></dd><dd><a href="http://www.w3.org/TR/1999/PR-xhtml1-19990824">
@@ -116,7 +116,7 @@ ballots to w3c-html-review@w3.org. Please send any comments of a
 confidential nature in separate email to w3t-html@w3.org, which is
 visible to the Team only.</p>
 <p>No sooner than 14 days after the end of the review period, the
-Director will announce the document&apos;s disposition: it may become a W3C
+Director will announce the document's disposition: it may become a W3C
 Recommendation (possibly with minor changes), it may revert to Working
 Draft status, or it may be dropped as a W3C work item.</p>
 <p>Publication as a Proposed Recommendation does not imply endorsement
@@ -194,7 +194,7 @@ likely to interoperate within and among various XHTML environments.</li>
 <p>The XHTML family is the next step in the evolution of the Internet. By
 migrating to XHTML today, content developers can enter the XML world with all
 of its attendant benefits, while still remaining confident in their
-content&apos;s backward and future compatibility.</p>
+content's backward and future compatibility.</p>
 <h2>
 <a name="html4" id="html4">1.1 What is HTML 4.0?</a>
 </h2>
@@ -206,7 +206,7 @@ standard publishing language of the World Wide Web.</p>
 particularly those used in electronic document exchange, document
 management, and document publishing. HTML is an example of a
 language defined in SGML.</p>
-    <p>SGML has been around since the middle 1980&apos;s and has remained
+<p>SGML has been around since the middle 1980's and has remained
 quite stable. Much of this stability stems from the fact that the
 language is both feature-rich and flexible. This flexibility,
 however, comes at a price, and that price is a level of
@@ -221,24 +221,24 @@ In addition to simplifying the document structure, HTML added
 support for hypertext. Multimedia capabilities were added
 later.</p>
 <p>In a remarkably short space of time, HTML became wildly
-popular and rapidly outgrew its original purpose. Since HTML&apos;s
+popular and rapidly outgrew its original purpose. Since HTML's
 inception, there has been rapid invention of new elements for use
 within HTML (as a standard) and for adapting HTML to vertical,
 highly specialized, markets. This plethora of new elements has
 led to compatibility problems for documents across different
 platforms.</p>
 <p>As the heterogeneity of both software and platforms rapidly
-proliferate, it is clear that the suitability of &apos;classic&apos; HTML
+proliferate, it is clear that the suitability of 'classic' HTML
 4.0 for use on these platforms is somewhat limited.</p>
 <h2>
 <a name="xml" id="xml">1.2 What is XML?</a>
 </h2>
-    <p>XML<sup>&quot;</sup> is the shorthand for Extensible Markup
+<p>XML<sup>&#x2122;</sup> is the shorthand for Extensible Markup
 Language, and is an acronym of Extensible Markup Language <a href="#ref-xml">[XML]</a>.</p>
 <p>XML was conceived as a means of regaining the power and
 flexibility of SGML without most of its complexity. Although a
-restricted form of SGML, XML nonetheless preserves most of SGML&apos;s
+restricted form of SGML, XML nonetheless preserves most of SGML's
-power and richness, and yet still retains all of SGML&apos;s commonly
+power and richness, and yet still retains all of SGML's commonly
 used features.</p>
 <p>While retaining these beneficial features, XML removes many of
 the more complex features of SGML that make the authoring and
@@ -323,7 +323,7 @@ facility, is not a Strictly Conforming XHTML Document.</dd>
 <dl>
 <dt>Attribute</dt>
 <dd>An attribute is a parameter to an element declared in the
-DTD. An attribute&apos;s type and value range, including a possible
+DTD. An attribute's type and value range, including a possible
 default value, are defined in the DTD.</dd>
 <dt>DTD</dt>
 <dd>A DTD, or document type definition, is a collection of XML
@@ -340,7 +340,7 @@ elements</span> that are organized as defined in the associated
 Conformance</a> for more information.</dd>
 <dt>Element</dt>
 <dd>An element is a document structuring unit declared in the
-<span class="term">DTD</span>. The element&apos;s content model is
+<span class="term">DTD</span>. The element's content model is
 defined in the <span class="term">DTD</span>, and additional
 semantics may be defined in the prose description of the
 element.</dd>
@@ -410,7 +410,7 @@ specification. Such a document must meet all of the following
 criteria:</p>
 <ol>
 <li>
-<p>It must validate against one of the three DTDs found in <a href="#dtds">Appendix&#160;A</a>.</p>
+<p>It must validate against one of the three DTDs found in <a href="#dtds">Appendix&#xA0;A</a>.</p>
 </li>
 <li>
 <p>The root element of the document must be <code>
@@ -426,7 +426,7 @@ defined to be
 <p>There must be a DOCTYPE declaration in the document prior to
 the root element. The public identifier included in
 the DOCTYPE declaration must reference one of the three DTDs
-found in <a href="#dtds">Appendix&#160;A</a> using the respective
+found in <a href="#dtds">Appendix&#xA0;A</a> using the respective
 Formal Public Identifier. The system identifier may be changed to reflect
 local system conventions.</p>
 
@@ -503,13 +503,13 @@ could be incorporated into another XML namespace:</p>
 <pre>
 &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
 &lt;!-- initially, the default namespace is &quot;books&quot; --&gt;
-&lt;book xmlns=&apos;urn:loc.gov:books&apos;
+&lt;book xmlns='urn:loc.gov:books'
-    xmlns:isbn=&apos;urn:ISBN:0-395-36341-6&apos; xml:lang=&quot;en&quot; lang=&quot;en&quot;&gt;
+    xmlns:isbn='urn:ISBN:0-395-36341-6' xml:lang=&quot;en&quot; lang=&quot;en&quot;&gt;
   &lt;title&gt;Cheaper by the Dozen&lt;/title&gt;
   &lt;isbn:number&gt;1568491379&lt;/isbn:number&gt;
   &lt;notes&gt;
     &lt;!-- make HTML the default namespace for a hypertext commentary --&gt;
-    &lt;p xmlns=&apos;http://www.w3.org/1999/xhtml&apos;&gt;
+    &lt;p xmlns='http://www.w3.org/1999/xhtml'&gt;
         This is also available &lt;a href=&quot;http://www.w3.org/&quot;&gt;online&lt;/a&gt;.
     &lt;/p&gt;
   &lt;/notes&gt;
@@ -531,22 +531,22 @@ against their referenced DTDs according to <a href="#ref-xml">
 <li>When the user agent claims to support <a href="#facilities">
 facilities</a> defined within this specification or required by
 this specification through normative reference, it must do so in
-ways consistent with the facilities&apos; definition.</li>
+ways consistent with the facilities' definition.</li>
 <li>When a user agent processes an XHTML document as generic XML,
 it shall only recognize attributes of type
 <code>ID</code> (e.g. the <code>id</code> attribute on most XHTML elements)
 as fragment identifiers.</li>
 <li>If a user agent encounters an element it does not recognize,
-it must render the element&apos;s content.</li>
+it must render the element's content.</li>
 <li>If a user agent encounters an attribute it does not
 recognize, it must ignore the entire attribute specification
 (i.e., the attribute and its value).</li>
-      <li>If a user agent encounters an attribute value it doesn&apos;t
+<li>If a user agent encounters an attribute value it doesn't
 recognize, it must use the default attribute value.</li>
 <li>If it encounters an entity reference (other than one
 of the predefined entities) for which the User Agent has 
 processed no declaration (which could happen if the declaration
-is in the external subset which the User Agent hasn&apos;t read), the entity 
+is in the external subset which the User Agent hasn't read), the entity 
 reference should be rendered as the characters (starting
 with the ampersand and ending with the semi-colon) that
 make up the entity reference.</li>
@@ -558,7 +558,7 @@ The following characters are defined in [XML] as whitespace characters:
 <ul><li>Space (&amp;#x0020;)</li><li>Tab (&amp;#x0009;)</li><li>Carriage return (&amp;#x000D;)</li><li>Line feed (&amp;#x000A;)</li></ul>
 
 <p>
-The XML processor normalizes different system&apos;s line end codes into one
+The XML processor normalizes different system's line end codes into one
 single line-feed character, that is passed up to the application. The XHTML
 user agent in addition, must treat the following characters as whitespace:
 </p>
@@ -566,7 +566,7 @@ user agent in addition, must treat the following characters as whitespace:
 <ul><li>Form feed (&amp;#x000C;)</li><li>Zero-width space (&amp;#x200B;)</li></ul>
 
 <p>
-In elements where the &apos;xml:space&apos; attribute is set to &apos;preserve&apos;, the user
+In elements where the 'xml:space' attribute is set to 'preserve', the user
 agent must leave all whitespace characters intact (with the exception of
 leading and trailing whitespace characters, which should be removed).
 Otherwise, whitespace
@@ -582,10 +582,10 @@ space characters.
 </li><li>
 Leading and trailing whitespace inside a block element must be removed.
 </li><li>Line feed characters within a block element must be converted into a
-space (except when the &apos;xml:space&apos; attribute is set to &apos;preserve&apos;).
+space (except when the 'xml:space' attribute is set to 'preserve').
 </li><li>
 A sequence of white space characters must be reduced to a single space
-character (except when the &apos;xml:space&apos; attribute is set to &apos;preserve&apos;).
+character (except when the 'xml:space' attribute is set to 'preserve').
 </li><li>
 With regard to rendition,
 the User Agent should render the content in a
@@ -594,12 +594,12 @@ In languages whose primary script is Latinate, the ASCII space
 character is typically used to encode both grammatical word boundaries and
 typographic whitespace; in languages whose script is related to Nagari
 (e.g., Sanskrit, Thai, etc.), grammatical boundaries may be encoded using
-the ZW &apos;space&apos; character, but will not typically be represented by
+the ZW 'space' character, but will not typically be represented by
 typographic whitespace in rendered output; languages using Arabiform scripts
 may encode typographic whitespace using a space character, but may also use
-the ZW space character to delimit &apos;internal&apos; grammatical boundaries (what
+the ZW space character to delimit 'internal' grammatical boundaries (what
 look like words in Arabic to an English eye frequently encode several words,
-e.g. &apos;kitAbuhum&apos; = &apos;kitAbu-hum&apos; = &apos;book them&apos; == their book); and languages
+e.g. 'kitAbuhum' = 'kitAbu-hum' = 'book them' == their book); and languages
 in the Chinese script tradition typically neither encode such delimiters nor
 use typographic whitespace in this way. 
 </li></ul>
@@ -761,15 +761,15 @@ documents.</p>
 elements from being contained within an element. Such
 prohibitions (called &quot;exclusions&quot;) are not possible in XML.</p>
 <p>For example, the HTML 4.0 Strict DTD forbids the nesting of an
-&apos;<code>a</code>&apos; element within another &apos;<code>a</code>&apos; element
+'<code>a</code>' element within another '<code>a</code>' element
 to any descendant depth. It is not possible to spell out such
 prohibitions in XML. Even though these prohibitions cannot be
 defined in the DTD, certain elements should not be nested. A
 summary of such elements and the elements that should not be
 nested in them is found in the normative <a href="#prohibitions">
-Appendix&#160;B</a>.</p>
+Appendix&#xA0;B</a>.</p>
 <h2>
-      <a name="h-4.10" id="h-4.10">4.10 The elements with &apos;id&apos; and &apos;name&apos;
+<a name="h-4.10" id="h-4.10">4.10 The elements with 'id' and 'name'
 attributes</a>
 </h2>
 <p>HTML 4.0 defined the <code>name</code> attribute for the elements
@@ -801,7 +801,7 @@ subsequent version of XHTML.</p>
 <p>Although there is no requirement for XHTML 1.0 documents to be
 compatible with existing user agents, in practice this is easy to
 accomplish. Guidelines for creating compatible documents can be
-found in <a href="#guidelines">Appendix&#160;C</a>.</p>
+found in <a href="#guidelines">Appendix&#xA0;C</a>.</p>
 <h2>
 <a name="media" id="media">5.1 Internet Media Type</a>
 </h2>
@@ -872,7 +872,7 @@ different versions of documents for different clients.</p>
 <p>For special groups such as chemists, medical doctors, or
 mathematicians this allows a special profile to be built using
 standard HTML elements plus a group of elements geared to the
-specialist&apos;s needs.</p>
+specialist's needs.</p>
 <!--OddPage-->
 <h1><a name="appendices" id="appendices"/>
 <a name="dtds" id="dtds">Appendix A. DTDs</a></h1>
@@ -981,9 +981,9 @@ or UTF-16.</p>
 <h2>C.2 Empty Elements</h2>
 <p>Include a space before the trailing <code>/</code> and <code>
 &gt;</code> of empty elements, e.g. <code class="greenmono">
-&lt;br&#160;/&gt;</code>, <code class="greenmono">
+&lt;br&#xA0;/&gt;</code>, <code class="greenmono">
-&lt;hr&#160;/&gt;</code> and <code class="greenmono">&lt;img
+&lt;hr&#xA0;/&gt;</code> and <code class="greenmono">&lt;img
-src=&quot;karen.jpg&quot; alt=&quot;Karen&quot;&#160;/&gt;</code>. Also, use the
+src=&quot;karen.jpg&quot; alt=&quot;Karen&quot;&#xA0;/&gt;</code>. Also, use the
 minimized tag syntax for empty elements, e.g. <code class="greenmono">&lt;br /&gt;</code>, as the alternative syntax <code class="greenmono">&lt;br&gt;&lt;/br&gt;</code> allowed by XML
 gives uncertain results in many existing user agents.</p>
 <h2>C.3 Element Minimization and Empty Element Content</h2>
@@ -991,7 +991,7 @@ gives uncertain results in many existing user agents.</p>
 not <code>EMPTY</code> (for example, an empty title or paragraph)
 do not use the minimized form (e.g. use <code class="greenmono">
 &lt;p&gt; &lt;/p&gt;</code> and not <code class="greenmono">
-&lt;p&#160;/&gt;</code>).</p>
+&lt;p&#xA0;/&gt;</code>).</p>
 <h2>C.4 Embedded Style Sheets and Scripts</h2>
 <p>Use external style sheets if your style sheet uses <code>
 &lt;</code> or <code>&amp;</code> or <code>]]&gt;</code> or <code>--</code>. Use
@@ -1006,7 +1006,7 @@ implementations.</p>
 attribute values. These are handled inconsistently by user
 agents.</p>
 <h2>C.6 Isindex</h2>
-    <p>Don&apos;t include more than one <code>isindex</code> element in
+<p>Don't include more than one <code>isindex</code> element in
 the document <code>head</code>. The <code>isindex</code> element
 is deprecated in favor of the <code>input</code> element.</p>
 <h2>C.7 The <code>lang</code> and <code>xml:lang</code> Attributes</h2>
@@ -1018,7 +1018,7 @@ of the <code>xml:lang</code> attribute takes precedence.</p>
 <code>&quot;#foo&quot;</code> do not refer to elements with an attribute
 <code>name=&quot;foo&quot;</code>; rather, they refer to elements with an
 attribute defined to be of type <code>ID</code>, e.g., the <code>
-id</code> attribute in HTML 4.0. Many existing HTML clients don&apos;t
+id</code> attribute in HTML 4.0. Many existing HTML clients don't
 support the use of <code>ID</code>-type attributes in this way,
 so identical values may be supplied for both of these attributes to ensure
 maximum forward and backward compatibility (e.g., <code class="greenmono">&lt;a id=&quot;foo&quot; name=&quot;foo&quot;&gt;...&lt;/a&gt;</code>).</p>
@@ -1045,13 +1045,13 @@ encoding attribute specification on the xml declaration (e.g.
 <code class="greenmono">&lt;?xml version=&quot;1.0&quot;
 encoding=&quot;EUC-JP&quot;?&gt;</code>) and a meta http-equiv statement
 (e.g. <code class="greenmono">&lt;meta http-equiv=&quot;Content-type&quot;
-content=&apos;text/html; charset=&quot;EUC-JP&quot;&apos;&#160;/&gt;</code>). The
+content='text/html; charset=&quot;EUC-JP&quot;'&#xA0;/&gt;</code>). The
 value of the encoding attribute of the xml processing instruction
 takes precedence.</p>
 <h2>C.10 Boolean Attributes</h2>
 <p>Some HTML user agents are unable to interpret boolean
 attributes when these appear in their full (non-minimized) form,
-as required by XML 1.0. Note this problem doesn&apos;t effect user
+as required by XML 1.0. Note this problem doesn't effect user
 agents compliant with HTML 4.0. The following attributes are
 involved: <code>compact</code>, <code>nowrap</code>, <code>
 ismap</code>, <code>declare</code>, <code>noshade</code>, <code>
@@ -1153,7 +1153,7 @@ Masayasu Ishikawa, W3C<br/>
 Warner ten Kate, Philips Electronics<br/>
 Peter King, Phone.com<br/>
 Paula Klante, JetForm<br/>
-Shin&apos;ichi Matsui, W3C/Panasonic<br/>
+Shin'ichi Matsui, W3C/Panasonic<br/>
 Shane McCarron, Applied Testing and Technology (The Open Group through August
 1999)<br/>
 Ann Navarro, HTML Writers Guild<br/>
@@ -1196,7 +1196,7 @@ http://www.w3.org/TR/REC-DOM-Level-1</a></dd>
 <b>[HTML]</b>
 </a>
 </dt>
-      <dd><a href="http://www.w3.org/TR/1999/PR-html40-19990824">&quot;HTML 4.01 Specification&quot;</a>, D. Raggett, A. Le&#160;Hors, I.
+<dd><a href="http://www.w3.org/TR/1999/PR-html40-19990824">&quot;HTML 4.01 Specification&quot;</a>, D. Raggett, A. Le&#xA0;Hors, I.
 Jacobs, 24 August 1999.<br/>
 Available at: <a href="http://www.w3.org/TR/1999/PR-html40-19990824">
 http://www.w3.org/TR/1999/PR-html40-19990824</a></dd>

xmlmemory.h

@@ -8,7 +8,7 @@
 #ifndef _DEBUG_MEMORY_ALLOC_
 #define _DEBUG_MEMORY_ALLOC_
 
-/* #define NO_DEBUG_MEMORY */
+#define NO_DEBUG_MEMORY
 
 #ifdef NO_DEBUG_MEMORY
 #ifdef HAVE_MALLOC_H