You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xerces.apache.org by bo...@apache.org on 2008/02/25 16:35:11 UTC

svn commit: r630879 [3/4] - in /xerces/c/trunk/doc: ./ html/ html/apiDocs-3/ html/apiDocs/ style/dtd/ style/graphics/ style/resources/ style/stylesheets/

Modified: xerces/c/trunk/doc/migration_archive.xml
URL: http://svn.apache.org/viewvc/xerces/c/trunk/doc/migration_archive.xml?rev=630879&r1=630878&r2=630879&view=diff
==============================================================================
--- xerces/c/trunk/doc/migration_archive.xml (original)
+++ xerces/c/trunk/doc/migration_archive.xml Mon Feb 25 07:35:02 2008
@@ -21,8 +21,10 @@
 <s1 title="Migration Archive">
     <s2 title="Migrating to earlier Releases">
       <ul>
+        <li><link anchor="Migrateto270">Migrating from &XercesCName; 2.6.0 to 2.7.0</link></li>
+        <li><link anchor="Migrateto260">Migrating from &XercesCName; 2.5.0 to 2.6.0</link></li>
         <li><link anchor="Migrateto250">Migrating from &XercesCName; 2.4.0 to 2.5.0</link></li>
-        <li><link anchor="Migrateto240">Migrating from &XercesCName; 2.3.0 to 2.4.0</link></li>      
+        <li><link anchor="Migrateto240">Migrating from &XercesCName; 2.3.0 to 2.4.0</link></li>
         <li><link anchor="Migrateto230">Migrating from &XercesCName; 2.2.0 to 2.3.0</link></li>
         <li><link anchor="Migrateto220">Migrating from &XercesCName; 2.1.0 to 2.2.0</link></li>
         <li><link anchor="Migrateto210">Migrating from &XercesCName; 2.0.0 to 2.1.0</link></li>
@@ -34,6 +36,168 @@
       </ul>
     </s2>
 
+
+    <anchor name="Migrateto270"/>
+    <s2 title="Migrating from &XercesCName; 2.6.0 to &XercesCName; 2.7.0">
+      <p>The following section is a discussion of the technical differences between
+      &XercesCName; 2.6.0 code base and the &XercesCName; 2.7.0.</p>
+
+      <p>Topics discussed are:</p>
+      <ul>
+        <li><link anchor="NewFeatures270">New features in &XercesCName; 2.7.0</link></li>
+        <li><link anchor="API270">Public API Changes</link></li>
+        <ul>
+            <li><link anchor="NewAPI270">New Public API</link></li>
+            <li><link anchor="ModifiedAPI270">Modified Public API</link></li>
+            <li><link anchor="DeprecatedAPI270">Deprecated/Removed Public API</link></li>
+        </ul>
+      </ul>
+
+    <anchor name="NewFeatures270"/>
+    <s3 title="New features in &XercesCName; 2.7.0">
+      <ul>
+        <li>Feature to not generate XML Schema annotations.  That is, not to add them to the grammar.  If you don't need annotations you may want to turn on this feature to avoid memory bloat for XML Schemas that use annotations heavily.</li>
+        <li>Option to skip regenerating the XML Schema annotations when deserializing a grammar.  If you don't need annotations you may want to turn on this option to avoid memory bloat for XML Schemas that use annotations heavily.</li>
+        <li>Feature to not perform default entity resolution.  When the entityResolver returns NULL, the parser doesn't try to resolve the entity externally.</li>
+        <li>Feature to do schema-only validation even if there is a DTD.</li>
+      </ul>
+    </s3>
+
+    <anchor name="API270"/>
+    <s3 title="Public API Changes">
+
+        <p>The following lists the public API changes between the &XercesCName;
+           2.6.0; and the &XercesCName; 2.7.0 releases
+           of the parser. </p>
+
+        <anchor name="NewAPI270"/>
+        <s4 title="New Public API">
+            <ul>
+              <li>XMLString: subString, compareIStringASCII, lowercaseASCII, uppercaseASCII</li>
+              <li>RefHash2KeysTableOf: rehashing support</li>
+              <li>XMemory: placement new and delete</li>
+              <li>SAX2XMLFilter</li>
+            </ul>
+        </s4>
+
+        <anchor name="ModifiedAPI270"/>
+        <s4 title="Modified Public API">
+        </s4>
+
+        <anchor name="DeprecatedAPI270"/>
+        <s4 title="Deprecated/Removed Public API">
+        </s4>
+
+    </s3>
+    </s2>
+
+
+	<anchor name="Migrateto260"/>
+	<s2 title="Migrating from &XercesCName; 2.5.0 to &XercesCName; 2.6.0">
+	<p>The following section is a discussion of the technical differences between
+      &XercesCName; 2.5.0 code base and the &XercesCName; 2.6.0.</p>
+
+      <p>Topics discussed are:</p>
+      <ul>
+        <li><link anchor="NewFeatures260">New features in &XercesCName; 2.6.0</link></li>
+        <li><link anchor="API260">Public API Changes</link></li>
+        <ul>
+            <li><link anchor="NewAPI260">New Public API</link></li>
+            <li><link anchor="ModifiedAPI260">Modified Public API</link></li>
+            <li><link anchor="DeprecatedAPI260">Deprecated/Removed Public API</link></li>
+            <li>Please note the following source code incompatibility: Rename VALUE_CONSTRAINT enumeration values in XSConstants.hpp due to conflict with system header.  New
+              values are VALUE_CONSTRAINT_NONE, VALUE_CONSTRAINT_DEFAULT and VALUE_CONSTRAINT_FIXED.  Old
+              values are VC_NONE, VC_DEFAULT and VC_FIXED.</li>
+            <li>Also note that if you have implemented your own XMLGrammarPool implementation, that
+                the original getXSModel has been marked deprecated and a new method, of the same
+                name, that takes a bool parameter has been added.  This new getXSModel needs
+                to always return an XSModel.</li>
+        </ul>
+      </ul>
+
+    <anchor name="NewFeatures260"/>
+    <s3 title="New features in &XercesCName; 2.6.0">
+      <ul>
+		<li>Reduce footprint of DLL by building the deprecated DOM as a separate library</li>
+        <li>Improve packaging scripts</li>
+        <li>Enable ID's to work on all kinds of schema components</li>
+        <li>Add messages to DOMExceptions along with the error code</li>
+        <li>Improve annotation error-reporting capabilities</li>
+        <li>Make grammar caching work with DTD internal subsets</li>
+        <li>Bring parser up to the XML 1.0 3rd Edition</li>
+        <li>Update to the XML 1.1 recommendation</li>
+        <li>Add new method to DOMDocument so that DOM level-2 style DOMDocumentTypes (which have a
+        DOMDocument to own them) can be created</li>
+        <li>Feature for disabling identity constraints</li>
+        <li>Update schema errata</li>
+        <li>Provide means to get actual values out of PSVI/schema component model</li>
+        <li>Synthesize annotation components for non-schema attributes</li>
+        <li>Expose partial PSVIElement information at the start element call</li>
+        <li>Externalize validation, actual/canonical value production for arbitrary strings</li>
+        <li>Laxly validate schema annotations</li>
+        <li>Upgrade to ICU 3.0</li>
+        <li>Handle elements with a large number of attributes more efficiently</li>
+      </ul>
+    </s3>
+
+    <anchor name="API260"/>
+    <s3 title="Public API Changes">
+
+        <p>The following lists the public API changes between the &XercesCName;
+           2.5.0; and the &XercesCName; 2.6.0 releases
+           of the parser. </p>
+
+        <anchor name="NewAPI260"/>
+        <s4 title="New Public API">
+            <ul>
+              <li>XSValue</li>
+              <li>IdentityConstraintHandler</li>
+              <li>XMLBufferFullHandler</li>
+              <li>XMLString: removeChar, isValidNOTATION</li>
+              <li>XMLUri: normalizeUri</li>
+              <li>PSVIHandler: handlePartialElementPSVI</li>
+              <li>RefHash family of classes: getHashModulus</li>
+              <li>XSAnnotation: setline/col and systemid</li>
+              <li>XMLReader: handeEOL</li>
+              <li>XMLChar: isValidNmToken</li>
+              <li>XMLBigDecimal: parseDecimal, getIntVal</li>
+              <li>HexBin: getCanonicalRepresentation, decode</li>
+              <li>Base64: getCanonicalRepresentation, decode</li>
+              <li>XMLBigInteger: compareValues</li>
+              <li>XMLAbstractDoubleFloat: isDataConverted, getValue, isDataOverFlowed</li>
+              <li>PSVIItem: getActualValue</li>
+              <li>XSSimpleTypeDefinition: getDatatypeValidator</li>
+              <li>RefHash2KeysTableOf: transferElement</li>
+              <li>XMLGrammarPool: getXSModel</li>
+            </ul>
+        </s4>
+
+        <anchor name="ModifiedAPI260"/>
+        <s4 title="Modified Public API">
+            <ul>
+              <li>XSerializeEngine constructor</li>
+              <li>MACUnicodeConverters</li>
+            </ul>
+        </s4>
+
+        <anchor name="DeprecatedAPI260"/>
+        <s4 title="Deprecated/Removed Public API">
+            <ul>
+              <li>XSerializeEngine constructor</li>
+              <li>DTDAttDef: getDOMTypeInfoName,  getDOMTypeInfoUri</li>
+			  <li>DTDElementDecl: getDOMTypeInfoName, getDOMTypeInfoUri</li>
+     	      <li>SchemaAttDef: setAnyDatatypeValidator</li>
+ 			  <li>UnionDatatypeValidator: getMemberTypeName, getMemberTypeUri, getMemberTypeAnonymous, getMemberTypeValidator</li>
+ 			  <li>XMLAttr: getValidatingTypeURI, getValidatingTypeName, setDatatypeValidator, setSchemaValidated</li>
+ 			  <li>ComplexTypeInfo: setContentModel</li>
+ 			  <li>XMLGrammarPool: getXSModel</li>
+ 			  <li>SAXParser, mark this class deprecated</li>
+            </ul>
+        </s4>
+
+    </s3>
+    </s2>
+
 	<anchor name="Migrateto250"/>
 	<s2 title="Migrating from &XercesCName; 2.4.0 to &XercesCName; 2.5.0">
       <p>The following section is a discussion of the technical differences between
@@ -60,7 +224,7 @@
               <li>Re-pluggable Panic Handler</li>
               <li>Enhenced mutex creation to impove thread safety</li>
               <li>Intrinsic transcoding support for 390.</li>
-              <li>Canonical Representation Support </li>              
+              <li>Canonical Representation Support </li>
               <li>New sample SCMPrint</li>
               <li>New sample PSVIWriter</li>
               <li>New test XSerializerTest</li>
@@ -77,7 +241,7 @@
         <anchor name="NewAPI250"/>
         <s4 title="New Public API">
             <ul>
-              <li></li>            
+              <li></li>
             </ul>
         </s4>
 
@@ -91,13 +255,13 @@
         <anchor name="DeprecatedAPI250"/>
         <s4 title="Deprecated/Removed Public API">
             <ul>
-              <li></li>              
+              <li></li>
             </ul>
         </s4>
 
     </s3>
     </s2>
-    
+
     <anchor name="Migrateto240"/>
     <s2 title="Migrating from &XercesCName; 2.3.0 to &XercesCName; 2.4.0">
       <p>The following section is a discussion of the technical differences between
@@ -118,7 +282,7 @@
     <s3 title="New features in &XercesCName; 2.4.0">
       <ul>
         <li>PSVI</li>
-        <li>Performance enhancement</li>        
+        <li>Performance enhancement</li>
         <li>Stateless Grammar </li>
         <li>Grammar Serialization/Deserialiation</li>
       </ul>
@@ -135,7 +299,7 @@
         <s4 title="New Public API">
             <ul>
               <li>PSVI related</li>
-              <li>Grammar serialization/deserialization related</li>              
+              <li>Grammar serialization/deserialization related</li>
             </ul>
         </s4>
 
@@ -152,7 +316,7 @@
               <li>XMLAttDef: getProvided, getDOMTypeInfoUri, getDOMTypeInfoName, setProvided</li>
               <li>XMLAttDefList: hasMoreElements, nextElement, Reset</li>
               <li>DTDAttDefList: hasMoreElements, nextElement, Reset</li>
-              <li>SchemaAttDefList: hasMoreElements, nextElement, Reset</li>       
+              <li>SchemaAttDefList: hasMoreElements, nextElement, Reset</li>
               <li>XMLElementDecl: LookupOpts</li>
               <li>XMLNumber family: toString</li>
               <li>ENTITYDatatypeValidator: setEntityDeclPool</li>
@@ -162,13 +326,13 @@
               <li>SchemaGrammar: getIDRefList</li>
               <li>SchemaElementDecl: all non thread safe methods </li>
               <li>SchemaAttDef: getters </li>
-              <li>DTDGrammar: getRootElemId</li>                           
+              <li>DTDGrammar: getRootElemId</li>
             </ul>
         </s4>
 
     </s3>
     </s2>
-    
+
     <anchor name="Migrateto230"/>
     <s2 title="Migrating from &XercesCName; 2.2.0 to &XercesCName; 2.3.0">
       <p>The following section is a discussion of the technical differences between
@@ -191,15 +355,15 @@
         <li>Experimental Implementation of Namespaces in XML 1.1 </li>
         <li>Experimental Implementation of XML 1.1: in DOMWriter</li>
         <li>More Schema 1.0 Errata Implementation</li>
-        <li>More DOM L3 Core Support</li>        
+        <li>More DOM L3 Core Support</li>
         <ul>
             <li>DOMConfiguration</li>
             <li>Document Normalization</li>
         </ul>
-        <li>Plugable Memory Manager</li>      
-        <li>Plugable Security Manager</li>      
+        <li>Plugable Memory Manager</li>
+        <li>Plugable Security Manager</li>
         <li>Plugable Panic Handler</li>
-        <li>Logical Path Resolution</li>        
+        <li>Logical Path Resolution</li>
       </ul>
     </s3>
 
@@ -235,7 +399,7 @@
 
     </s3>
     </s2>
-        
+
     <anchor name="Migrateto220"/>
     <s2 title="Migrating from &XercesCName; 2.1.0 to &XercesCName; 2.2.0">
       <p>The following section is a discussion of the technical differences between
@@ -268,7 +432,7 @@
         <li>DOM Message: make use of the non-standard extension DOMImplementation::loadDOMExceptionMsg
         to load the default error text message for the correspond Exception Code.</li>
         <li>New feature XMLPlatformUtils::Initialize(const char* const locale) to set
-        the locale for message loader.   See <jump href="program-others.html#SpecifylocaleforMessageLoader">
+        the locale for message loader.   See <jump href="program-others-&XercesC3Series;.html#SpecifylocaleforMessageLoader">
         Specify locale for Message Loader</jump> for details</li>
         <li>Support Build with ICU Message Loader, or Message Catalog Message Loader</li>
         <li>RPM for Linux</li>
@@ -277,23 +441,23 @@
         <li>Support for Linux/390</li>
         <li>Performance: Break Scanner for different functionalities and many other performance improvement</li>
         <li>New feature, "http://apache.org/xml/features/dom/byte-order-mark", allows user to enable
-            DOMWriter to write Byte-Order-Mark in the output XML stream, 
-            See <jump href="program-dom.html#Byte-Order-Mark">
-            Xercesc Feature: Byte Order Mark</jump> for details</li>        
+            DOMWriter to write Byte-Order-Mark in the output XML stream,
+            See <jump href="program-dom-&XercesC3Series;.html#Byte-Order-Mark">
+            Xercesc Feature: Byte Order Mark</jump> for details</li>
       </ul>
     </s3>
 
     <anchor name="CPPNamespace220"/>
     <s3 title="Using C++ Namespace">
         <p>&XercesCName; 2.2.0 now supports C++ Namespace.  All &XercesCName;
-           classes, data and variables are defined in the &XercesCNamespace; namespace
+           classes, data and variables are defined in the &XercesC3Namespace; namespace
            if C++ Namespace support is ENABLED.</p>
 
         <p>All the binary distributions of &XercesCName; 2.2.0 are now built with
            C++ Namespace enabled.   Therefore users' applications that links with the distributed
            binary packages must namespace qualify all the &XercesCName; classes, data and variables.</p>
 
-        <p>See the Programming Guide <jump href="program-others.html#CPPNamespace">Using C++ Namespace</jump>
+        <p>See the Programming Guide <jump href="program-others-&XercesC3Series;.html#CPPNamespace">Using C++ Namespace</jump>
            for details.</p>
 
     </s3>
@@ -380,7 +544,7 @@
 
     </s3>
     </s2>
-        
+
     <anchor name="Migrateto210"/>
     <s2 title="Migrating from &XercesCName; 2.0.0 to &XercesCName; 2.1.0">
       <p>The following section is a discussion of the technical differences between
@@ -482,21 +646,21 @@
          <ul>
             <li>AIX</li>
             <ul>
-              <li>&XercesCUnixLib;&XercesCUnixSoName;.so</li>
-              <li>symbolic link: &XercesCUnixLib;.so                      ----&gt; &XercesCUnixLib;&XercesCUnixVersion;.so</li>
-              <li>symbolic link: &XercesCUnixLib;&XercesCUnixVersion;.so  ----&gt; &XercesCUnixLib;&XercesCUnixSoName;.so</li>
+              <li>&XercesC3UnixLib;&XercesC3UnixSoName;.so</li>
+              <li>symbolic link: &XercesC3UnixLib;.so                      ----&gt; &XercesC3UnixLib;&XercesC3UnixVersion;.so</li>
+              <li>symbolic link: &XercesC3UnixLib;&XercesC3UnixVersion;.so  ----&gt; &XercesC3UnixLib;&XercesC3UnixSoName;.so</li>
             </ul>
             <li>Solaris / Linux</li>
             <ul>
-              <li>&XercesCUnixLib;.so.&XercesCUnixSoName;</li>
-              <li>symbolic link: &XercesCUnixLib;.so                      ----&gt; &XercesCUnixLib;.so.&XercesCUnixVersion;</li>
-              <li>symbolic link: &XercesCUnixLib;.so.&XercesCUnixVersion; ----&gt; &XercesCUnixLib;.so.&XercesCUnixSoName;</li>
+              <li>&XercesC3UnixLib;.so.&XercesC3UnixSoName;</li>
+              <li>symbolic link: &XercesC3UnixLib;.so                      ----&gt; &XercesC3UnixLib;.so.&XercesC3UnixVersion;</li>
+              <li>symbolic link: &XercesC3UnixLib;.so.&XercesC3UnixVersion; ----&gt; &XercesC3UnixLib;.so.&XercesC3UnixSoName;</li>
             </ul>
             <li>HP-UX</li>
             <ul>
-              <li>&XercesCUnixLib;.sl.&XercesCUnixSoName;</li>
-              <li>symbolic link: &XercesCUnixLib;.sl                      ----&gt; &XercesCUnixLib;.sl.&XercesCUnixVersion;</li>
-              <li>symbolic link: &XercesCUnixLib;.sl.&XercesCUnixVersion; ----&gt; &XercesCUnixLib;.sl.&XercesCUnixSoName;</li>
+              <li>&XercesC3UnixLib;.sl.&XercesC3UnixSoName;</li>
+              <li>symbolic link: &XercesC3UnixLib;.sl                      ----&gt; &XercesC3UnixLib;.sl.&XercesC3UnixVersion;</li>
+              <li>symbolic link: &XercesC3UnixLib;.sl.&XercesC3UnixVersion; ----&gt; &XercesC3UnixLib;.sl.&XercesC3UnixSoName;</li>
             </ul>
          </ul>
     </s3>
@@ -547,7 +711,7 @@
                      file is renamed as well</li>
                  <li>the rest is the same, see
                      <jump href="ApacheDOMC++Binding.html">Apache Recommended DOM C++ binding</jump>
-                     and <jump href="program-dom.html">DOM Programming Guide</jump> for more programming
+                     and <jump href="program-dom-&XercesC3Series;.html">DOM Programming Guide</jump> for more programming
                      information</li>
               </ul>
               <p>Users of IDOM are required to change all their #include lines and do a global rename of
@@ -642,7 +806,7 @@
                   by targetNamespace (for Schema) or system id (for DTD).</li>
               <li>Plus "Grammar Caching" has much more functionalities other than above
                   (like "Pre-parsing Grammar").  Please refer to
-                  <jump href="program-others.html#GrammarCache">Preparsing Grammar and Grammar Caching
+                  <jump href="program-others-&XercesC3Series;.html#GrammarCache">Preparsing Grammar and Grammar Caching
                   </jump> for more programming details.</li>
            </ol>
     </s3>
@@ -658,7 +822,7 @@
         <s4 title="New Public API">
             <ul>
               <li>To support DOM Level 3, the following are added (see
-                  <jump href="api.html">the API documentation page</jump> for details).</li>
+                  <jump href="api-&XercesC3Series;.html">the API documentation page</jump> for details).</li>
                 <ul>
                   <li>DOMNode functions set/getUserData, isSameNode isEqualNode.</li>
                   <li>DOMDocument functions renameNode, get/setActualEncoding, get/setEncoding, get/setVersion, get/setStandalone, get/setDocumentURI.</li>
@@ -745,7 +909,7 @@
               <li>The old Java-like DOM is now deprecated as described in
                   <link anchor="DirChange200">DOM Reorganization</link></li>
               <li>SAX2XMLReader::setValidationConstraint.   For consistency, SAX2XMLReader users should
-                  set the feature http://apache.org/xml/features/validation-error-as-fatal" instead.</li>
+                  set the feature "http://apache.org/xml/features/validation-error-as-fatal" instead.</li>
               <li>SAX2XMLReader::setExitOnFirstFatalError.  For consistency, SAX2XMLReader users should
                   set the feature "http://apache.org/xml/features/continue-after-fatal-error" instead.</li>
               <li>With the new Grammar Caching introduced, the following features will not be
@@ -813,7 +977,7 @@
         <s4 title="New Public API">
             <ul>
               <li>Added SAX2-ext's DeclHandler class.
-                  See <jump href="api.html">the API documentation page</jump> for details.</li>
+                  See <jump href="api-&XercesC3Series;.html">the API documentation page</jump> for details.</li>
               <li>To support SAX2-ext's DeclHandler, the following new methods are added
                   in classes DefaultHandler and SAX2XMLReader:</li>
               <ul>
@@ -886,7 +1050,7 @@
     <s3 title="New features in &XercesCName; 1.6.0">
       <ul>
         <li>Full Schema support is available in this release.
-            See <jump href="schema.html">the Schema page</jump> for details.</li>
+            See <jump href="schema-&XercesC3Series;.html">the Schema page</jump> for details.</li>
         <li>New sample SEnumVal to show how to enumerate the markup decls in a Schema Grammar is added.</li>
       </ul>
     </s3>
@@ -974,16 +1138,13 @@
               <li>New command line option "-s" for samples.</li>
             </ul>
             <p>
-               See <jump href="schema.html">the Schema page</jump> for details.
+               See <jump href="schema-&XercesC3Series;.html">the Schema page</jump> for details.
             </p>
         </s4>
 
         <s4 title="Experimental IDOM">
-           <p>The experimental IDOM API is a new design of the C++ DOM API. If you would like
-              to migrate from DOM to the experimental IDOM, please refer to
-              <jump href="program-idom.html">
-              IDOM programming guide.</jump> Please note that this experimental IDOM API is only
-              a prototype and is subject to change.
+           <p>The experimental IDOM API is a new design of the C++ DOM API. Please note that
+              this experimental IDOM API is only a prototype and is subject to change.
            </p>
         </s4>
 

Modified: xerces/c/trunk/doc/pparse.xml
URL: http://svn.apache.org/viewvc/xerces/c/trunk/doc/pparse.xml?rev=630879&r1=630878&r2=630879&view=diff
==============================================================================
--- xerces/c/trunk/doc/pparse.xml (original)
+++ xerces/c/trunk/doc/pparse.xml Mon Feb 25 07:35:02 2008
@@ -60,7 +60,7 @@
              <em>-v=never</em> will not use any validation<br/>
              <em>-v=auto</em> will validate if a DOCTYPE declaration or a schema declaration is present in the XML document</p>
           <p>Here is a sample output from PParse</p>
-<source>cd &XercesCInstallDir;-linux/samples/data
+<source>cd &XercesC3InstallDir;-linux/samples/data
 PParse -v=always personal.xml
 personal.xml: 60 ms (37 elems, 12 attrs, 134 spaces, 134 chars)</source>
           <p>Running PParse with the validating parser gives a different result because

Modified: xerces/c/trunk/doc/program-dom.xml
URL: http://svn.apache.org/viewvc/xerces/c/trunk/doc/program-dom.xml?rev=630879&r1=630878&r2=630879&view=diff
==============================================================================
--- xerces/c/trunk/doc/program-dom.xml (original)
+++ xerces/c/trunk/doc/program-dom.xml Mon Feb 25 07:35:02 2008
@@ -35,9 +35,9 @@
 
     <anchor name="DOM3"/>
     <s2 title="DOM Level 3 Support in &XercesCName;">
-      <p>The &XercesCName; &XercesCVersion; contains a partial implementation of the W3C
+      <p>The &XercesCName; &XercesC3Version; contains a partial implementation of the W3C
          Document Object Model Level 3.  This implementation is experimental.    See the document
-         <jump href="dom3.html"> DOM Level 3 Support</jump> for details.
+         <jump href="dom3-&XercesC3Series;.html"> DOM Level 3 Support</jump> for details.
       </p>
     </s2>
 
@@ -310,7 +310,7 @@
         }
 
         XercesDOMParser* parser = new XercesDOMParser();
-        parser->setValidationScheme(XercesDOMParser::Val_Always);    
+        parser->setValidationScheme(XercesDOMParser::Val_Always);
         parser->setDoNamespaces(true);    // optional
 
         ErrorHandler* errHandler = (ErrorHandler*) new HandlerBase();
@@ -354,7 +354,7 @@
            of the features below are set using the "setter" methods (e.g. <code>setDoNamespaces</code>),
            and are queried using the corresponding "getter" methods (e.g. <code>getDoNamespaces</code>).
            The following only gives you a quick summary of supported features.  Please
-           refer to <jump href="api.html">API Documentation</jump> for complete detail.
+           refer to <jump href="api-&XercesC3Series;.html">API Documentation</jump> for complete detail.
            </p>
 
             <anchor name="createEntityRef"/>
@@ -552,26 +552,26 @@
                 improves the performance.</td></tr>
             </table>
             <p/>
-            
+
             <anchor name="IdentityConstraintChecking"/>
             <table>
                 <tr><th colspan="2"><em>void setIdentityConstraintChecking(const bool);</em></th></tr>
                 <tr><th><em>true:</em></th><td> Enable identity constraint checking. </td></tr>
                 <tr><th><em>false:</em></th><td> Disable identity constraint checking. </td></tr>
-                <tr><th><em>default:</em></th><td> true </td></tr>                
+                <tr><th><em>default:</em></th><td> true </td></tr>
             </table>
             <p/>
-            
+
             <anchor name="GenerateSyntheticAnnotations"/>
             <table>
                 <tr><th colspan="2"><em>void setGenerateSyntheticAnnotations(const bool);</em></th></tr>
-                <tr><th><em>true:</em></th><td> Enable generation of synthetic annotations.  A synthetic annotation will be 
+                <tr><th><em>true:</em></th><td> Enable generation of synthetic annotations.  A synthetic annotation will be
                 generated when a schema component has non-schema attributes but no child annotation. </td></tr>
                 <tr><th><em>false:</em></th><td> Disable generation of synthetic annotations. </td></tr>
-                <tr><th><em>default:</em></th><td> false </td></tr>                
+                <tr><th><em>default:</em></th><td> false </td></tr>
             </table>
             <p/>
-            
+
             <anchor name="XercesValidateAnnotations"/>
             <table>
                 <tr><th colspan="2"><em>setValidateAnnotation</em></th></tr>
@@ -580,80 +580,80 @@
                 <tr><th><em>default:</em></th><td> false </td></tr>
                 <tr><th><em>note:</em></th><td> Each annotation is validated independently. </td></tr>
             </table>
-            <p/>         
+            <p/>
 
             <anchor name="IgnoreAnnotations"/>
             <table>
                 <tr><th colspan="2"><em>setIgnoreAnnotations</em></th></tr>
                 <tr><th><em>true:</em></th><td> Do not generate XSAnnotations when traversing a schema.</td></tr>
                 <tr><th><em>false:</em></th><td> Generate XSAnnotations when traversing a schema.</td></tr>
-                <tr><th><em>default:</em></th><td> false </td></tr>                
+                <tr><th><em>default:</em></th><td> false </td></tr>
             </table>
-            <p/>    
-            
+            <p/>
+
             <anchor name="DisableDefaultEntityResolution"/>
             <table>
                 <tr><th colspan="2"><em>setDisableDefaultEntityResolution</em></th></tr>
                 <tr><th><em>true:</em></th><td> The parser will not attempt to resolve the entity when the resolveEntity method returns NULL.</td></tr>
                 <tr><th><em>false:</em></th><td> The parser will attempt to resolve the entity when the resolveEntity method returns NULL.</td></tr>
-                <tr><th><em>default:</em></th><td> false </td></tr>                
+                <tr><th><em>default:</em></th><td> false </td></tr>
             </table>
             <p/>
-            
+
             <anchor name="SkipDTDValidation"/>
             <table>
                 <tr><th colspan="2"><em>setSkipDTDValidation</em></th></tr>
                 <tr><th><em>true:</em></th><td> When schema validation is on the parser will ignore the DTD, except for entities.</td></tr>
                 <tr><th><em>false:</em></th><td> The parser will not ignore DTDs when validating.</td></tr>
-                <tr><th><em>default:</em></th><td> false </td></tr>                
+                <tr><th><em>default:</em></th><td> false </td></tr>
                 <tr><th><em>see:</em></th><td>
-                <link anchor="schema">DoSchema</link></td></tr>                
+                <link anchor="schema">DoSchema</link></td></tr>
             </table>
-            <p/>                                               
-                        
+            <p/>
+
             <anchor name="XercesIgnoreCachedDTD"/>
-            <table>            
+            <table>
                 <tr><th colspan="2"><em>setIgnoreCachedDTD</em></th></tr>
-                <tr><th><em>true:</em></th><td> Ignore a cached DTD when an XML document contains both an 
+                <tr><th><em>true:</em></th><td> Ignore a cached DTD when an XML document contains both an
                 								internal and external DTD, and the use cached grammar from parse option
                 								is enabled. Currently, we do not allow using cached DTD grammar when an
                 								internal subset is present in the document. This option will only affect
-                								the behavior of the parser when an internal and external DTD both exist 
+                								the behavior of the parser when an internal and external DTD both exist
                 								in a document (i.e. no effect if document has no internal subset).</td></tr>
                 <tr><th><em>false:</em></th><td> Don't ignore cached DTD. </td></tr>
-                <tr><th><em>default:</em></th><td> false </td></tr>                
+                <tr><th><em>default:</em></th><td> false </td></tr>
                 <tr><th><em>see:</em></th><td>
                 <link anchor="use-cached">useCachedGrammarInParse</link></td></tr>
             </table>
             <p/>
-            
+
             <anchor name="XercesHandleMultipleImports"/>
-            <table>            
+            <table>
                 <tr><th colspan="2"><em>setHandleMultipleImports</em></th></tr>
                 <tr><th><em>true:</em></th><td> During schema validation allow multiple schemas with the same namespace
-                                                to be imported.</td></tr>            
+                                                to be imported.</td></tr>
                 <tr><th><em>false:</em></th><td> Don't import multiple schemas with the same namespace. </td></tr>
-                <tr><th><em>default:</em></th><td> false </td></tr>                                
-            </table>            
+                <tr><th><em>default:</em></th><td> false </td></tr>
+            </table>
             <p/>
-                        
+
             <anchor name="CreateSchemaInfo"/>
             <table>
                 <tr><th colspan="2"><em>setCreateSchemaInfo</em></th></tr>
                 <tr><th><em>true:</em></th><td> Enable storing of PSVI information in element and attribute nodes. </td></tr>
                 <tr><th><em>false:</em></th><td> Disable storing of PSVI information in element and attribute nodes. </td></tr>
-                <tr><th><em>default:</em></th><td> false </td></tr>               
+                <tr><th><em>default:</em></th><td> false </td></tr>
             </table>
-            <p/>         
-            
+            <p/>
+
             <anchor name="CreateCommentNodes"/>
             <table>
                 <tr><th colspan="2"><em>setCreateCommentNodes</em></th></tr>
                 <tr><th><em>true:</em></th><td> Enable the parser to create comment nodes in the DOM tree being produced.</td></tr>
                 <tr><th><em>false:</em></th><td> Disable comment nodes being produced. </td></tr>
-                <tr><th><em>default:</em></th><td> true </td></tr>               
+                <tr><th><em>default:</em></th><td> true </td></tr>
             </table>
-            <p/>                                       
+            <p/>
         </s3>
 
         <anchor name="XercesDOMProperties"/>
@@ -662,7 +662,7 @@
            of the properties below are set using the "setter" methods (e.g. <code>setExternalSchemaLocation</code>),
            and are queried using the corresponding "getter" methods (e.g. <code>getExternalSchemaLocation</code>).
            The following only gives you a quick summary of supported features.  Please
-           refer to <jump href="api.html">API Documentation</jump> for
+           refer to <jump href="api-&XercesC3Series;.html">API Documentation</jump> for
            complete details.
            </p>
             <table>
@@ -715,7 +715,7 @@
                             fgSGXMLScanner, or fgIGXMLScanner) or a string that matches the value of
                             one of those constants.</td></tr>
                 <tr><th><em>Value Type</em></th><td> XMLCh* </td></tr>
-                <tr><th><em>note: </em></th><td> See <jump href="program-others.html#UseSpecificScanner">Use Specific Scanner</jump>
+                <tr><th><em>note: </em></th><td> See <jump href="program-others-&XercesC3Series;.html#UseSpecificScanner">Use Specific Scanner</jump>
                 for more programming details. </td></tr>
             </table>
 
@@ -736,7 +736,7 @@
                 <tr><th
                 colspan="2"><em>setSecurityManager(Security Manager * const)</em></th></tr>
                 <tr><th><em>Description</em></th>
-                <td> 
+                <td>
                     Certain valid XML and XML Schema constructs can force a
                     processor to consume more system resources than an
                     application may wish.  In fact, certain features could
@@ -744,10 +744,10 @@
                     denial-of-service attack.  This property allows
                     applications to impose limits on the amount of
                     resources the processor will consume while processing
-                    these constructs.  
+                    these constructs.
                 </td></tr>
                 <tr><th><em>Value</em></th>
-                <td> 
+                <td>
                     An instance of the SecurityManager class (see
                     <code>xercesc/util/SecurityManager</code>).  This
                     class's documentation describes the particular limits
@@ -798,7 +798,7 @@
     #endif
 
     XERCES_CPP_NAMESPACE_USE
-    
+
     int main (int argc, char* args[]) {
 
         try {
@@ -862,7 +862,7 @@
         return 0;
     }
     </source>
-           <p>Please refer to the <jump href="api.html">API Documentation</jump> and the sample
+           <p>Please refer to the <jump href="api-&XercesC3Series;.html">API Documentation</jump> and the sample
            DOMCount for more detail.
           </p>
         </s3>
@@ -918,7 +918,7 @@
            </source>
            </s4>
 
-        <p>Please refer to the <jump href="api.html">API Documentation</jump> for more detail.
+        <p>Please refer to the <jump href="api-&XercesC3Series;.html">API Documentation</jump> for more detail.
         </p>
         </s3>
 
@@ -953,7 +953,7 @@
                 <tr><th><em>true:</em></th><td> Keep Comment nodes in the document. </td></tr>
                 <tr><th><em>false:</em></th><td> Discard Comment nodes in the document. </td></tr>
                 <tr><th><em>default:</em></th><td> true </td></tr>
-                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgDOMComments </td></tr>                
+                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgDOMComments </td></tr>
                 <tr><th><em>see:</em></th><td>
                 <jump href="http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407">
                 DOM Level 3.0 Load and Save Specification</jump>
@@ -972,7 +972,7 @@
                 <tr><th><em>false:</em></th><td> Any character set encoding information from higher
                 level protocols is ignored by the parser. </td></tr>
                 <tr><th><em>default:</em></th><td> true </td></tr>
-                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgDOMCharsetOverridesXMLEncoding </td></tr>                
+                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgDOMCharsetOverridesXMLEncoding </td></tr>
                 <tr><th><em>see:</em></th><td>
                 <jump href="http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407">
                 DOM Level 3.0 Load and Save Specification</jump>
@@ -988,7 +988,7 @@
                 <tr><th><em>false:</em></th><td> Disable datatype normalization.
                 The XML 1.0 attribute value normalization always occurs though. </td></tr>
                 <tr><th><em>default:</em></th><td> false </td></tr>
-                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgDOMDatatypeNormalization </td></tr>               
+                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgDOMDatatypeNormalization </td></tr>
                 <tr><th><em>note:</em></th><td> Note that setting this feature to true does not affect
                 the DTD normalization operation which always takes place, in accordance to
                 <jump href="http://www.w3.org/TR/2000/REC-xml-20001006">XML 1.0 (Second Edition)</jump>.
@@ -1012,7 +1012,7 @@
                 EntityReference nodes will be created, only the nodes corresponding to their fully
                 expanded substitution text will be created.  </td></tr>
                 <tr><th><em>default:</em></th><td> true </td></tr>
-                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgDOMEntities </td></tr>                
+                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgDOMEntities </td></tr>
                 <tr><th><em>note:</em></th><td> This feature only affects the appearance of
                 EntityReference nodes in the DOM tree. The document will always contain the entity
                 reference child nodes. </td></tr>
@@ -1044,7 +1044,7 @@
                 <tr><th><em>true:</em></th><td> Not Supported. </td></tr>
                 <tr><th><em>false:</em></th><td> No effect. </td></tr>
                 <tr><th><em>default:</em></th><td> false </td></tr>
-                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgDOMInfoset </td></tr>  
+                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgDOMInfoset </td></tr>
                 <tr><th><em>note:</em></th><td> Setting this feature to true is not supported. </td></tr>
                 <tr><th><em>see:</em></th><td>
                 <jump href="http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407">
@@ -1060,7 +1060,7 @@
                 <tr><th><em>true:</em></th><td> Perform Namespace processing </td></tr>
                 <tr><th><em>false:</em></th><td> Do not perform Namespace processing</td></tr>
                 <tr><th><em>default:</em></th><td> false </td></tr>
-                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgDOMNamespaces </td></tr> 
+                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgDOMNamespaces </td></tr>
                 <tr><th><em>note:</em></th><td> If the validation is on, then the
                 document must contain a grammar that supports the use of namespaces </td></tr>
                 <tr><th><em>see:</em></th><td>
@@ -1179,7 +1179,7 @@
                 <tr><th><em>true:</em></th><td> Enable the parser's schema support.  </td></tr>
                 <tr><th><em>false:</em></th><td> Disable the parser's schema support. </td></tr>
                 <tr><th><em>default:</em></th><td> false </td></tr>
-                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesSchema </td></tr>                
+                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesSchema </td></tr>
                 <tr><th><em>note</em></th><td> If set to true, namespace processing must also be turned on. </td></tr>
                 <tr><th><em>see:</em></th><td>
                 <link anchor="builder-namespaces">namespaces</link>
@@ -1313,28 +1313,28 @@
                 improves the performance.</td></tr>
             </table>
             <p/>
-            
+
             <anchor name="builder-IdentityConstraintChecking"/>
             <table>
                 <tr><th colspan="2"><em>http://apache.org/xml/features/validation/identity-constraint-checking</em></th></tr>
                 <tr><th><em>true:</em></th><td> Enable identity constraint checking. </td></tr>
                 <tr><th><em>false:</em></th><td> Disable identity constraint checking. </td></tr>
                 <tr><th><em>default:</em></th><td> true </td></tr>
-                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesIdentityConstraintChecking </td></tr>                
+                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesIdentityConstraintChecking </td></tr>
             </table>
             <p/>
-            
+
             <anchor name="builder-GenerateSyntheticAnnotations"/>
             <table>
                 <tr><th colspan="2"><em>http://apache.org/xml/features/generate-synthetic-annotations</em></th></tr>
-                <tr><th><em>true:</em></th><td> Enable generation of synthetic annotations.  A synthetic annotation will be 
+                <tr><th><em>true:</em></th><td> Enable generation of synthetic annotations.  A synthetic annotation will be
                 generated when a schema component has non-schema attributes but no child annotation. </td></tr>
                 <tr><th><em>false:</em></th><td> Disable generation of synthetic annotations. </td></tr>
                 <tr><th><em>default:</em></th><td> false </td></tr>
-                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesGenerateSyntheticAnnotations </td></tr>                
+                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesGenerateSyntheticAnnotations </td></tr>
             </table>
             <p/>
-            
+
             <anchor name="builder-XercesValidateAnnotations"/>
             <table>
                 <tr><th colspan="2"><em>http://apache.org/xml/features/validate-annotations</em></th></tr>
@@ -1345,75 +1345,75 @@
                 <tr><th><em>note:</em></th><td> Each annotation is validated independently. </td></tr>
             </table>
             <p/>
-            
+
             <anchor name="builder-IgnoreAnnotations"/>
             <table>
                 <tr><th colspan="2"><em>http://apache.org/xml/features/schema/ignore-annotations</em></th></tr>
                 <tr><th><em>true:</em></th><td> Do not generate XSAnnotations when traversing a schema.</td></tr>
                 <tr><th><em>false:</em></th><td> Generate XSAnnotations when traversing a schema.</td></tr>
-                <tr><th><em>default:</em></th><td> false </td></tr>     
-                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesIgnoreAnnotations </td></tr>           
+                <tr><th><em>default:</em></th><td> false </td></tr>
+                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesIgnoreAnnotations </td></tr>
             </table>
-            <p/>    
-            
+            <p/>
+
             <anchor name="builder-DisableDefaultEntityResolution"/>
             <table>
                 <tr><th colspan="2"><em>http://apache.org/xml/features/disable-default-entity-resolution</em></th></tr>
                 <tr><th><em>true:</em></th><td> The parser will not attempt to resolve the entity when the resolveEntity method returns NULL.</td></tr>
                 <tr><th><em>false:</em></th><td> The parser will attempt to resolve the entity when the resolveEntity method returns NULL.</td></tr>
-                <tr><th><em>default:</em></th><td> false </td></tr>       
-                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesDisableDefaultEntityResolution </td></tr>         
+                <tr><th><em>default:</em></th><td> false </td></tr>
+                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesDisableDefaultEntityResolution </td></tr>
             </table>
             <p/>
-            
+
             <anchor name="builder-SkipDTDValidation"/>
             <table>
                 <tr><th colspan="2"><em>http://apache.org/xml/features/validation/schema/skip-dtd-validation</em></th></tr>
                 <tr><th><em>true:</em></th><td> When schema validation is on the parser will ignore the DTD, except for entities.</td></tr>
                 <tr><th><em>false:</em></th><td> The parser will not ignore DTDs when validating.</td></tr>
-                <tr><th><em>default:</em></th><td> false </td></tr>                
+                <tr><th><em>default:</em></th><td> false </td></tr>
                 <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesSkipDTDValidation </td></tr>
                 <tr><th><em>see:</em></th><td>
-                <link anchor="builder-schema">Schema Validation</link></td></tr>                
+                <link anchor="builder-schema">Schema Validation</link></td></tr>
             </table>
-            <p/>                                               
-                        
+            <p/>
+
             <anchor name="builder-IgnoreCachedDTD"/>
-            <table>            
+            <table>
                 <tr><th colspan="2"><em>http://apache.org/xml/features/validation/ignoreCachedDTD</em></th></tr>
-                <tr><th><em>true:</em></th><td> Ignore a cached DTD when an XML document contains both an 
+                <tr><th><em>true:</em></th><td> Ignore a cached DTD when an XML document contains both an
                 								internal and external DTD, and the use cached grammar from parse option
                 								is enabled. Currently, we do not allow using cached DTD grammar when an
                 								internal subset is present in the document. This option will only affect
-                								the behavior of the parser when an internal and external DTD both exist 
+                								the behavior of the parser when an internal and external DTD both exist
                 								in a document (i.e. no effect if document has no internal subset).</td></tr>
                 <tr><th><em>false:</em></th><td> Don't ignore cached DTD. </td></tr>
                 <tr><th><em>default:</em></th><td> false </td></tr>
                 <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesIgnoreCachedDTD </td></tr>
-                <tr><th><em>see:</em></th><td>                
+                <tr><th><em>see:</em></th><td>
                 <link anchor="builder-use-cached">http://apache.org/xml/features/validation/use-cachedGrammarInParse</link>
                 </td></tr>
             </table>
-            <p/>              
-            
+            <p/>
+
             <anchor name="builder-HandleMultipleImports"/>
-            <table>            
+            <table>
                 <tr><th colspan="2"><em>http://apache.org/xml/features/validation/schema/handle-multiple-imports</em></th></tr>
                 <tr><th><em>true:</em></th><td> During schema validation allow multiple schemas with the same namespace
-                                                to be imported.</td></tr>            
+                                                to be imported.</td></tr>
                 <tr><th><em>false:</em></th><td> Don't import multiple schemas with the same namespace. </td></tr>
-                <tr><th><em>default:</em></th><td> false </td></tr>  
-                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesHandleMultipleImports </td></tr>                              
-            </table>   
-            <p/>           
-                        
+                <tr><th><em>default:</em></th><td> false </td></tr>
+                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesHandleMultipleImports </td></tr>
+            </table>
+            <p/>
+
             <anchor name="builder-DOMHasPsviInfo"/>
             <table>
                 <tr><th colspan="2"><em>http://apache.org/xml/features/dom-has-psvi-info</em></th></tr>
                 <tr><th><em>true:</em></th><td> Enable storing of PSVI information in element and attribute nodes.</td></tr>
                 <tr><th><em>false:</em></th><td> Disable storing of PSVI information in element and attribute nodes. </td></tr>
                 <tr><th><em>default:</em></th><td> false </td></tr>
-                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesDOMHasPSVIInfo </td></tr>                
+                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesDOMHasPSVIInfo </td></tr>
             </table>
             <p/>
 
@@ -1429,7 +1429,7 @@
                 <tr><th><em>default:</em></th><td> false </td></tr>
                 <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesUserAdoptsDOMDocument </td></tr>
                 <tr><th><em>see:</em></th><td>
-                <jump href="apiDocs/classDOMLSParser.html">
+                <jump href="api-&XercesC3Series;.html">
                 DOMLSParser API Documentation</jump>, (DOMLSParser::parse and DOMLSParser::resetDocumentPool)
                 </td></tr>
             </table>
@@ -1511,7 +1511,7 @@
                             one of those constants.</td></tr>
                 <tr><th><em>Value Type</em></th><td> XMLCh* </td></tr>
                 <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesScannerName </td></tr>
-                <tr><th><em>note: </em></th><td> See <jump href="program-others.html#UseSpecificScanner">Use Specific Scanner</jump>
+                <tr><th><em>note: </em></th><td> See <jump href="program-others-&XercesC3Series;.html#UseSpecificScanner">Use Specific Scanner</jump>
                 for more programming details. </td></tr>
             </table>
             <p/>
@@ -1528,7 +1528,7 @@
             <table>
                 <tr><th colspan="2"><em>http://apache.org/xml/properties/security-manager</em></th></tr>
                 <tr><th><em>Description</em></th>
-                <td> 
+                <td>
                     Certain valid XML and XML Schema constructs can force a
                     processor to consume more system resources than an
                     application may wish.  In fact, certain features could
@@ -1536,10 +1536,10 @@
                     denial-of-service attack.  This property allows
                     applications to impose limits on the amount of
                     resources the processor will consume while processing
-                    these constructs.  
+                    these constructs.
                 </td></tr>
-                <tr><th><em>Value</em></th>                
-                <td> 
+                <tr><th><em>Value</em></th>
+                <td>
                     An instance of the SecurityManager class (see
                     <code>xercesc/util/SecurityManager</code>).  This
                     class's documentation describes the particular limits
@@ -1584,7 +1584,7 @@
     #include &lt;xercesc/dom/DOM.hpp>
     #include &lt;xercesc/util/XMLString.hpp>
     #include &lt;xercesc/util/PlatformUtils.hpp>
-    
+
     #if defined(XERCES_NEW_IOSTREAMS)
     #include &lt;iostream>
     #else
@@ -1654,7 +1654,7 @@
     }
 
     </source>
-           <p>Please refer to the <jump href="api.html">API Documentation</jump> and the sample
+           <p>Please refer to the <jump href="api-&XercesC3Series;.html">API Documentation</jump> and the sample
            DOMPrint for more detail.
           </p>
         </s3>
@@ -1914,13 +1914,13 @@
             </table>
 
             <p/>
-            
+
             <table>
                 <tr><th colspan="2"><em>xml declaration</em></th></tr>
                 <tr><th><em>true:</em></th><td> Include xml declaration. </td></tr>
-                <tr><th><em>false:</em></th><td> Do not include xml declaration. </td></tr>                
+                <tr><th><em>false:</em></th><td> Do not include xml declaration. </td></tr>
                 <tr><th><em>default:</em></th><td> true </td></tr>
-                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgDOMXMLDeclaration </td></tr>                
+                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgDOMXMLDeclaration </td></tr>
             </table>
 
             <p/>

Modified: xerces/c/trunk/doc/program-others.xml
URL: http://svn.apache.org/viewvc/xerces/c/trunk/doc/program-others.xml?rev=630879&r1=630878&r2=630879&view=diff
==============================================================================
--- xerces/c/trunk/doc/program-others.xml (original)
+++ xerces/c/trunk/doc/program-others.xml Mon Feb 25 07:35:02 2008
@@ -45,7 +45,7 @@
     <anchor name="Schema"/>
     <s2 title="Schema Support">
         <p>&XercesCName; contains an implementation of the W3C XML Schema
-           Language.  See <jump href="schema.html">the Schema page</jump> for details.
+           Language.  See <jump href="schema-&XercesC3Series;.html">the Schema page</jump> for details.
          </p>
     </s2>
 
@@ -130,7 +130,7 @@
 
     <anchor name="GrammarCache"/>
     <s2 title="Preparsing Grammar and Grammar Caching">
-        <p>&XercesCName; &XercesCVersion; provides a new function to pre-parse the grammar so that users
+        <p>&XercesCName; &XercesC3Version; provides a new function to pre-parse the grammar so that users
            can check for any syntax or error before using the grammar.  Users can also optionally
            cache these pre-parsed grammars for later use during actual parsing.
         </p>
@@ -378,7 +378,7 @@
             going, you may want to adapt the message catalog message loader, or
             write one of your own that uses local services.</li>
         <li>What should I define XMLCh to be? Please refer to <jump
-            href="build-misc.html#XMLChInfo">What should I define XMLCh to be?</jump> for
+            href="build-misc-&XercesC3Series;.html#XMLChInfo">What should I define XMLCh to be?</jump> for
             further details.</li>
       </ul>
 
@@ -388,7 +388,7 @@
     <anchor name="CPPNamespace"/>
     <s2 title="Using C++ Namespace">
 
-        <p>&XercesCName; &XercesCVersion; supports C++ Namespace as of Version 2.2.0.</p>
+        <p>&XercesCName; &XercesC3Version; supports C++ Namespace as of Version 2.2.0.</p>
 
         <p>The macro <code>XERCES_HAS_CPP_NAMESPACE</code> is defined in each Compiler
            Definition file if C++ Namespace is supported.</p>
@@ -404,7 +404,7 @@
 </source>
 
         <p>If C++ Namespace support is ENABLED (all the binary
-           distributions of &XercesCName; &XercesCVersion; are built
+           distributions of &XercesCName; &XercesC3Version; are built
            with C++ Namespace enabled), users' applications must
            namespace qualify all the &XercesCName; classes, data and
            variables with <code>XERCES_CPP_NAMESPACE_QUALIFIER </code>
@@ -463,13 +463,13 @@
 
 <source>
 #if defined(XERCES_HAS_CPP_NAMESPACE)
-    #define XERCES_CPP_NAMESPACE_BEGIN    namespace &XercesCNSVersion; {
+    #define XERCES_CPP_NAMESPACE_BEGIN    namespace &XercesC3NSVersion; {
     #define XERCES_CPP_NAMESPACE_END    }
-    #define XERCES_CPP_NAMESPACE_USE    using namespace &XercesCNSVersion;;
-    #define XERCES_CPP_NAMESPACE_QUALIFIER    &XercesCNSVersion;::
+    #define XERCES_CPP_NAMESPACE_USE    using namespace &XercesC3NSVersion;;
+    #define XERCES_CPP_NAMESPACE_QUALIFIER    &XercesC3NSVersion;::
 
-    namespace &XercesCNSVersion; { }
-    namespace &XercesCNamespace; = &XercesCNSVersion;;
+    namespace &XercesC3NSVersion; { }
+    namespace &XercesC3Namespace; = &XercesC3NSVersion;;
 #else
     #define XERCES_CPP_NAMESPACE_BEGIN
     #define XERCES_CPP_NAMESPACE_END
@@ -532,19 +532,19 @@
 <source>
 new XERCES_CPP_NAMESPACE_QUALIFIER SAXParser();
 </source>
-           
+
         <p>Header file <code>xercesc/util/XercesDefs.hpp</code> also
-           declares <code>namespace &XercesCNamespace;</code> as a
+           declares <code>namespace &XercesC3Namespace;</code> as a
            generic namespace name which will be assigned to
            <code>xercesc_YY_ZZ</code> in each specific release, where
            "YY" is the Major Release Number and "ZZ" is the Minor
            Version Number. However, when you use
-           <code>&XercesCNamespace;::</code> instead of
+           <code>&XercesC3Namespace;::</code> instead of
            <code>XERCES_CPP_NAMESPACE_QUALIFIER </code> when your
            compiler does not support namespaces, your code will not
            work.</p>
- 
-           
+
+
 
     </s2>
 
@@ -603,7 +603,7 @@
     {
     }
 ..
-</source> 
+</source>
     </s2>
 
     <anchor name="PluggablePanicHandler"/>
@@ -611,11 +611,11 @@
 
         <p>The &XercesCName; reports, through the method panic(), any panic encountered,
            to the panic handler installed, which in turn takes whatever action appropriate,
-           to handle the panic.                    
+           to handle the panic.
         </p>
-        <p>The &XercesCName; allows application plugging a customized panic handler 
-           (class implementing the interface PanicHandler), in its very first invocation to 
-           XMLPlatformUtils::Initialize() by supplying a parameter for the panic handler 
+        <p>The &XercesCName; allows application plugging a customized panic handler
+           (class implementing the interface PanicHandler), in its very first invocation to
+           XMLPlatformUtils::Initialize() by supplying a parameter for the panic handler
            intended.
         </p>
         <p>In the absence of such a plugged panic handler, &XercesCName; default
@@ -660,7 +660,7 @@
         parser, so long as their code conforms to Xerces-C best
         practices (e.g., avoids implicit destruction of objects
         related to the parser after XMLPlatformUtils::Terminate() has
-        been called; see <jump href="faq-parse.html#faq-7">the FAQ
+        been called; see <jump href="faq-parse-&XercesC3Series;.html#faq-7">the FAQ
         entry describing a reason why applications may suddenly start
         segfaulting with Xerces-C 2.3.0</jump> for details.).  Such users can ignore this subsection and
         continue using the parser as they always had.
@@ -705,7 +705,7 @@
 
 // ...
 delete parser;
-XMLPlatformUtils::Terminate(); 
+XMLPlatformUtils::Terminate();
 </source>
       <p>
         Notice that, to maintain backward compatibility, the
@@ -713,7 +713,7 @@
         parameters to XMLPlatformUtils::Initialize(); this means that
         all other parameters must be specified with their defaults as
         found in Xerces code if all other aspects of standard
-        behaviour are to be preserved.  
+        behaviour are to be preserved.
       </p>
       <p>
         If a user provides a MemoryManager object to the parser, then
@@ -753,7 +753,7 @@
 
     <anchor name="SecurityManager"/>
     <s2 title="Managing Security Vulnerabilities">
-      <p> 
+      <p>
         The purpose of the SecurityManager class is to permit applications a
         means to have the parser reject documents whose processing would
         otherwise consume large amounts of system resources.  Malicious
@@ -788,7 +788,7 @@
 SAXParser *myParser = new SAXParser();
 SecurityManager *myManager = new SecurityManager();
 myManager->setEntityExpansionLimit(100000); // larger than default
-myParser->setSecurityManager(myManager); 
+myParser->setSecurityManager(myManager);
 // ... use the parser
 </source>
       <p>

Modified: xerces/c/trunk/doc/program-sax.xml
URL: http://svn.apache.org/viewvc/xerces/c/trunk/doc/program-sax.xml?rev=630879&r1=630878&r2=630879&view=diff
==============================================================================
--- xerces/c/trunk/doc/program-sax.xml (original)
+++ xerces/c/trunk/doc/program-sax.xml Mon Feb 25 07:35:02 2008
@@ -37,7 +37,7 @@
         called when XML constructs are recognized, and ErrorHandler
         which is called when an error occurs. The header files for the
         various SAX handler classes are in
-        '&lt;&XercesCInstallDir;>/include/xercesc/sax'</p>
+        '&lt;&XercesC3InstallDir;>/include/xercesc/sax'</p>
 
       <p>As a convenience, &XercesCName; provides the class
         HandlerBase, which is a single class which is publicly derived
@@ -174,7 +174,7 @@
            of the features below are set using the "setter" methods (e.g. <code>setDoNamespaces</code>),
            and are queried using the corresponding "getter" methods (e.g. <code>getDoNamespaces</code>).
            The following only gives you a quick summary of supported features.  Please
-           refer to <jump href="api.html">API Documentation</jump> for complete detail.
+           refer to <jump href="api-&XercesC3Series;.html">API Documentation</jump> for complete detail.
            </p>
            <p>None of these features can be modified in the middle of a parse, or an exception will be thrown.</p>
 
@@ -351,20 +351,20 @@
                 <tr><th colspan="2"><em>void setIdentityConstraintChecking(const bool);</em></th></tr>
                 <tr><th><em>true:</em></th><td> Enable identity constraint checking. </td></tr>
                 <tr><th><em>false:</em></th><td> Disable identity constraint checking. </td></tr>
-                <tr><th><em>default:</em></th><td> true </td></tr>                
+                <tr><th><em>default:</em></th><td> true </td></tr>
             </table>
             <p/>
-            
+
             <anchor name="GenerateSyntheticAnnotations"/>
             <table>
                 <tr><th colspan="2"><em>void setGenerateSyntheticAnnotations(const bool);</em></th></tr>
-                <tr><th><em>true:</em></th><td> Enable generation of synthetic annotations.  A synthetic annotation will be 
+                <tr><th><em>true:</em></th><td> Enable generation of synthetic annotations.  A synthetic annotation will be
                 generated when a schema component has non-schema attributes but no child annotation. </td></tr>
                 <tr><th><em>false:</em></th><td> Disable generation of synthetic annotations. </td></tr>
-                <tr><th><em>default:</em></th><td> false </td></tr>                
+                <tr><th><em>default:</em></th><td> false </td></tr>
             </table>
             <p/>
-            
+
             <anchor name="XercesValidateAnnotations"/>
             <table>
                 <tr><th colspan="2"><em>setValidateAnnotation</em></th></tr>
@@ -373,63 +373,63 @@
                 <tr><th><em>default:</em></th><td> false </td></tr>
                 <tr><th><em>note:</em></th><td> Each annotation is validated independently. </td></tr>
             </table>
-            <p/>               
-            
+            <p/>
+
             <anchor name="IgnoreAnnotations"/>
             <table>
                 <tr><th colspan="2"><em>setIgnoreAnnotations</em></th></tr>
                 <tr><th><em>true:</em></th><td> Do not generate XSAnnotations when traversing a schema.</td></tr>
                 <tr><th><em>false:</em></th><td> Generate XSAnnotations when traversing a schema.</td></tr>
-                <tr><th><em>default:</em></th><td> false </td></tr>                
+                <tr><th><em>default:</em></th><td> false </td></tr>
             </table>
-            <p/>    
-            
+            <p/>
+
             <anchor name="DisableDefaultEntityResolution"/>
             <table>
                 <tr><th colspan="2"><em>setDisableDefaultEntityResolution</em></th></tr>
                 <tr><th><em>true:</em></th><td> The parser will not attempt to resolve the entity when the resolveEntity method returns NULL.</td></tr>
                 <tr><th><em>false:</em></th><td> The parser will attempt to resolve the entity when the resolveEntity method returns NULL.</td></tr>
-                <tr><th><em>default:</em></th><td> false </td></tr>                
+                <tr><th><em>default:</em></th><td> false </td></tr>
             </table>
             <p/>
-            
+
             <anchor name="SkipDTDValidation"/>
             <table>
                 <tr><th colspan="2"><em>setSkipDTDValidation</em></th></tr>
                 <tr><th><em>true:</em></th><td> When schema validation is on the parser will ignore the DTD, except for entities.</td></tr>
                 <tr><th><em>false:</em></th><td> The parser will not ignore DTDs when validating.</td></tr>
-                <tr><th><em>default:</em></th><td> false </td></tr>                
+                <tr><th><em>default:</em></th><td> false </td></tr>
                 <tr><th><em>see:</em></th><td>
-                <link anchor="schema">DoSchema</link></td></tr>                
+                <link anchor="schema">DoSchema</link></td></tr>
             </table>
-            <p/>                                                
+            <p/>
 
 			<anchor name="XercesIgnoreCachedDTD"/>
-            <table>            
+            <table>
                 <tr><th colspan="2"><em>setIgnoreCachedDTD</em></th></tr>
-                <tr><th><em>true:</em></th><td> Ignore a cached DTD when an XML document contains both an 
+                <tr><th><em>true:</em></th><td> Ignore a cached DTD when an XML document contains both an
                 								internal and external DTD, and the use cached grammar from parse option
                 								is enabled. Currently, we do not allow using cached DTD grammar when an
                 								internal subset is present in the document. This option will only affect
-                								the behavior of the parser when an internal and external DTD both exist 
+                								the behavior of the parser when an internal and external DTD both exist
                 								in a document (i.e. no effect if document has no internal subset).</td></tr>
                 <tr><th><em>false:</em></th><td> Don't ignore cached DTD. </td></tr>
-                <tr><th><em>default:</em></th><td> false </td></tr>                
+                <tr><th><em>default:</em></th><td> false </td></tr>
                 <tr><th><em>see:</em></th><td>
                 <link anchor="use-cached">useCachedGrammarInParse</link></td></tr>
             </table>
             <p/>
-            
+
             <anchor name="XercesHandleMultipleImports"/>
-            <table>            
+            <table>
                 <tr><th colspan="2"><em>setHandleMultipleImports</em></th></tr>
                 <tr><th><em>true:</em></th><td> During schema validation allow multiple schemas with the same namespace
-                                                to be imported.</td></tr>            
+                                                to be imported.</td></tr>
                 <tr><th><em>false:</em></th><td> Don't import multiple schemas with the same namespace. </td></tr>
-                <tr><th><em>default:</em></th><td> false </td></tr>                                
-            </table>   
-            <p/>         
-                                    
+                <tr><th><em>default:</em></th><td> false </td></tr>
+            </table>
+            <p/>
+
             <table>
                 <tr><th colspan="2"><em>void setExternalSchemaLocation(const XMLCh* const)</em></th></tr>
                 <tr><th><em>Description</em></th><td> The XML Schema Recommendation explicitly states that
@@ -479,7 +479,7 @@
                             Users can use the predefined constants defined in XMLUni directly (fgWFXMLScanner, fgDGXMLScanner,
                             fgSGXMLScanner, or fgIGXMLScanner) or a string that matches the value of one of those constants.</td></tr>
                 <tr><th><em>Value Type</em></th><td> XMLCh* </td></tr>
-                <tr><th><em>note: </em></th><td> See <jump href="program-others.html#UseSpecificScanner">Use Specific Scanner</jump>
+                <tr><th><em>note: </em></th><td> See <jump href="program-others-&XercesC3Series;.html#UseSpecificScanner">Use Specific Scanner</jump>
                 for more programming details. </td></tr>
             </table>
 
@@ -489,7 +489,7 @@
                 <tr><th
                 colspan="2"><em>setSecurityManager(Security Manager * const)</em></th></tr>
                 <tr><th><em>Description</em></th>
-                <td> 
+                <td>
                     Certain valid XML and XML Schema constructs can force a
                     processor to consume more system resources than an
                     application may wish.  In fact, certain features could
@@ -497,10 +497,10 @@
                     denial-of-service attack.  This property allows
                     applications to impose limits on the amount of
                     resources the processor will consume while processing
-                    these constructs.  
+                    these constructs.
                 </td></tr>
                 <tr><th><em>Value</em></th>
-                <td> 
+                <td>
                     An instance of the SecurityManager class (see
                     <code>xercesc/util/SecurityManager</code>).  This
                     class's documentation describes the particular limits
@@ -518,15 +518,15 @@
                     performed.
                 </td></tr>
                 <tr><th><em>Value Type</em></th><td> SecurityManager* </td></tr>
-            </table>                
-            
+            </table>
+
             <p/>
-                        
-            <table>            
+
+            <table>
                 <tr><th
                 colspan="2"><em>setInputBufferSize(const size_t bufferSize)</em></th></tr>
                 <tr><th><em>Description</em></th>
-                <td> 
+                <td>
                     Set maximum input buffer size.
                     This method allows users to limit the size of buffers used in parsing
                     XML character data. The effect of setting this size is to limit the
@@ -534,7 +534,7 @@
                     The parser's default input buffer size is 1 megabyte.
                 </td></tr>
                 <tr><th><em>Value</em></th>
-                <td> 
+                <td>
                     The maximum input buffer size
                 </td></tr>
                 <tr><th><em>Value Type</em></th><td> XMLCh* </td></tr>

Modified: xerces/c/trunk/doc/program-sax2.xml
URL: http://svn.apache.org/viewvc/xerces/c/trunk/doc/program-sax2.xml?rev=630879&r1=630878&r2=630879&view=diff
==============================================================================
--- xerces/c/trunk/doc/program-sax2.xml (original)
+++ xerces/c/trunk/doc/program-sax2.xml Mon Feb 25 07:35:02 2008
@@ -37,7 +37,7 @@
         called when XML constructs are recognized, and ErrorHandler
         which is called when an error occurs. The header files for the
         various SAX2 handler classes are in
-        '&lt;&XercesCInstallDir;>/include/xercesc/sax2'</p>
+        '&lt;&XercesC3InstallDir;>/include/xercesc/sax2'</p>
 
       <p>As a convenience, &XercesCName; provides the class
         DefaultHandler, which is a single class which is publicly derived
@@ -139,7 +139,7 @@
 
         char* xmlFile = "x1.xml";
         SAX2XMLReader* parser = XMLReaderFactory::createXMLReader();
-        parser->setFeature(XMLUni::fgSAX2CoreValidation, true);   
+        parser->setFeature(XMLUni::fgSAX2CoreValidation, true);
         parser->setFeature(XMLUni::fgSAX2CoreNameSpaces, true);   // optional
 
         DefaultHandler* defaultHandler = new DefaultHandler();
@@ -389,28 +389,28 @@
                 improves the performance.</td></tr>
             </table>
             <p/>
-            
+
             <anchor name="IdentityConstraintChecking"/>
             <table>
                 <tr><th colspan="2"><em>http://apache.org/xml/features/validation/identity-constraint-checking</em></th></tr>
                 <tr><th><em>true:</em></th><td> Enable identity constraint checking. </td></tr>
                 <tr><th><em>false:</em></th><td> Disable identity constraint checking. </td></tr>
                 <tr><th><em>default:</em></th><td> true </td></tr>
-                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesIdentityConstraintChecking </td></tr>                
+                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesIdentityConstraintChecking </td></tr>
             </table>
             <p/>
-            
+
             <anchor name="GenerateSyntheticAnnotations"/>
             <table>
                 <tr><th colspan="2"><em>http://apache.org/xml/features/generate-synthetic-annotations</em></th></tr>
-                <tr><th><em>true:</em></th><td> Enable generation of synthetic annotations.  A synthetic annotation will be 
+                <tr><th><em>true:</em></th><td> Enable generation of synthetic annotations.  A synthetic annotation will be
                 generated when a schema component has non-schema attributes but no child annotation. </td></tr>
                 <tr><th><em>false:</em></th><td> Disable generation of synthetic annotations. </td></tr>
                 <tr><th><em>default:</em></th><td> false </td></tr>
-                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesGenerateSyntheticAnnotations </td></tr>                
+                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesGenerateSyntheticAnnotations </td></tr>
             </table>
             <p/>
-            
+
             <anchor name="XercesValidateAnnotations"/>
             <table>
                 <tr><th colspan="2"><em>http://apache.org/xml/features/validate-annotations</em></th></tr>
@@ -420,68 +420,68 @@
                 <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesValidateAnnotations </td></tr>
                 <tr><th><em>note:</em></th><td> Each annotation is validated independently. </td></tr>
             </table>
-            <p/>                                    
-            
+            <p/>
+
             <anchor name="IgnoreAnnotations"/>
             <table>
                 <tr><th colspan="2"><em>http://apache.org/xml/features/schema/ignore-annotations</em></th></tr>
                 <tr><th><em>true:</em></th><td> Do not generate XSAnnotations when traversing a schema.</td></tr>
                 <tr><th><em>false:</em></th><td> Generate XSAnnotations when traversing a schema.</td></tr>
-                <tr><th><em>default:</em></th><td> false </td></tr>     
-                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesIgnoreAnnotations </td></tr>           
+                <tr><th><em>default:</em></th><td> false </td></tr>
+                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesIgnoreAnnotations </td></tr>
             </table>
-            <p/>    
-            
+            <p/>
+
             <anchor name="DisableDefaultEntityResolution"/>
             <table>
                 <tr><th colspan="2"><em>http://apache.org/xml/features/disable-default-entity-resolution</em></th></tr>
                 <tr><th><em>true:</em></th><td> The parser will not attempt to resolve the entity when the resolveEntity method returns NULL.</td></tr>
                 <tr><th><em>false:</em></th><td> The parser will attempt to resolve the entity when the resolveEntity method returns NULL.</td></tr>
-                <tr><th><em>default:</em></th><td> false </td></tr>       
-                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesDisableDefaultEntityResolution </td></tr>         
+                <tr><th><em>default:</em></th><td> false </td></tr>
+                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesDisableDefaultEntityResolution </td></tr>
             </table>
             <p/>
-            
+
             <anchor name="SkipDTDValidation"/>
             <table>
                 <tr><th colspan="2"><em>http://apache.org/xml/features/validation/schema/skip-dtd-validation</em></th></tr>
                 <tr><th><em>true:</em></th><td> When schema validation is on the parser will ignore the DTD, except for entities.</td></tr>
                 <tr><th><em>false:</em></th><td> The parser will not ignore DTDs when validating.</td></tr>
-                <tr><th><em>default:</em></th><td> false </td></tr>                
+                <tr><th><em>default:</em></th><td> false </td></tr>
                 <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesSkipDTDValidation </td></tr>
                 <tr><th><em>see:</em></th><td>
-                <link anchor="schema">Schema Validation</link></td></tr>                
+                <link anchor="schema">Schema Validation</link></td></tr>
             </table>
-            <p/>                                               
-                      
+            <p/>
+
            <anchor name="IgnoreCachedDTD"/>
-            <table>            
+            <table>
                 <tr><th colspan="2"><em>http://apache.org/xml/features/validation/ignoreCachedDTD</em></th></tr>
-                <tr><th><em>true:</em></th><td> Ignore a cached DTD when an XML document contains both an 
+                <tr><th><em>true:</em></th><td> Ignore a cached DTD when an XML document contains both an
                 								internal and external DTD, and the use cached grammar from parse option
                 								is enabled. Currently, we do not allow using cached DTD grammar when an
                 								internal subset is present in the document. This option will only affect
-                								the behavior of the parser when an internal and external DTD both exist 
+                								the behavior of the parser when an internal and external DTD both exist
                 								in a document (i.e. no effect if document has no internal subset).</td></tr>
                 <tr><th><em>false:</em></th><td> Don't ignore cached DTD. </td></tr>
                 <tr><th><em>default:</em></th><td> false </td></tr>
                 <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesIgnoreCachedDTD </td></tr>
-                <tr><th><em>see:</em></th><td>                
+                <tr><th><em>see:</em></th><td>
                 <link anchor="use-cached">http://apache.org/xml/features/validation/use-cachedGrammarInParse</link>
                 </td></tr>
             </table>
-            <p/>              
-            
+            <p/>
+
             <anchor name="builder-HandleMultipleImports"/>
-            <table>            
+            <table>
                 <tr><th colspan="2"><em>http://apache.org/xml/features/validation/schema/handle-multiple-imports</em></th></tr>
                 <tr><th><em>true:</em></th><td> During schema validation allow multiple schemas with the same namespace
-                                                to be imported.</td></tr>            
+                                                to be imported.</td></tr>
                 <tr><th><em>false:</em></th><td> Don't import multiple schemas with the same namespace. </td></tr>
-                <tr><th><em>default:</em></th><td> false </td></tr>  
-                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesHandleMultipleImports </td></tr>                              
-            </table>   
-            <p/>                       
+                <tr><th><em>default:</em></th><td> false </td></tr>
+                <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesHandleMultipleImports </td></tr>
+            </table>
+            <p/>
             </s4>
         </s3>
 
@@ -558,7 +558,7 @@
                             one of those constants.</td></tr>
                 <tr><th><em>Value Type</em></th><td> XMLCh* </td></tr>
                 <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesScannerName </td></tr>
-                <tr><th><em>note: </em></th><td> See <jump href="program-others.html#UseSpecificScanner">Use Specific Scanner</jump>
+                <tr><th><em>note: </em></th><td> See <jump href="program-others-&XercesC3Series;.html#UseSpecificScanner">Use Specific Scanner</jump>
                 for more programming details. </td></tr>
             </table>
 
@@ -567,7 +567,7 @@
             <table>
                 <tr><th colspan="2"><em>http://apache.org/xml/properties/security-manager</em></th></tr>
                 <tr><th><em>Description</em></th>
-                <td> 
+                <td>
                     Certain valid XML and XML Schema constructs can force a
                     processor to consume more system resources than an
                     application may wish.  In fact, certain features could
@@ -575,10 +575,10 @@
                     denial-of-service attack.  This property allows
                     applications to impose limits on the amount of
                     resources the processor will consume while processing
-                    these constructs.  
+                    these constructs.
                 </td></tr>
                 <tr><th><em>Value</em></th>
-                <td> 
+                <td>
                     An instance of the SecurityManager class (see
                     <code>xercesc/util/SecurityManager</code>).  This
                     class's documentation describes the particular limits
@@ -598,14 +598,14 @@
                 <tr><th><em>Value Type</em></th><td> SecurityManager* </td></tr>
                 <tr><th><em>XMLUni Predefined Constant:</em></th><td> fgXercesSecurityManager </td></tr>
             </table>
-            
+
             <p/>
-                        
-            <table>            
+
+            <table>
                 <tr><th
                 colspan="2"><em>setInputBufferSize(const size_t bufferSize)</em></th></tr>
                 <tr><th><em>Description</em></th>
-                <td> 
+                <td>
                     Set maximum input buffer size.
                     This method allows users to limit the size of buffers used in parsing
                     XML character data. The effect of setting this size is to limit the
@@ -613,12 +613,12 @@
                     The parser's default input buffer size is 1 megabyte.
                 </td></tr>
                 <tr><th><em>Value</em></th>
-                <td> 
+                <td>
                     The maximum input buffer size
                 </td></tr>
                 <tr><th><em>Value Type</em></th><td> XMLCh* </td></tr>
             </table>
-                        
+
             <p/>
           </s4>
         </s3>



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xerces.apache.org
For additional commands, e-mail: commits-help@xerces.apache.org