xml-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From p...@locus.apache.org
Subject cvs commit: xml-site/xerces-c apidocs.xml caveats.xml faq-distrib.xml faq-other.xml faq-parse.xml feedback.xml install.xml program.xml readme.xml releases.xml samples.xml
Date Thu, 02 Dec 1999 01:00:46 GMT
pier        99/12/01 17:00:46

  Modified:    .        entities.ent xerces-c.xml
               xerces-c apidocs.xml caveats.xml faq-distrib.xml
                        faq-other.xml faq-parse.xml feedback.xml
                        install.xml program.xml readme.xml releases.xml
                        samples.xml
  Log:
  Modified Entities and Xerces-C documentation.
  
  Revision  Changes    Path
  1.2       +10 -1     xml-site/entities.ent
  
  Index: entities.ent
  ===================================================================
  RCS file: /home/cvs/xml-site/entities.ent,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- entities.ent	1999/12/01 23:21:42	1.1
  +++ entities.ent	1999/12/02 01:00:44	1.2
  @@ -1 +1,10 @@
  -<?xml encoding="US-ASCII"?>
  \ No newline at end of file
  +<?xml encoding="US-ASCII"?>
  +
  +<!ENTITY XercesCFullName     "Xerces C++ Parser">          <!-- fullproductname -->
  +<!ENTITY XercesCName         "Xerces-C">                   <!-- productname -->
  +<!ENTITY XercesCVersion      "1.0">                        <!-- versionnumber -->
  +<!ENTITY XercesCProjectName  "Xerces">                     <!-- projectname -->
  +<!ENTITY XercesCInstallDir   "xerces-1_0">                 <!-- installdirname -->
  +<!ENTITY XercesCWindowsLib   "xerces-c_1_0">               <!-- windowslibname -->
  +<!ENTITY XercesCUnixLib      "libxerces-c1_0">             <!-- unixlibname -->
  +<!ENTITY XercesCEmailAddress "xerces-dev@xml.apache.org "> <!-- emailaddress -->
  
  
  
  1.3       +18 -23    xml-site/xerces-c.xml
  
  Index: xerces-c.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/xerces-c.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- xerces-c.xml	1999/12/01 23:37:22	1.2
  +++ xerces-c.xml	1999/12/02 01:00:44	1.3
  @@ -1,27 +1,22 @@
   <?xml version="1.0"?>
   <!DOCTYPE book SYSTEM "sbk:/style/dtd/book.dtd">
   
  -<book title="Xerces-J documentation" copyright="1999 The Apache Software Foundation">
  -
  -<extern  id="home"      href="../index.html"       label="Home"                     />
  -<separator/>
  -<chapter  id="index"       label="Readme"       href="xerces-c/readme.xml"       type="document"/>
  -<chapter  id="install"     label="Installation" href="xerces-c/install.xml"      type="document"/>
  -<separator/>
  -<chapter  id="api"         label="API Docs"     href="xerces-c/apidocs.xml"      type="document"/>
  -<chapter  id="samples"     label="Samples"      href="xerces-c/samples.xml"      type="document"/>
  -
  -<chapter  id="program"     label="Programming"  href="xerces-c/program.xml"      type="document"/>
  -
  -<group    id="faqs"        label="FAQs"                                         type="faqs">
  -  <hidden id="faq-distrib"                      href="xerces-c/faq-distrib.xml"  type="faq"/>
  -  <hidden id="faq-parse"                        href="xerces-c/faq-parse.xml"    type="faq"/>
  -  <hidden id="faq-other"                        href="xerces-c/faq-other.xml"    type="faq"/>
  -</group>
  -<separator/>
  -
  -<chapter  id="releases"    label="Releases"     href="xerces-c/releases.xml"     type="document"/>
  -<chapter  id="caveats"     label="Caveats"      href="xerces-c/caveats.xml"      type="document"/>
  -<chapter  id="feedback"    label="Feedback"     href="xerces-c/feedback.xml"     type="document"/>
  -
  +<book title="Xerces-C documentation" copyright="1999 The Apache Software Foundation">
  +  <external href="../index.html"  label="Home"/>
  +  <separator/>
  +  <document id="index"       label="Readme"       source="xerces-c/readme.xml"     />
  +  <document id="install"     label="Installation" source="xerces-c/install.xml"    />
  +  <separator/>
  +  <document id="api"         label="API Docs"     source="xerces-c/apidocs.xml"    />
  +  <document id="samples"     label="Samples"      source="xerces-c/samples.xml"    />
  +  <document id="program"     label="Programming"  source="xerces-c/program.xml"    />
  +  <group    id="faqs"        label="FAQs">
  +    <entry  id="faq-distrib"                      source="xerces-c/faq-distrib.xml"/>
  +    <entry  id="faq-parse"                        source="xerces-c/faq-parse.xml"  />
  +    <entry  id="faq-other"                        source="xerces-c/faq-other.xml"  />
  +  </group>
  +  <separator/>
  +  <document id="releases"    label="Releases"     source="xerces-c/releases.xml"   />
  +  <document id="caveats"     label="Caveats"      source="xerces-c/caveats.xml"    />
  +  <document id="feedback"    label="Feedback"     source="xerces-c/feedback.xml"   />
   </book>
  
  
  
  1.3       +6 -6      xml-site/xerces-c/apidocs.xml
  
  Index: apidocs.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/xerces-c/apidocs.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- apidocs.xml	1999/12/02 00:09:34	1.2
  +++ apidocs.xml	1999/12/02 01:00:44	1.3
  @@ -1,24 +1,24 @@
   <?xml version="1.0" standalone="no"?>
  -<!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  +<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
   
   <s1 title="API Documentation">
       <s2 title="API Docs for SAX and DOM">
   
  -    <p>&productname; comes packaged with the API documentation for SAX and DOM - the two
  +    <p>&XercesCName; comes packaged with the API documentation for SAX and DOM - the two
                     most common interfaces for programming XML. In addition the most common
                     framework classes have also been documented.</p>
  -    <p>The &productname; DOM is an implementation of  the Core Level 1 Document Object
  +    <p>The &XercesCName; DOM is an implementation of  the Core Level 1 Document Object
                     model as defined in the W3C Recommendation of 1 October, 1998.  The W3C
                     document is at
                     <jump href="http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/level-one-core.html">
                     http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/level-one-core.html</jump>
       </p>
  -    <p>For a complete understanding of how the &productname; APIs work, we highly
  +    <p>For a complete understanding of how the &XercesCName; APIs work, we highly
                     encourage you to read the DOM Level 1 Specification mentioned above.</p>
       <p>The SAX APIs are derived from the SAX 1.0 Specification which may be found at
                     <jump href="http://www.megginson.com/SAX/index.html">http://www.megginson.com/SAX/index.html</jump>. You are also encouraged to read
  -                  this document for a better understanding of the SAX API in &productname;.</p>
  -    <p><jump href="apiDocs/index.html"><em>Click here to access the &productname; API documentation.</em></jump></p>
  +                  this document for a better understanding of the SAX API in &XercesCName;.</p>
  +    <p><em><jump href="apiDocs/index.html">Click here to access the &XercesCName; API documentation.</jump></em></p>
       <note>The documentation is generated automatically from the comments inside
                     the headers using <jump href="http://www.zib.de/Visual/software/doc++/index.html">DOC++</jump> and then massaged through a script.</note>
   
  
  
  
  1.3       +1 -1      xml-site/xerces-c/caveats.xml
  
  Index: caveats.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/xerces-c/caveats.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- caveats.xml	1999/12/02 00:09:34	1.2
  +++ caveats.xml	1999/12/02 01:00:44	1.3
  @@ -1,5 +1,5 @@
   <?xml version="1.0" standalone="no"?>
  -<!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  +<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
   
   <s1 title="Caveats and Limitations">
   
  
  
  
  1.3       +21 -21    xml-site/xerces-c/faq-distrib.xml
  
  Index: faq-distrib.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/xerces-c/faq-distrib.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- faq-distrib.xml	1999/12/02 00:09:34	1.2
  +++ faq-distrib.xml	1999/12/02 01:00:44	1.3
  @@ -1,19 +1,19 @@
   <?xml version="1.0" ?>
  -<!DOCTYPE s1 SYSTEM "../dtd/faqs.dtd">
  +<!DOCTYPE faqs SYSTEM "sbk:/style/dtd/faqs.dtd">
   
  -<faqs title="Distributing &productname;">
  +<faqs title="Distributing &XercesCName;">
   
   <faq title="Which DLL's do I need to distribute with my application?">
   
   <q>Which DLL's do I need to distribute with my application?</q>
   <a>
  -<p>The current &projectname; distribution contains TWO shared
  -libraries, &windowslibname;.dll and icuuc.dll. To distribute
  +<p>The current &XercesCProjectName; distribution contains TWO shared
  +libraries, &XercesCWindowsLib;.dll and icuuc.dll. To distribute
   your application, you will need to distribute these two
   DLLs along with your own. On AIX the shared library name
  -is &unixlibname;.a and libicu-uc.a, on Solaris/Linux it is
  -called &unixlibname;.so and libicu-uc.so while on HP-UX it
  -is called &unixlibname;.sl and libicu-uc.sl.</p>
  +is &XercesCUnixLib;.a and libicu-uc.a, on Solaris/Linux it is
  +called &XercesCUnixLib;.so and libicu-uc.so while on HP-UX it
  +is called &XercesCUnixLib;.sl and libicu-uc.sl.</p>
   </a>
   
   </faq>
  @@ -30,7 +30,7 @@
   The file may not work if you have changed your
   source tree. You have to modify the script to suit
   your current state of the source tree. To invoke the
  -script, go to the \&lt;&projectname;&gt;\scripts directory, and type:</p>
  +script, go to the \&lt;&XercesCProjectName;&gt;\scripts directory, and type:</p>
   
   <source>
   perl packageBinaries.pl
  @@ -73,19 +73,19 @@
   incorporate these changes in the source code base and make
   them available in the future releases.</p>
   
  -<p>All such changes may be sent to &emailaddress;.</p>
  +<p>All such changes may be sent to &lt;&XercesCEmailAddress;&gt;.</p>
   </a>
   
   </faq>
  -<faq title="How can I port &projectname; to my favourite platform?">
  +<faq title="How can I port &XercesCProjectName; to my favourite platform?">
   
  -<q>How can I port &projectname; to my favourite platform?</q>
  +<q>How can I port &XercesCProjectName; to my favourite platform?</q>
   
   <a>
  -<p>All platform dependent code in &projectname; has been isolated to
  +<p>All platform dependent code in &XercesCProjectName; has been isolated to
   a couple of files, which should ease the porting effort.
   Here are the basic steps that should be followed to port
  -&projectname;.</p>
  +&XercesCProjectName;.</p>
   
   <ol>
   <li>The directory 'src/util/Platforms' contains the
  @@ -93,7 +93,7 @@
   operating system has a file of its own and each
   development environment has another one of its own. (if
   that development environment covers multiple platforms you
  -could use one internally <i>ifdef'd</i> or have multiple ones
  +could use one internally <ref>ifdef'd</ref> or have multiple ones
   with different names).
   <br></br>
   <br></br>
  @@ -117,7 +117,7 @@
   Add the new ones for your platform under the appropriate
   conditionals.</li>
   
  -<li>Now edit 'AutoSense.hpp'. Here we set canonical &projectname;
  +<li>Now edit 'AutoSense.hpp'. Here we set canonical &XercesCProjectName;
   internal #define tokens which indicate the platform and
   compiler. These definitions are based on known platform
   and compiler defines.
  @@ -185,7 +185,7 @@
   
   <q>Can I get the source code for the C++ Builder TreeViewer
   application whose screen shot appears on the front page of
  -&projectname; documentation?</q>
  +&XercesCProjectName; documentation?</q>
   
   <a>
   <p>In view of the numerous requests that we have received for
  @@ -194,21 +194,21 @@
   independent download from IBM's AlphaWorks portal. Please
   note, this is provided on a "as-is, no support" basis.</p>
   
  -<p>This demo application parses the XML file, using &projectname;,
  +<p>This demo application parses the XML file, using &XercesCProjectName;,
   IBM's XML parser for C++, and displays the data as a tree.</p>
   
   <p>The URL is: <jump href="http://www.alphaworks.ibm.com">http://www.alphaWorks.ibm.com</jump></p>
   
  -<p>We welcome your additional feedback at: &emailaddress;</p>
  +<p>We welcome your additional feedback at: &lt;&XercesCEmailAddress;&gt;</p>
   </a>
   
   </faq>
  -<faq title="Can I use &projectname; in my product?">
  +<faq title="Can I use &XercesCProjectName; in my product?">
   
  -<q>Can I use &projectname; in my product?</q>
  +<q>Can I use &XercesCProjectName; in my product?</q>
   <a>
   <p>Yes! Read the license agreement first and contact us at
  -&emailaddress; if you need assistance.</p>
  +&lt;&XercesCEmailAddress;&gt; if you need assistance.</p>
   </a>
   </faq>
   </faqs>
  
  
  
  1.3       +7 -7      xml-site/xerces-c/faq-other.xml
  
  Index: faq-other.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/xerces-c/faq-other.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- faq-other.xml	1999/12/02 00:09:34	1.2
  +++ faq-other.xml	1999/12/02 01:00:44	1.3
  @@ -1,13 +1,13 @@
   <?xml version="1.0" standalone="no"?>
  -<!DOCTYPE s1 SYSTEM "../dtd/faqs.dtd">
  +<!DOCTYPE faqs SYSTEM "sbk:/style/dtd/faqs.dtd">
   
  -<faqs title="Other &productname; Questions">
  +<faqs title="Other &XercesCName; Questions">
   
   <faq title="I can't use C++. Do you have a Java version?">
   
   <q>I can't use C++. Do you have a Java version?</q>
   
  -<a> <p>Yes. The &projectname; family of products also has a Java version.</p>
  +<a> <p>Yes. The &XercesCProjectName; family of products also has a Java version.</p>
   </a>
   
   </faq>
  @@ -15,7 +15,7 @@
   
   <q>I found a bug - what do I do?</q>
   
  -<a> <p>Send the bug report to &emailaddress; with the version number,
  +<a> <p>Send the bug report to &lt;&XercesCEmailAddress;&gt; with the version number,
   the exact OS release number, the compiler version number, and a
   copy of the XML document that generates the error. The more
   information you can provide, the faster we can get a fix into the
  @@ -29,15 +29,15 @@
   <q>I have a question not covered here, or in the documentation -- who
   do I contact?</q>
   
  -<a>
  +<a><p>
   First post your question on the
   <jump href="http://www.alphaworks.ibm.com/aw.nsf/discussion?ReadForm&amp;/forum/xml4c.nsf/discussion?createdocument">XML4C
   discussion group on Alphaworks</jump>, and
   someone from the XML4C development team will answer that question. The list is
   monitored very closely and the response is usually within 24 hours. If you need to
  -ask a special question privately, send email to <jump href="mailto:&emailaddress;">&emailaddress;</jump> and give us
  +ask a special question privately, send email to &lt;<jump href="mailto:&XercesCEmailAddress;">&XercesCEmailAddress;</jump>&gt; and give us
   as much information as you can. We'll get back to you as soon as possible!
  -</a>
  +</p></a>
   
   </faq>
   
  
  
  
  1.3       +88 -88    xml-site/xerces-c/faq-parse.xml
  
  Index: faq-parse.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/xerces-c/faq-parse.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- faq-parse.xml	1999/12/02 00:09:34	1.2
  +++ faq-parse.xml	1999/12/02 01:00:44	1.3
  @@ -1,7 +1,7 @@
   <?xml version="1.0" standalone="no"?>
  -<!DOCTYPE s1 SYSTEM "../dtd/faqs.dtd">
  +<!DOCTYPE faqs SYSTEM "sbk:/style/dtd/faqs.dtd">
   
  -<faqs title="Parsing with &productname;">
  +<faqs title="Parsing with &XercesCName;">
       <faq title="Why does my application crash on AIX when I run it under a
            multi-threaded environment?">
   
  @@ -27,22 +27,22 @@
             LIBPATH can be simply set as:</p>
   
           <source>
  -LIBPATH=$HOME/&lt;&projectname;&gt;/lib
  +LIBPATH=$HOME/&lt;&XercesCProjectName;&gt;/lib
   </source>
   
  -        <p>Where &lt;&projectname;&gt; points to the directory where
  -          &projectname; application resides.</p>
  +        <p>Where &lt;&XercesCProjectName;&gt; points to the directory where
  +          &XercesCProjectName; application resides.</p>
   
  -        <p>If for any reason, unrelated to &projectname;, you need to
  +        <p>If for any reason, unrelated to &XercesCProjectName;, you need to
             keep a 'system library path' in your LIBPATH environment
             variable, you must make sure that you have placed the
             thread-safe path before you specify the normal system
  -          path. For example, you must place <i>/lib/threads</i> before
  -          <i>/lib</i> in your LIBPATH variable. That is to say your
  +          path. For example, you must place <ref>/lib/threads</ref> before
  +          <ref>/lib</ref> in your LIBPATH variable. That is to say your
             LIBPATH may look like this:</p>
   
           <source>
  -export LIBPATH=$HOME/&lt;&projectname;&gt;/lib:/usr/lib/threads:/usr/lib
  +export LIBPATH=$HOME/&lt;&XercesCProjectName;&gt;/lib:/usr/lib/threads:/usr/lib
   </source>
   
           <p>Where /usr/lib is where your system libraries are.</p>
  @@ -54,7 +54,7 @@
       <q>What compilers are being used on the supported platforms?</q>
   
       <a>
  -      <p>&projectname; has been built on the following platforms with these
  +      <p>&XercesCProjectName; has been built on the following platforms with these
           compilers</p>
   
         <table>
  @@ -77,14 +77,14 @@
       <q>I cannot run my sample applications. What is wrong?</q>
       <a>
         <p>There are two major installation issues which must be dealt
  -        with in order to use &projectname; from your applications. The
  +        with in order to use &XercesCProjectName; from your applications. The
           DLL or shared library must be locatable via the system's
  -        environment. And, the converter files used by &projectname; for
  +        environment. And, the converter files used by &XercesCProjectName; for
           its transcoding must be locatable.
         </p>
         <p>On UNIX platforms you need to ensure that your library search
           environment variable includes the directory which has the
  -        &projectname; shared library (On AIX, this is LIBPATH, on
  +        &XercesCProjectName; shared library (On AIX, this is LIBPATH, on
           Solaris and Linux it is LD_LIBRARY_PATH while on HP-UX it is
           SHLIB_PATH). Thus, if you installed your binaries under
           <code>$HOME/fastxmlparser</code>, you need to point your
  @@ -99,7 +99,7 @@
   export SHLIB_PATH=$SHLIB_PATH:$HOME/fastxmlparser/lib # (HP-UX)
   </source>
   
  -      <p>On Win32, you would ensure that the &projectname; DLLs are in
  +      <p>On Win32, you would ensure that the &XercesCProjectName; DLLs are in
           the PATH environment.</p>
   
         <p>For the transcoding files <code>(*.cnv)</code>, the most
  @@ -109,7 +109,7 @@
           <code>icu/data</code> directory relative to the shared library
           or DLL. This will allow them to be located automatically.</p>
   
  -      <p>However, if you redistribute &projectname; within some other
  +      <p>However, if you redistribute &XercesCProjectName; within some other
           product, and cannot maintain this relationship, or if your
           build scenario does not allow you to maintain this
           relationship during debugging for instance, you can use the
  @@ -123,16 +123,16 @@
       </a>
     </faq>
   
  -  <faq title="I just built my own application using the &projectname; parser. Why does it
  +  <faq title="I just built my own application using the &XercesCProjectName; parser. Why does it
          crash?">
   
  -    <q>I just built my own application using the &projectname; parser. Why does it
  +    <q>I just built my own application using the &XercesCProjectName; parser. Why does it
         crash?</q>
       <a>
  -      <p>In order to work with the &projectname; parser, you have to
  +      <p>In order to work with the &XercesCProjectName; parser, you have to
           first initialize the XML subsystem. The most common mistake is
           to forget this initialization. Before you make any calls to
  -        &projectname; APIs, you must call</p>
  +        &XercesCProjectName; APIs, you must call</p>
   
         <source>
       XMLPlatformUtils::Initialize():
  @@ -144,7 +144,7 @@
       }
   </source>
   
  -      <p>This initializes the &projectname; system and sets its
  +      <p>This initializes the &XercesCProjectName; system and sets its
           internal variables.  Note that you must the include
           <code>util/PlatformUtils.hpp</code> file for this to work.</p>
   
  @@ -153,25 +153,25 @@
           simple fix, if you understand how the transcoding converter
           files are searched.</p>
   
  -      <p>&projectname; first looks for the environment variable
  +      <p>&XercesCProjectName; first looks for the environment variable
           ICU_DATA. If it finds this variable in your environment
           settings, then it assumes that the transcoding converter files
           are kept in that directory.  Thus, for example, if you had set
           your environment variable to (say):</p>
   
         <source>
  -set ICU_DATA=d:\my&projectname;\icu\data
  +set ICU_DATA=d:\my&XercesCProjectName;\icu\data
         </source>
   
         <p>The transcoding converter files (all files having extension
           .cnv and convrtrs.txt) will be searched under
  -        <code>d:\my&projectname;\icu\data</code></p>
  +        <code>d:\my&XercesCProjectName;\icu\data</code></p>
   
         <p>If you have not set your environment variable, then the
           search for the transcoding converters is done relative to the
  -        location of the shared library &windowslibname;.dll (or
  -        &unixlibname;.a on AIX and &unixlibname;.so on Solaris and
  -        Linux, &unixlibname;.sl on HP-UX). Thus if your shared library
  +        location of the shared library &XercesCWindowsLib;.dll (or
  +        &XercesCUnixLib;.a on AIX and &XercesCUnixLib;.so on Solaris and
  +        Linux, &XercesCUnixLib;.sl on HP-UX). Thus if your shared library
           is in <code>d:\fastxmlparser\lib</code>, then your transcoding
           converter files should be in
           <code>d:\fastxmlparser\lib\icu\data.</code></p>
  @@ -182,12 +182,12 @@
       </a>
     </faq>
   
  -  <faq title="How do I use VisualAge for Windows with &projectname;?">
  +  <faq title="How do I use VisualAge for Windows with &XercesCProjectName;?">
   
  -    <q>How do I use VisualAge for Windows with &projectname;</q>
  +    <q>How do I use VisualAge for Windows with &XercesCProjectName;</q>
   
       <a>
  -      <p>IBM VisualAge &projectname; for Windows Build Requirements</p>
  +      <p>IBM VisualAge &XercesCProjectName; for Windows Build Requirements</p>
   
         <ol>
           <li>VisualAge C++ Version 4.0 with Fixpak 1: Download the
  @@ -197,27 +197,27 @@
             </jump></li>
   
           <li>ICU Build: You should have the ICU Library in the same
  -          directory as the &projectname; library. For example if
  -          &projectname; is at the top level of the d drive, put the
  +          directory as the &XercesCProjectName; library. For example if
  +          &XercesCProjectName; is at the top level of the d drive, put the
             ICU library also at the top level of d drive
  -          e.g. d:/&projectname;, d:/icu.</li>
  +          e.g. d:/&XercesCProjectName;, d:/icu.</li>
         </ol>
   
         <p>Instructions</p>
   
         <note>These instructions assume that you are installing in
  -        d:\&projectname; Replace d with the appropriate drive
  +        d:\&XercesCProjectName; Replace d with the appropriate drive
           letter.</note>
   
         <ol>
  -        <li>Change directory to d:\&projectname;\Projects\Win32</li>
  +        <li>Change directory to d:\&XercesCProjectName;\Projects\Win32</li>
   
  -        <li>If a d:\&projectname;\Project\Win32\VACPP40 directory does
  +        <li>If a d:\&XercesCProjectName;\Project\Win32\VACPP40 directory does
             not exist, create it.</li>
   
  -        <li>Copy the IBM VisualAge project file, &projectname;X.icc,
  +        <li>Copy the IBM VisualAge project file, &XercesCProjectName;X.icc,
             to the VACPP40 directory. (If it is not provided in your
  -          download, request it from &emailaddress;.</li>
  +          download, request it from &lt;&XercesCEmailAddress;&gt;.</li>
   
           <li>From the VisualAge main menu enter the project file name
             and path.</li>
  @@ -230,12 +230,12 @@
       </a>
     </faq>
   
  -  <faq title="How do I use VisualAge for OS/2 with &projectname;?">
  +  <faq title="How do I use VisualAge for OS/2 with &XercesCProjectName;?">
   
  -    <q>How do I use VisualAge for OS/2 with &projectname;</q>
  +    <q>How do I use VisualAge for OS/2 with &XercesCProjectName;</q>
   
       <a>
  -      <p>IBM VisualAge &projectname;/C++ for Windows Build Requirements</p>
  +      <p>IBM VisualAge &XercesCProjectName;/C++ for Windows Build Requirements</p>
   
         <ol>
           <li>VisualAge C++ Version 4.0 with Fixpak 1: Download the
  @@ -245,10 +245,10 @@
             </jump></li>
   
           <li>ICU Build: You should have the ICU Library in the same
  -          directory as the &projectname; library. For example if
  -          &projectname; is at the top level of the d drive, put the
  +          directory as the &XercesCProjectName; library. For example if
  +          &XercesCProjectName; is at the top level of the d drive, put the
             ICU library also at the top level of d drive
  -          e.g. d:/&projectname;, d:/icu.</li>
  +          e.g. d:/&XercesCProjectName;, d:/icu.</li>
         </ol>
   
         <p>Instructions</p>
  @@ -259,15 +259,15 @@
         </note>
         <ol>
           <li>Change directory to
  -        d:\&projectname;\Projects\Win32</li>
  +        d:\&XercesCProjectName;\Projects\Win32</li>
   
  -        <li>If a d:\&projectname;\Project\OS2\VACPP40 directory
  +        <li>If a d:\&XercesCProjectName;\Project\OS2\VACPP40 directory
             does not exist, create it.</li>
   
           <li>Copy the IBM VisualAge project file,
  -          &projectname;X.icc, to the VACPP40 directory. (If it is not
  +          &XercesCProjectName;X.icc, to the VACPP40 directory. (If it is not
             provided in your download, request it from
  -          &emailaddress;.</li>
  +          &lt;&XercesCEmailAddress;&gt;.</li>
   
           <li>From the VisualAge main menu enter the project file
             name and path.</li>
  @@ -278,27 +278,27 @@
       </a>
     </faq>
   
  -  <faq title="How do I use CodeWarrior for Macintosh with &projectname;">
  +  <faq title="How do I use CodeWarrior for Macintosh with &XercesCProjectName;">
   
  -    <q>How do I use CodeWarrior for Macintosh with &projectname;</q>
  +    <q>How do I use CodeWarrior for Macintosh with &XercesCProjectName;</q>
       <a>
  -      <p>The directions in this file cover installing and building &projectname;
  +      <p>The directions in this file cover installing and building &XercesCProjectName;
           and ICU under the MacOS using CodeWarrior.</p>
   
         <ol>
  -        <li>Create a folder that will contain the &projectname; and
  +        <li>Create a folder that will contain the &XercesCProjectName; and
             ICU distributions. For future reference I will refer to this
             folder as "src drop".</li>
   
           <li>Download and uncompress the ICU source distribution and
  -          the &projectname; source distribution.  You might also want
  +          the &XercesCProjectName; source distribution.  You might also want
             to download the binary distributions because they may
             contain documentation not present in the source
             distribution.  This will create two additional directories;
  -          &projectname; and icu Folder. Move these folders into the
  +          &XercesCProjectName; and icu Folder. Move these folders into the
             "src drop" folder.</li>
   
  -        <li>Drag the &projectname; folder and drop it on to the
  +        <li>Drag the &XercesCProjectName; folder and drop it on to the
             "rename file" application located in the same folder as this
             readme. This is a MacPerl script that renames files with
             names too long to fit in a HFS/HFS+ filesystem.  It also
  @@ -306,30 +306,30 @@
             #include statements to refer to the new file names.</li>
   
           <li>Move the MacOS folder (in the Projects folder) to "src
  -          drop:&projectname;:Projects".</li>
  +          drop:&XercesCProjectName;:Projects".</li>
   
           <li>You should be able to open the CodeWarrior project file
  -          "src drop:&projectname;:Projects:MacOS:&projectname;:&projectname;"
  -          and build the &projectname; library.</li>
  +          "src drop:&XercesCProjectName;:Projects:MacOS:&XercesCProjectName;:&XercesCProjectName;"
  +          and build the &XercesCProjectName; library.</li>
   
           <li>You should also be able to open the CodeWarrior project
  -          file "src drop:&projectname;:Projects:MacOS:icu:icu" and
  +          file "src drop:&XercesCProjectName;:Projects:MacOS:icu:icu" and
             build the ICU library.</li>
   
           <li>If you wish you can create projects for and build the rest
             of the tools and test suites.  They are not needed if you
  -          just want to use &projectname;.  I suggest that you use the
  +          just want to use &XercesCProjectName;.  I suggest that you use the
             binary data files distributed with the binary distribution
             of ICU instead of creating your own from the text data files
             in the ICE source distribution.</li>
         </ol>
   
         <p>There are some things to be aware of when creating your own
  -        projects using &projectname;.</p>
  +        projects using &XercesCProjectName;.</p>
   
         <ol>
           <li>You will need to link against both the ICU and
  -          &projectname; libraries.</li>
  +          &XercesCProjectName; libraries.</li>
   
           <li>The options "Always search user paths" and "Interpret DOS
             and Unix Paths" are very useful.  Some of the code won't
  @@ -341,24 +341,24 @@
             them working correctly.</li>
   
           <li>You will most likely have to set up the Access Paths. The
  -          access paths in the &projectname; projects should serve as a
  +          access paths in the &XercesCProjectName; projects should serve as a
             good example.</li>
         </ol>
   
  -      <p>If you are having problems getting &projectname; working, feel
  +      <p>If you are having problems getting &XercesCProjectName; working, feel
           free to send an email to <jump href="mailto:jbellardo@alumni.calpoly.edu">
           jbellardo@alumni.calpoly.edu</jump>. However, help will arrive
           only if time permits.</p>
       </a>
     </faq>
   
  -  <faq title="Is &projectname; thread-safe?">
  +  <faq title="Is &XercesCProjectName; thread-safe?">
   
  -    <q>Is &projectname; thread-safe?</q>
  +    <q>Is &XercesCProjectName; thread-safe?</q>
   
       <a>
         <p>This is not a question that has a simple yes/no answer. Here are
  -        the rules for using &projectname; in a multi-threaded environment:</p>
  +        the rules for using &XercesCProjectName; in a multi-threaded environment:</p>
   
         <p>Within an address space, an instance of the parser may be used
           without restriction from a single thread, or an instance of the
  @@ -373,7 +373,7 @@
           first thread concurrently with the second parser running
           within the second thread.</p>
   
  -      <p>The same rules apply to &projectname; DOM documents -
  +      <p>The same rules apply to &XercesCProjectName; DOM documents -
           multiple document instances may be concurrently accessed from
           different threads, but any given document instance can only be
           accessed by one thread at a time.</p>
  @@ -387,12 +387,12 @@
       </a>
     </faq>
   
  -  <faq title="How do I find out what version of &projectname; I am using?">
  +  <faq title="How do I find out what version of &XercesCProjectName; I am using?">
   
  -    <q>How do I find out what version of &projectname; I am using?</q>
  +    <q>How do I find out what version of &XercesCProjectName; I am using?</q>
   
       <a>
  -      <p>The version string for &projectname; happens to be in one of
  +      <p>The version string for &XercesCProjectName; happens to be in one of
           the source files. Look inside the file
           <code>src/util/XML4CDefs.hpp</code> and find out what the
           static variable <code>gXML4CFullVersionStr</code> is defined
  @@ -401,25 +401,25 @@
   
         <p>If you don't have the source code, you have to find the version
           information from the shared library name. On Windows NT/95/98
  -        right click on the DLL name &windowslibname;.dll in the bin directory
  +        right click on the DLL name &XercesCWindowsLib;.dll in the bin directory
           and look up properties. The version information may be found on
           the Version tab.</p>
   
  -      <p>On AIX, just look for the library name &unixlibname;.a (or
  -        &unixlibname;.so on Solaris/Linux and &unixlibname;.sl on
  +      <p>On AIX, just look for the library name &XercesCUnixLib;.a (or
  +        &XercesCUnixLib;.so on Solaris/Linux and &XercesCUnixLib;.sl on
           HP-UX).  The version number is coded in the name of the
           library.</p>
       </a>
     </faq>
   
  -  <faq title="How do I uninstall &projectname;?">
  +  <faq title="How do I uninstall &XercesCProjectName;?">
   
  -    <q>How do I uninstall &projectname;?</q>
  +    <q>How do I uninstall &XercesCProjectName;?</q>
       <a>
  -      <p>&projectname; only installs itself in a single directory and
  +      <p>&XercesCProjectName; only installs itself in a single directory and
           does not set any registry entries. Thus, to un-install, you
           only need to remove the directory where you installed it, and
  -        all &projectname; related files will be removed.</p>
  +        all &XercesCProjectName; related files will be removed.</p>
       </a>
     </faq>
   
  @@ -429,7 +429,7 @@
       set?</q>
   
       <a>
  -      <p>Transcoding files shipped with binary drops of &projectname;
  +      <p>Transcoding files shipped with binary drops of &XercesCProjectName;
           exist in the <code>bin/icu/data</code> directory on Win32 and
           in the <code>lib/icu/data</code> directory under various
           unix's.  All transcoding files have the extension .cnv and are
  @@ -482,9 +482,9 @@
       </a>
     </faq>
   
  -  <faq title="What kinds of URLs are currently supported in &projectname;?">
  +  <faq title="What kinds of URLs are currently supported in &XercesCProjectName;?">
   
  -    <q>What kinds of URLs are currently supported in &projectname;?</q>
  +    <q>What kinds of URLs are currently supported in &XercesCProjectName;?</q>
       <a>
         <p>We now have a spec. compliant, but limited, implementation of
           the class URL.</p>
  @@ -503,11 +503,11 @@
         <p>Examples of what this implementation will allow you to do are:</p>
   
         <source>
  -e:\&gt;domcount file:///e:/&projectname;/build/win32/vc6/debug/abc.xml
  +e:\&gt;domcount file:///e:/&XercesCProjectName;/build/win32/vc6/debug/abc.xml
   
   or
   
  -e:\&gt;domcount file::///&projectname;/build/win32/vc6/debug/abc.xml
  +e:\&gt;domcount file::///&XercesCProjectName;/build/win32/vc6/debug/abc.xml
   e:\&gt;domcount file::///d:/abc.xml
   
   or
  @@ -534,9 +534,9 @@
       </a>
     </faq>
   
  -  <faq title="Can I use &projectname; to parse HTML?">
  +  <faq title="Can I use &XercesCProjectName; to parse HTML?">
   
  -    <q>Can I use &projectname; to parse HTML?</q>
  +    <q>Can I use &XercesCProjectName; to parse HTML?</q>
   
       <a>
         <p>Yes, if it follows the XML spec rules. Most HTML, however,
  @@ -568,14 +568,14 @@
     </faq>
   
   
  -  <faq title="What encodings are supported by &projectname;?">
  +  <faq title="What encodings are supported by &XercesCProjectName;?">
   
  -    <q>What encodings are supported by &projectname;?</q>
  +    <q>What encodings are supported by &XercesCProjectName;?</q>
   
       <a>
  -      <p>&projectname; uses a subset of IBM's International Classes
  +      <p>&XercesCProjectName; uses a subset of IBM's International Classes
           for Unicode (ICU) for encoding &amp; Unicode
  -        support. &fullproductname; is Unicode 3.0 compliant.</p>
  +        support. &XercesCFullName; is Unicode 3.0 compliant.</p>
   
         <p>Besides ASCII, the following encodings are currrently
         supported:</p>
  
  
  
  1.3       +3 -3      xml-site/xerces-c/feedback.xml
  
  Index: feedback.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/xerces-c/feedback.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- feedback.xml	1999/12/02 00:09:34	1.2
  +++ feedback.xml	1999/12/02 01:00:44	1.3
  @@ -1,13 +1,13 @@
   <?xml version="1.0" standalone="no"?>
  -<!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  +<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
   
   <s1 title="Feedback Procedures">
       <s2 title="Questions or Comments">
  -        <p>For all questions or comments, write to the &projectname; mailing list.</p>
  +        <p>For all questions or comments, write to the &XercesCProjectName; mailing list.</p>
           <p>If you are submitting a bug (and bug reports are definitely appreciated!),
               please provide the following information:</p>
           <ul>
  -            <li>Version number of &productname; (&versionnumber;?) </li>
  +            <li>Version number of &XercesCName; (&XercesCVersion;?) </li>
               <li>Which OS platform/version you are using (NT4+SP4? Win98? Redhat Linux 6.0? Solaris2.6? AIX 4.3? HP-UX10? HP-UX11?) </li>
               <li>Which compiler/version you are using (MSVC6? gcc? cc? aCC?) </li>
               <li>Sample XML file that causes the bug</li>
  
  
  
  1.3       +17 -17    xml-site/xerces-c/install.xml
  
  Index: install.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/xerces-c/install.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- install.xml	1999/12/02 00:09:34	1.2
  +++ install.xml	1999/12/02 01:00:44	1.3
  @@ -1,34 +1,34 @@
   <?xml version="1.0" standalone="no"?>
  -<!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  +<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
   
   <s1 title="Installation">
   
   
       <s2 title="Window NT/98">
           <p>
  -        Binary installation of this release of &productname; is simply to unzip the .zip
  +        Binary installation of this release of &XercesCName; is simply to unzip the .zip
           archive under Windows environment (using WinZip, or any other UnZip utility like
           WinZip).
           </p>
           <source>
  -unzip &installdirname;-win32.zip </source>
  +unzip &XercesCInstallDir;-win32.zip </source>
   
           <p>
  -        This will create a '&installdirname;-win32' sub-directory (in the current directory)
  -        which contains the &productname; distribution. </p>
  +        This will create a '&XercesCInstallDir;-win32' sub-directory (in the current directory)
  +        which contains the &XercesCName; distribution. </p>
   
           <p>
  -        You will need to add the '&installdirname;-win32\bin' directory to your path: </p>
  +        You will need to add the '&XercesCInstallDir;-win32\bin' directory to your path: </p>
   
           <p>To do this under Windows NT, go to the start menu, click the settings menu
           and
           select control panel. When the control panel opens, double click on System and
           select the 'Environment' tab. Locate the PATH variable under system variables
  -        and add &lt;full_path_to_&installdirname;>\bin to the PATH variable.  To do this
  +        and add &lt;full_path_to_&XercesCInstallDir;>\bin to the PATH variable.  To do this
           under Windows 95/98 add the line:</p>
   
           <source>
  -   SET PATH=&lt;full_path_to_&installdirname;>\bin;%PATH%  </source>
  +   SET PATH=&lt;full_path_to_&XercesCInstallDir;>\bin;%PATH%  </source>
   
            <p>
            to your AUTOEXEC.BAT file, or run the set in your shell window.
  @@ -43,22 +43,22 @@
   
           <source>
   cd $HOME
  -gunzip &installdirname;-linux.tar.gz
  -tar -xvf &installdirname;-linux.tar </source>
  +gunzip &XercesCInstallDir;-linux.tar.gz
  +tar -xvf &XercesCInstallDir;-linux.tar </source>
   
           <p>
  -        This will create an '&installdirname;-linux' sub-directory (in the home directory)
  -        which contains the &productname; distribution. You will need to add the
  -        &installdirname;-linux/bin directory to your PATH environment variable:
  +        This will create an '&XercesCInstallDir;-linux' sub-directory (in the home directory)
  +        which contains the &XercesCName; distribution. You will need to add the
  +        &XercesCInstallDir;-linux/bin directory to your PATH environment variable:
           </p>
   
           <p>For Bourne Shell, K Shell or Bash, type: </p>
           <source>
  -    export PATH="$PATH:$HOME/&installdirname;-linux/bin" </source>
  +    export PATH="$PATH:$HOME/&XercesCInstallDir;-linux/bin" </source>
   
           <p>For C Shell type:</p>
           <source>
  -    setenv PATH "$PATH:$HOME/&installdirname;-linux/bin"</source>
  +    setenv PATH "$PATH:$HOME/&XercesCInstallDir;-linux/bin"</source>
   
           <p>If you wish to make this setting permanent, you need to change your profile
           by
  @@ -75,7 +75,7 @@
           <p>For Bourne Shell, K Shell or Bash, type:</p>
   
   <source>
  -export XERCESCROOT=&lt;wherever you installed &productname;>
  +export XERCESCROOT=&lt;wherever you installed &XercesCName;>
   export ICUROOT=&lt;wherever you installed ICU>
   export LIBPATH=$XERCESCROOT/lib:$LIBPATH (on AIX)
   export LD_LIBRARY_PATH=$XERCESCROOT/lib:$LD_LIBRARY_PATH (on Solaris, Linux)
  @@ -84,7 +84,7 @@
       <p>For C Shell, type:</p>
   
   <source>
  -setenv XERCESCROOT "&lt;wherever you installed &productname;>"
  +setenv XERCESCROOT "&lt;wherever you installed &XercesCName;>"
   setenv ICUROOT "&lt;wherever you installed ICU>"
   setenv LIBPATH "$XERCESCROOT/lib:$LIBPATH" (on AIX)
   setenv LD_LIBRARY_PATH "$XERCESCROOT/lib:$LD_LIBRARY_PATH" (on Solaris, Linux)
  
  
  
  1.3       +32 -54    xml-site/xerces-c/program.xml
  
  Index: program.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/xerces-c/program.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- program.xml	1999/12/02 00:09:34	1.2
  +++ program.xml	1999/12/02 01:00:44	1.3
  @@ -1,15 +1,15 @@
   <?xml version="1.0" standalone="no"?>
  -<!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  +<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
   
   <s1 title="Programming Guide">
     <s2 title="SAX Programming Guide">
       <s3 title="Constructing a parser">
  -      <p>In order to use &productname; to parse XML files, you will
  +      <p>In order to use &XercesCName; to parse XML files, you will
           need to create an instance of the SAXParser class. The example
           below shows the code you need in order to create an instance
           of SAXParser. The DocumentHandler and ErrorHandler instances
           required by the SAX API are provided using the HandlerBase
  -        class supplied with &productname;.</p>
  +        class supplied with &XercesCName;.</p>
   
         <source><![CDATA[
   int main (int argc, char* args[]) {
  @@ -47,7 +47,7 @@
       <s3 title="Using the SAX API">
         <p>The SAX API for XML parsers was originally developed for
           Java.  Please be aware that there is no standard SAX API for
  -        C++, and that use of the &productname; SAX API does not
  +        C++, and that use of the &XercesCName; SAX API does not
           guarantee client code compatibility with other C++ XML
           parsers.</p>
   
  @@ -60,13 +60,13 @@
           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;&installdirname;>/include/sax'</p>
  +        '&lt;&XercesCInstallDir;>/include/sax'</p>
   
  -      <p>As a convenience, &productname; provides the class
  +      <p>As a convenience, &XercesCName; provides the class
           HandlerBase, which is a single class which is publicly derived
           from all the Handler classes. HandlerBase's default
           implementation of the handler callback methods is to do
  -        nothing. A convenient way to get started with &productname; is
  +        nothing. A convenient way to get started with &XercesCName; is
           to derive your own handler class from HandlerBase and override
           just those methods in HandlerBase which you are interested in
           customizing. This simple example shows how to create a handler
  @@ -113,7 +113,7 @@
           ]]></source>
   
         <p>The XMLCh and AttributeList types are supplied by
  -        &productname; and are documented in the include
  +        &XercesCName; and are documented in the include
           files. Examples of their usage appear in the source code to
           the sample applications.</p>
   
  @@ -133,16 +133,14 @@
       </s3>
   
       <s3 title="Accessing the API from application code">
  -      <table>
  -        <tr><td><source><![CDATA[
  +
  +<source><![CDATA[
   // C++
  -#include <dom/DOM.hpp>
  -        ]]></source></td></tr>
  -      <tr><td><source><![CDATA[
  +#include <dom/DOM.hpp>]]></source>
  +
  +<source><![CDATA[
   // Java
  -import org.w3c.dom.*
  -        ]]></source></td></tr>
  -    </table>
  +import org.w3c.dom.*]]></source>
   
         <p>The header file &lt;dom/DOM.hpp&gt; includes all the
           individual headers for the DOM API classes. </p>
  @@ -160,35 +158,28 @@
           conflict problem, but for the fact that many compilers do not
           yet support them.</p>
   
  -      <table>
  -        <tr><td><source><![CDATA[
  +<source><![CDATA[
   DOM_Document   myDocument;   // C++
   DOM_Node       aNode;
  -DOM_Text       someText;
  -        ]]></source></td></tr>
  +DOM_Text       someText;]]></source>
   
  -      <tr><td><source><![CDATA[
  +<source><![CDATA[
   Document       myDocument;   // Java
   Node           aNode;
  -Text           someText;
  -        ]]></source></td></tr>
  -    </table>
  +Text           someText;]]></source>
   
         <p>If you wish to use the Java class names in C++, then you need
           to typedef them in C++. This is not advisable for the general
           case - conflicts really do occur - but can be very useful when
           converting a body of existing Java code to C++.</p>
   
  -      <table>
  -        <tr><td><source><![CDATA[
  +<source><![CDATA[
   typedef DOM_Document  Document;
   typedef DOM_Node      Node;
   
   Document   myDocument;        // Now C++ usage is
                                 // indistinguishable from Java
  -Node       aNode;
  -        ]]></source></td></tr>
  -    </table>
  +Node       aNode;]]></source>
       </s3>
   
   
  @@ -201,24 +192,20 @@
           any explicit object deletion.</p>
   
         <p>Consider the following code snippets </p>
  -      <table>
  -        <tr><td><source><![CDATA[
  +
  +<source><![CDATA[
   // This is C++
   DOM_Node       aNode;
   aNode = someDocument.createElement("ElementName");
   DOM_Node docRootNode = someDoc.getDocumentElement();
  -docRootNode.AppendChild(aNode);
  -        ]]></source></td></tr>
  -    </table>
  -      <table>
  -        <tr><td><source><![CDATA[
  +docRootNode.AppendChild(aNode);]]></source>
  +
  +<source><![CDATA[
   // This is Java
   Node       aNode;
   aNode = someDocument.createElement("ElementName");
   Node docRootNode = someDoc.getDocumentElement();
  -docRootNode.AppendChild(aNode);
  -        ]]></source></td></tr>
  -    </table>
  +docRootNode.AppendChild(aNode);]]></source>
   
         <p>The Java and the C++ are identical on the surface, except for
           the class names, and this similarity remains true for most DOM
  @@ -357,28 +344,21 @@
           DOM_Element, for example.  The syntax for doing this in C++ is
           different from that in Java.</p>
   
  -      <table>
  -        <tr><td><source><![CDATA[
  +<source><![CDATA[
   // This is C++
   DOM_Node       aNode = someFunctionReturningNode();
  -DOM_Element    el = (Element &) aNode;
  -        ]]></source></td></tr>
  -    </table>
  +DOM_Element    el = (Element &) aNode;]]></source>
   
  -      <table>
  -        <tr><td><source><![CDATA[
  +<source><![CDATA[
   // This is Java
   Node       aNode = someFunctionReturningNode();
  -Element    el = (Element) aNode;
  -        ]]></source></td></tr>
  -    </table>
  +Element    el = (Element) aNode;]]></source>
   
         <p>The C++ cast is not type-safe; the Java cast is checked for
           compatible types at runtime.  If necessary, a type-check can
           be made in C++ using the node type information: </p>
   
  -      <table>
  -        <tr><td><source><![CDATA[
  +<source><![CDATA[
   // This is C++
   
   DOM_Node       aNode = someFunctionReturningNode();
  @@ -388,9 +368,7 @@
      el = (Element &) aNode;
   else
      // aNode does not refer to an element.
  -   // Do something to recover here.
  -        ]]></source></td></tr>
  -    </table>
  +   // Do something to recover here.]]></source>
   
       </s3>
   
  
  
  
  1.3       +9 -9      xml-site/xerces-c/readme.xml
  
  Index: readme.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/xerces-c/readme.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- readme.xml	1999/12/02 00:09:34	1.2
  +++ readme.xml	1999/12/02 01:00:44	1.3
  @@ -1,15 +1,15 @@
   <?xml version="1.0" standalone="no"?>
  -<!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  +<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
   
  -<s1 title="&fullproductname;">
  +<s1 title="&XercesCFullName;">
   
  -    <s2 title="&productname;++ Version &versionnumber;">
  +    <s2 title="&XercesCName;++ Version &XercesCVersion;">
   
  -<p>&productname; is a validating XML parser written in a portable subset of C++.
  -&productname; makes it easy to give your application
  +<p>&XercesCName; is a validating XML parser written in a portable subset of C++.
  +&XercesCName; makes it easy to give your application
   the ability to read and write XML data. A shared library is
   provided for parsing, generating, manipulating, and validating XML
  -documents. &productname; is faithful to the XML 1.0 recommendation
  +documents. &XercesCName; is faithful to the XML 1.0 recommendation
   and associated standards (DOM 1.0, SAX 1.0, Namespaces). It also provides
   early implementations of DOM Level 2.0, SAX version 2 and soon it will support
   XMLSchema. The parser provides high performance, modularity, and scalability.
  @@ -17,13 +17,13 @@
   portability, care has been taken to make minimal use of templates,
   no RTTI, no C++ namespaces, limited use of exceptions and minimal
   use of #ifdefs.</p>
  -<p>&productname; is fully compliant with Unicode 3.0 specification, making it
  +<p>&XercesCName; is fully compliant with Unicode 3.0 specification, making it
   the first Unicode 3.0 compliant application.</p>
   </s2>
   
  -    <s2 title="Applications of the &projectname; Parser">
  +    <s2 title="Applications of the &XercesCProjectName; Parser">
   
  -<p>&projectname; has rich generating and validating capabilities. The parser is used for:</p>
  +<p>&XercesCProjectName; has rich generating and validating capabilities. The parser is used for:</p>
   
   <ul>
       <li>Building XML-savvy Web servers</li>
  
  
  
  1.3       +3 -3      xml-site/xerces-c/releases.xml
  
  Index: releases.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/xerces-c/releases.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- releases.xml	1999/12/02 00:09:34	1.2
  +++ releases.xml	1999/12/02 01:00:44	1.3
  @@ -1,10 +1,10 @@
   <?xml version="1.0" standalone="no"?>
  -<!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  +<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
   
   <s1 title="Releases">
  -    <s2 title="&fullproductname; Version &versionnumber;: December 7, 1999">
  +    <s2 title="&XercesCFullName; Version &XercesCVersion;: December 7, 1999">
           <ul>
  -            <li>Released &productname; after incorporating ICU as a value-added plug-in.</li>
  +            <li>Released &XercesCName; after incorporating ICU as a value-added plug-in.</li>
               <li>Has bug fixes, better conformance, better speed and cleaner internal internal architecture</li>
               <li>Two additional samples added: PParse and StdInParse</li>
               <li>Experimental DOM Level 2 support</li>
  
  
  
  1.3       +53 -62    xml-site/xerces-c/samples.xml
  
  Index: samples.xml
  ===================================================================
  RCS file: /home/cvs/xml-site/xerces-c/samples.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- samples.xml	1999/12/02 00:09:34	1.2
  +++ samples.xml	1999/12/02 01:00:44	1.3
  @@ -1,10 +1,10 @@
   <?xml version="1.0" standalone="no"?>
  -<!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  +<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
   
   <s1 title="Samples">
   
       <s2 title="Building the Samples">
  -    <p>&productname; comes packaged with nine sample applications that
  +    <p>&XercesCName; comes packaged with nine sample applications that
       demonstrate salient features of the parser using simple
       applications written on top of the SAX and DOM APIs provided by
       the parser.</p>
  @@ -37,27 +37,25 @@
       </s2>
   
       <s2 title="SAXCount">
  -        <s3 title="What it does">
           <p>SAXCount is the simplest application that counts the elements and characters of
           a given XML file using the (event based) SAX API.</p>
  -        </s3>
   
           <s3 title="Building on Windows">
  -        <p>Load the &installdirname;-win32\samples\Projects\Win32\VC6\samples.dsw
  +        <p>Load the &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
           Microsoft Visual C++ workspace inside your MSVC IDE. Then
           build the project marked SAXCount.
           </p>
           </s3>
           <s3 title="Building on UNIX">
           <source>
  -        cd &installdirname;-linux/samples
  +        cd &XercesCInstallDir;-linux/samples
           ./runConfigure -p&lt;platform&gt; -c&lt;C_compiler&gt; -x&lt;C++_compiler&gt;
           cd SAXCount
           gmake
           </source>
           <p>
           This will create the object files in the current directory and the executable named
  -        SAXCount in '&installdirname;-linux/bin' directory.</p>
  +        SAXCount in '&XercesCInstallDir;-linux/bin' directory.</p>
   
           <p>To delete all the generated object files and executables, type</p>
           <source>
  @@ -78,7 +76,7 @@
             </source>
             <p>Here is a sample output from SAXCount</p>
             <source>
  -          cd &installdirname;-linux/samples/data
  +          cd &XercesCInstallDir;-linux/samples/data
             SAXCount -v personal.xml
             personal.xml: 60 ms (37 elems, 12 attrs, 134 spaces, 134 chars)
             </source>
  @@ -104,28 +102,26 @@
   
   
       <s2 title="SAXPrint">
  -        <s3 title="What it does">
           <p>SAXPrint uses the SAX APIs to parse an XML file and print it back. Notice that
                     the output of this file is not exactly the same as the input (in terms of white
                     spaces), but the output has the same information content as the input.</p>
  -        </s3>
   
           <s3 title="Building on Windows">
  -        <p>Load the &installdirname;-win32\samples\Projects\Win32\VC6\samples.dsw
  +        <p>Load the &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
           Microsoft Visual C++ workspace inside your MSVC IDE. Then
           build the project marked SAXPrint.
           </p>
           </s3>
           <s3 title="Building on UNIX">
           <source>
  -        cd &installdirname;-linux/samples
  +        cd &XercesCInstallDir;-linux/samples
           ./runConfigure -p&lt;platform&gt; -c&lt;C_compiler&gt; -x&lt;C++_compiler&gt;
           cd SAXPrint
           gmake
           </source>
           <p>
           This will create the object files in the current directory and the executable named
  -        SAXPrint in '&installdirname;-linux/bin' directory.</p>
  +        SAXPrint in '&XercesCInstallDir;-linux/bin' directory.</p>
   
           <p>To delete all the generated object files and executables, type</p>
           <source>
  @@ -146,7 +142,7 @@
             </source>
             <p>Here is a sample output from SAXPrint</p>
             <source>
  -          cd &installdirname;-linux/samples/data
  +          cd &XercesCInstallDir;-linux/samples/data
             SAXPrint -v personal.xml
   
             &lt;personnel>
  @@ -204,28 +200,26 @@
   
   
       <s2 title="DOMCount">
  -        <s3 title="What it does">
           <p>DOMCount uses the provided DOM API to parse an XML file, constructs the
                     DOM tree and walks through the tree counting the elements (using just one API
                     call).</p>
  -        </s3>
   
           <s3 title="Building on Windows">
  -        <p>Load the &installdirname;-win32\samples\Projects\Win32\VC6\samples.dsw
  +        <p>Load the &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
           Microsoft Visual C++ workspace inside your MSVC IDE. Then
           build the project marked DOMCount.
           </p>
           </s3>
           <s3 title="Building on UNIX">
           <source>
  -        cd &installdirname;-linux/samples
  +        cd &XercesCInstallDir;-linux/samples
           ./runConfigure -p&lt;platform&gt; -c&lt;C_compiler&gt; -x&lt;C++_compiler&gt;
           cd DOMCount
           gmake
           </source>
           <p>
           This will create the object files in the current directory and the executable named
  -        DOMCount in ' &installdirname;-linux/bin' directory.</p>
  +        DOMCount in ' &XercesCInstallDir;-linux/bin' directory.</p>
   
           <p>To delete all the generated object files and executables, type</p>
           <source>
  @@ -246,7 +240,7 @@
             </source>
             <p>Here is a sample output from DOMCount</p>
             <source>
  -          cd &installdirname;-linux/samples/data
  +          cd &XercesCInstallDir;-linux/samples/data
             DOMCount -v personal.xml
             personal.xml: 20 ms (37 elems)
             </source>
  @@ -265,28 +259,26 @@
   
   
       <s2 title="DOMPrint">
  -        <s3 title="What it does">
           <p>DOMPrint parses an XML file, constructs the DOM tree, and walks through the
                     tree printing each element. It thus dumps the XML back (output same as
                     SAXPrint).</p>
  -        </s3>
   
           <s3 title="Building on Windows">
  -        <p>Load the &installdirname;-win32\samples\Projects\Win32\VC6\samples.dsw
  +        <p>Load the &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
           Microsoft Visual C++ workspace inside your MSVC IDE. Then
           build the project marked DOMPrint.
           </p>
           </s3>
           <s3 title="Building on UNIX">
           <source>
  -        cd &installdirname;-linux/samples
  +        cd &XercesCInstallDir;-linux/samples
           ./runConfigure -p&lt;platform&gt; -c&lt;C_compiler&gt; -x&lt;C++_compiler&gt;
           cd DOMPrint
           gmake
           </source>
           <p>
           This will create the object files in the current directory and the executable named
  -        DOMPrint in ' &installdirname;-linux/bin' directory.</p>
  +        DOMPrint in ' &XercesCInstallDir;-linux/bin' directory.</p>
   
           <p>To delete all the generated object files and executables, type</p>
           <source>
  @@ -306,12 +298,12 @@
             <p>The -v option is used when you wish to use a validating parser. Here is a
                      sample output for DOMPrint when the validating parser is used: </p>
             <source>
  -               cd &installdirname;-linux/samples/data
  +               cd &XercesCInstallDir;-linux/samples/data
                  DOMPrint -v personal.xml
             </source>
             <p>Here is a sample output from DOMPrint</p>
             <source>
  -          cd &installdirname;-linux/samples/data
  +          cd &XercesCInstallDir;-linux/samples/data
             DOMPrint -v personal.xml
   
   
  @@ -373,27 +365,25 @@
   
   
       <s2 title="MemParse">
  -        <s3 title="What it does">
           <p>MemParse uses the Validating SAX Parser to parse a memory buffer containing
                     XML statements, and reports the number of elements and attributes found.</p>
  -        </s3>
   
           <s3 title="Building on Windows">
  -        <p>Load the &installdirname;-win32\samples\Projects\Win32\VC6\samples.dsw
  +        <p>Load the &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
           Microsoft Visual C++ workspace inside your MSVC IDE. Then
           build the project marked MemParse.
           </p>
           </s3>
           <s3 title="Building on UNIX">
           <source>
  -        cd &installdirname;-linux/samples
  +        cd &XercesCInstallDir;-linux/samples
           ./runConfigure -p&lt;platform&gt; -c&lt;C_compiler&gt; -x&lt;C++_compiler&gt;
           cd MemParse
           gmake
           </source>
           <p>
           This will create the object files in the current directory and the executable named
  -        MemParse in ' &installdirname;-linux/bin' directory.</p>
  +        MemParse in ' &XercesCInstallDir;-linux/bin' directory.</p>
   
           <p>To delete all the generated object files and executables, type</p>
           <source>
  @@ -413,7 +403,7 @@
   
             When invoked with a validating parser: </p>
             <source>
  -               cd &installdirname;-linux/samples/data
  +               cd &XercesCInstallDir;-linux/samples/data
                  MemParse -v
             </source>
             <p>The output is the following:</p>
  @@ -432,7 +422,7 @@
   
   
            &lt;company>
  -             &lt;product>&productname;&lt;/product>
  +             &lt;product>&XercesCName;&lt;/product>
                &lt;category idea='great'>XML Parsing Tools&lt;/category>
                &lt;developedAt>
                  IBM Center for Java Technology, Silicon Valley, Cupertino, CA
  @@ -451,28 +441,26 @@
   
   
       <s2 title="Redirect">
  -        <s3 title="What it does">
           <p>Redirect uses the SAX EntityResolver handler to redirect the input stream for
                     external entities. It installs an entity resolver, traps the call to the external DTD
                     file and redirects it to another specific file which contains the actual DTD.</p>
  -        </s3>
   
           <s3 title="Building on Windows">
  -        <p>Load the &installdirname;-win32\samples\Projects\Win32\VC6\samples.dsw
  +        <p>Load the &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
           Microsoft Visual C++ workspace inside your MSVC IDE. Then
           build the project marked Redirect.
           </p>
           </s3>
           <s3 title="Building on UNIX">
           <source>
  -        cd &installdirname;-linux/samples
  +        cd &XercesCInstallDir;-linux/samples
           ./runConfigure -p&lt;platform&gt; -c&lt;C_compiler&gt; -x&lt;C++_compiler&gt;
           cd Redirect
           gmake
           </source>
           <p>
           This will create the object files in the current directory and the executable named
  -        Redirect in '&installdirname;-linux/bin' directory.</p>
  +        Redirect in '&XercesCInstallDir;-linux/bin' directory.</p>
   
           <p>To delete all the generated object files and executables, type</p>
           <source>
  @@ -496,12 +484,12 @@
   
                      <p>When invoked as follows:</p>
             <source>
  -               cd &installdirname;-linux/samples/data
  +               cd &XercesCInstallDir;-linux/samples/data
                  Redirect -v personal.xml
             </source>
             <p>The output is the following:</p>
             <source>
  -          cd &installdirname;-linux/samples/data
  +          cd &XercesCInstallDir;-linux/samples/data
             Redirect -v personal.xml
             personal.xml: 30 ms (37 elems, 12 attrs, 134 spaces, 134 chars)
             </source>
  @@ -527,30 +515,37 @@
   
   
       <s2 title="PParse">
  -        <s3 title="What it does">
  -        <p>Demonstrates progressive parsing.
  -        </p>
  -          <p>In this example, the programmer doesn't have to depend upon throwing an exception to terminate the parsing operation. Calling parseFirst() will cause the DTD to be parsed (both internal and external subsets) and any pre-content, i.e. everything up to but not including the root element. Subsequent calls to parseNext() will cause one more piece of markup to be parsed, and spit out from the core scanning code to the parser. You can quit the parse any time by just not calling parseNext() anymore and breaking out of the loop. When you call parseNext() and the end of the root element is the next piece of markup, the parser will continue on to the end of the file and return false, to let you know that the parse is done.
  +        <p>Demonstrates progressive parsing.</p>
  +        <p>
  +           In this example, the programmer doesn't have to depend upon throwing
  +            an exception to terminate the parsing operation. Calling parseFirst() will
  +            cause the DTD to be parsed (both internal and external subsets) and any
  +            pre-content, i.e. everything up to but not including the root element.
  +            Subsequent calls to parseNext() will cause one more piece of markup to
  +            be parsed, and spit out from the core scanning code to the parser. You
  +            can quit the parse any time by just not calling parseNext() anymore
  +            and breaking out of the loop. When you call parseNext() and the end
  +            of the root element is the next piece of markup, the parser will 
  +            continue on to the end of the file and return false, to let you 
  +            know that the parse is done.
             </p>
   
  -        </s3>
  -
           <s3 title="Building on Windows">
  -        <p>Load the &installdirname;win32\samples\Projects\Win32\VC6\samples.dsw
  +        <p>Load the &XercesCInstallDir;win32\samples\Projects\Win32\VC6\samples.dsw
           Microsoft Visual C++ workspace inside your MSVC IDE. Then
           build the project marked PParse.
           </p>
           </s3>
           <s3 title="Building on UNIX">
           <source>
  -        cd &installdirname;-linux/samples
  +        cd &XercesCInstallDir;-linux/samples
           ./runConfigure -p&lt;platform&gt; -c&lt;C_compiler&gt; -x&lt;C++_compiler&gt;
           cd PParse
           gmake
           </source>
           <p>
           This will create the object files in the current directory and the executable named
  -        PParse in ' &installdirname;-linux/bin' directory.</p>
  +        PParse in ' &XercesCInstallDir;-linux/bin' directory.</p>
   
           <p>To delete all the generated object files and executables, type</p>
           <source>
  @@ -577,27 +572,25 @@
   
   
       <s2 title="StdInParse">
  -        <s3 title="What it does">
           <p>Demonstrates streaming XML data from the standard input.
           </p>
  -        </s3>
   
           <s3 title="Building on Windows">
  -        <p>Load the &installdirname;-win32\samples\Projects\Win32\VC6\samples.dsw
  +        <p>Load the &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
           Microsoft Visual C++ workspace inside your MSVC IDE. Then
           build the project marked StdInParse.
           </p>
           </s3>
           <s3 title="Building on UNIX">
           <source>
  -        cd &installdirname;-linux/samples
  +        cd &XercesCInstallDir;-linux/samples
           ./runConfigure -p&lt;platform&gt; -c&lt;C_compiler&gt; -x&lt;C++_compiler&gt;
           cd StdInParse
           gmake
           </source>
           <p>
           This will create the object files in the current directory and the executable named
  -        StdInParse in ' &installdirname;-linux/bin' directory.</p>
  +        StdInParse in ' &XercesCInstallDir;-linux/bin' directory.</p>
   
           <p>To delete all the generated object files and executables, type</p>
           <source>
  @@ -614,7 +607,7 @@
             </source>
             <p>Here is a sample output from StdInParse</p>
             <source>
  -          cd &installdirname;-linux/samples/data
  +          cd &XercesCInstallDir;-linux/samples/data
             StdInParse &lt; personal.xml
             personal.xml: 60 ms (37 elems, 12 attrs, 0 spaces, 268 chars)
             </source>
  @@ -628,27 +621,25 @@
   
   
       <s2 title="EnumVal">
  -        <s3 title="What it does">
           <p>Shows how to enumerate the markup decls in a DTD Validator.
           </p>
  -        </s3>
   
           <s3 title="Building on Windows">
  -        <p>Load the &installdirname;-win32\samples\Projects\Win32\VC6\samples.dsw
  +        <p>Load the &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
           Microsoft Visual C++ workspace inside your MSVC IDE. Then
           build the project marked EnumVal.
           </p>
           </s3>
           <s3 title="Building on UNIX">
           <source>
  -        cd &installdirname;-linux/samples
  +        cd &XercesCInstallDir;-linux/samples
           ./runConfigure -p&lt;platform&gt; -c&lt;C_compiler&gt; -x&lt;C++_compiler&gt;
           cd EnumVal
           gmake
           </source>
           <p>
           This will create the object files in the current directory and the executable named
  -        EnumVal in ' &installdirname;-linux/bin' directory.</p>
  +        EnumVal in ' &XercesCInstallDir;-linux/bin' directory.</p>
   
           <p>To delete all the generated object files and executables, type</p>
           <source>
  @@ -665,7 +656,7 @@
             </source>
             <p>Here is a sample output from EnumVal</p>
             <source>
  -cd &installdirname;-linux/samples/data
  +cd &XercesCInstallDir;-linux/samples/data
   EnumVal personal.xml
   
   ELEMENTS:
  
  
  

Mime
View raw message