xml-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From p...@hyperreal.org
Subject cvs commit: xml-0.0/docs/xerces-p readme.xml
Date Mon, 15 Nov 1999 21:45:44 GMT
pier        99/11/15 13:45:38

  Added:       docs     all.bat cocoon.bat cocoon.xml fop.bat fop.xml
                        website.bat website.xml xalan.bat xalan.xml
                        xerces-c.bat xerces-c.xml xerces-j.bat xerces-j.xml
                        xerces-p.bat xerces-p.xml
               docs/cocoon readme.xml
               docs/dtd blocks.ent book.dtd changes.dtd characters.ent
                        document.dtd faqs.dtd links.ent markup.ent
               docs/fop readme.xml
               docs/resources bottom.gif button-1.gif button-2.gif
                        button-3.gif button-a-bk.gif button-a.gif
                        button-asf-hi.gif button-asf-lo.gif button-b.gif
                        button-w3c-hi.gif button-w3c-lo.gif
                        button-xml-hi.gif button-xml-lo.gif close.gif
                        dot.gif join.gif line.gif logo.gif right.gif
                        script.js separator.gif style.css title.gif
               docs/stylesheets book2project.xsl context2document.xsl
                        context2faqs.xsl document2button1.xsl
                        document2button2.xsl document2button3.xsl
                        document2html.xsl document2title.xsl
                        faq2document1.xsl faq2document2.xsl
                        faqs2document1.xsl faqs2document2.xsl
                        group2title.xsl
               docs/website ack.xml communication.xml contact.xml cvs.xml
                        decisions.xml guidelines.xml index.xml legal.xml
                        library.xml mail.xml management.xml mission.xml
                        news.xml overview.xml roles.xml source.xml
                        whoweare.xml
               docs/xalan readme.xml
               docs/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
               docs/xerces-j api.xml caveats.xml faq-build.xml
                        faq-common.xml faq-general-doc.xml faq-general.xml
                        faq-write.xml features.xml feedback.xml install.xml
                        properties.xml readme.xml releases.xml
                        sam-iterator.xml sam-tree.xml samples.xml
                        schema.xml
               docs/xerces-p readme.xml
  Log:
  XML.APACHE.ORG documentation source primary checkin.
  
  Revision  Changes    Path
  1.1                  xml-0.0/docs/all.bat
  
  Index: all.bat
  ===================================================================
  @echo off
  call website.bat
  call xerces-j.bat
  call xerces-c.bat
  call xerces-p.bat
  call xalan.bat
  call fop.bat
  call cocoon.bat
  
  
  
  1.1                  xml-0.0/docs/cocoon.bat
  
  Index: cocoon.bat
  ===================================================================
  @echo off
  java org.apache.stylebook.StyleBook "target.dir=c:\targets\cocoon" cocoon.xml
  
  
  
  1.1                  xml-0.0/docs/cocoon.xml
  
  Index: cocoon.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE book SYSTEM "dtd/book.dtd">
  
  <?xml-stylesheet type="text/xsl" href="stylesheets/book2project.xsl"?>
  
  <book title="Cocoon documentation" copyright="1999 The Apache Software Foundation">
  
  <extern  id="home"      href="../index.html"       label="Home"                     />
  <separator/>
  <chapter  id="index"       label="Readme"       href="cocoon/readme.xml"       type="document"/>
  </book>
  
  
  
  1.1                  xml-0.0/docs/fop.bat
  
  Index: fop.bat
  ===================================================================
  @echo off
  java org.apache.stylebook.StyleBook "target.dir=c:\targets\fop" fop.xml
  
  
  
  1.1                  xml-0.0/docs/fop.xml
  
  Index: fop.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE book SYSTEM "dtd/book.dtd">
  
  <?xml-stylesheet type="text/xsl" href="stylesheets/book2project.xsl"?>
  
  <book title="FOP XSL-FO documentation" copyright="1999 The Apache Software Foundation">
  
  <extern  id="home"      href="../index.html"       label="Home"                     />
  <separator/>
  <chapter  id="index"       label="Readme"       href="fop/readme.xml"       type="document"/>
  </book>
  
  
  
  1.1                  xml-0.0/docs/website.bat
  
  Index: website.bat
  ===================================================================
  @echo off
  java org.apache.stylebook.StyleBook "target.dir=c:\targets" website.xml
  
  
  
  1.1                  xml-0.0/docs/website.xml
  
  Index: website.xml
  ===================================================================
  <?xml version="1.0"?>
  
  <?xml-stylesheet type="text/xsl" href="stylesheets/book2project.xsl"?>
  
  <book>
    <chapter id="index"         href="website/index.xml"         label="Welcome"      type="document"/>
    <chapter id="news"          href="website/news.xml"          label="News"         type="document"/>
    <chapter id="mission"       href="website/mission.xml"       label="Mission"      type="document"/>
    <chapter id="guidelines"    href="website/guidelines.xml"    label="Guidelines"   type="document"/>
    <hidden  id="roles"         href="website/roles.xml"                              type="document"/>
    <hidden  id="communication" href="website/communication.xml"                      type="document"/>
    <hidden  id="decisions"     href="website/decisions.xml"                          type="document"/>
    <hidden  id="source"        href="website/source.xml"                             type="document"/>
    <hidden  id="management"    href="website/management.xml"                         type="document"/>
    <separator/>
    <extern  id="xerces-j"      href="xerces-j/index.html"       label="Xerces Java"                 />
    <extern  id="xerces-c"      href="xerces-c/index.html"       label="Xerces C++"                  />
    <extern  id="xerces-p"      href="xerces-p/index.html"       label="Xerces Perl"                 />
    <extern  id="xalan"         href="xalan/index.html"          label="Xalan XSLT"                  />
    <extern  id="fop"           href="fop/index.html"            label="FOP"                         />
    <extern  id="cocoon"        href="cocoon/index.html"         label="Cocoon"                      />
    <separator/>
    <extern  id="download"      href="dist/"                     label="Downloads"                   />
    <separator/>
    <chapter id="overview"      href="website/overview.xml"      label="Get Involved"  type="document"/>
    <chapter id="cvs"           href="website/cvs.xml"           label="Repositories"  type="document"/>
    <chapter id="mail"          href="website/mail.xml"          label="Mailing Lists" type="document"/>
    <chapter id="library"       href="website/library.xml"       label="Reference"     type="document"/>
    <separator/>
    <chapter id="whoweare"      href="website/whoweare.xml"      label="Who We Are"   type="document"/>
    <chapter id="ack"           href="website/ack.xml"           label="Credits"      type="document"/>
    <separator/>
    <chapter id="legal"         href="website/legal.xml"         label="Legal Stuff"  type="document"/>
    <chapter id="contact"       href="website/contact.xml"       label="Contact Info" type="document"/>
  </book>
  
  
  
  1.1                  xml-0.0/docs/xalan.bat
  
  Index: xalan.bat
  ===================================================================
  @echo off
  java org.apache.stylebook.StyleBook "target.dir=c:\targets\xalan" xalan.xml
  
  
  
  1.1                  xml-0.0/docs/xalan.xml
  
  Index: xalan.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE book SYSTEM "dtd/book.dtd">
  
  <?xml-stylesheet type="text/xsl" href="stylesheets/book2project.xsl"?>
  
  <book title="Xalan documentation" copyright="1999 The Apache Software Foundation">
  
  <extern  id="home"      href="../index.html"       label="Home"                     />
  <separator/>
  <chapter  id="index"       label="Readme"       href="xalan/readme.xml"       type="document"/>
  </book>
  
  
  
  1.1                  xml-0.0/docs/xerces-c.bat
  
  Index: xerces-c.bat
  ===================================================================
  @echo off
  java org.apache.stylebook.StyleBook "target.dir=c:\targets\xerces-c" xerces-c.xml
  
  
  
  1.1                  xml-0.0/docs/xerces-c.xml
  
  Index: xerces-c.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE book SYSTEM "dtd/book.dtd">
  
  <?xml-stylesheet type="text/xsl" href="stylesheets/book2project.xsl"?>
  
  <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>
  
  
  
  1.1                  xml-0.0/docs/xerces-j.bat
  
  Index: xerces-j.bat
  ===================================================================
  @echo off
  java org.apache.stylebook.StyleBook "target.dir=c:\targets\xerces-j" xerces-j.xml
  
  
  
  1.1                  xml-0.0/docs/xerces-j.xml
  
  Index: xerces-j.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE book SYSTEM "dtd/book.dtd">
  
  <?xml-stylesheet type="text/xsl" href="stylesheets/book2project.xsl"?>
  
  <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-j/readme.xml"       type="document"/>
  <chapter  id="install"     label="Installation" href="xerces-j/install.xml"      type="document"/>
  <separator/>
  <chapter  id="api"         label="API Docs"     href="xerces-j/api.xml"          type="document"/>
  <chapter  id="samples"     label="Samples"      href="xerces-j/samples.xml"      type="document"/>
  <hidden   id="iterator"                         href="xerces-j/sam-iterator.xml" type="document"/>
  <hidden   id="tree"                             href="xerces-j/sam-tree.xml"     type="document"/>
  <chapter  id="schema"      label="Schema"       href="xerces-j/schema.xml"       type="document"/>
  <separator/>
  <chapter  id="properties"  label="Properties"   href="xerces-j/properties.xml"   type="document"/>
  <chapter  id="features"    label="Features"     href="xerces-j/features.xml"     type="document"/>
  <group    id="faqs"        label="FAQs"                                          type="faqs">
    <hidden id="faq-general"                      href="xerces-j/faq-general.xml"  type="faq"/>
    <hidden id="faq-build"                        href="xerces-j/faq-build.xml"    type="faq"/>
    <hidden id="faq-write"                        href="xerces-j/faq-write.xml"    type="faq"/>
    <hidden id="faq-common"                       href="xerces-j/faq-common.xml"   type="faq"/>
  </group>
  <separator/>
  <chapter  id="releases"    label="Releases"     href="xerces-j/releases.xml"     type="document"/>
  <chapter  id="caveats"     label="Caveats"      href="xerces-j/caveats.xml"      type="document"/>
  <chapter  id="feedback"    label="Feedback"     href="xerces-j/feedback.xml"     type="document"/>
  
  </book>
  
  
  
  1.1                  xml-0.0/docs/xerces-p.bat
  
  Index: xerces-p.bat
  ===================================================================
  @echo off
  java org.apache.stylebook.StyleBook "target.dir=c:\targets\xerces-p" xerces-p.xml
  
  
  
  1.1                  xml-0.0/docs/xerces-p.xml
  
  Index: xerces-p.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE book SYSTEM "dtd/book.dtd">
  
  <?xml-stylesheet type="text/xsl" href="stylesheets/book2project.xsl"?>
  
  <book title="Xerces-P documentation" copyright="1999 The Apache Software Foundation">
  
  <extern  id="home"      href="../index.html"       label="Home"                     />
  <separator/>
  <chapter  id="index"       label="Readme"       href="xerces-p/readme.xml"       type="document"/>
  </book>
  
  
  
  1.1                  xml-0.0/docs/cocoon/readme.xml
  
  Index: readme.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Cocoon">
    <s2 title="Cocoon">
      <p>
        Cocoon is a powerful framework for XML web publishing which brings a whole 
        new world of abstraction and ease to consolidated web site creation and
        management based on the XML paradigm and related technologies.
      </p>
      <p>
        Additional documentation to be provided soon. Watch this space.
      </p>
    </s2>
  </s1>
  
  
  1.1                  xml-0.0/docs/dtd/blocks.ent
  
  Index: blocks.ent
  ===================================================================
  <?xml encoding='US-ASCII'?>
  
  <!-- BLOCKS ENTITY -->
  
  <!ENTITY % blocks "p|note|ul|ol|table|source|anchor">
  
  <!ENTITY % markupEntity SYSTEM "markup.ent">
  <!ENTITY % linksEntity SYSTEM "links.ent">
  %markupEntity;
  %linksEntity;
  
  <!ENTITY % content "(#PCDATA|%markup;|%links;)*">
  
  <!ELEMENT p %content;>
  <!ELEMENT note %content;>
  <!ELEMENT ul (li|ol|ul)+>
  <!ELEMENT ol (li|ol|ul)+>
  <!ELEMENT table (tr)+>
  <!ELEMENT source (#PCDATA)>
  
  <!ELEMENT li %content;>
  
  <!ELEMENT tr (tn*,(th|td)+)>
  
  <!ELEMENT tn EMPTY>
  <!ATTLIST tn colspan CDATA #IMPLIED
               rowspan CDATA #IMPLIED
               width   CDATA #IMPLIED>
  
  <!ELEMENT th %content;>
  <!ATTLIST th colspan CDATA #IMPLIED
               rowspan CDATA #IMPLIED
               width   CDATA #IMPLIED>
  
  <!ELEMENT td %content;>
  <!ATTLIST td colspan CDATA #IMPLIED
               rowspan CDATA #IMPLIED
               width   CDATA #IMPLIED>
  
  
  
  1.1                  xml-0.0/docs/dtd/book.dtd
  
  Index: book.dtd
  ===================================================================
  <?xml encoding='US-ASCII'?>
  
  <!-- STYLEBOOK BOOK DTD -->
  
  <!ELEMENT book ((chapter|group)+,(resource)*)>
  <!ATTLIST book title     CDATA #REQUIRED
                 author    CDATA #IMPLIED
                 copyright CDATA #IMPLIED
                 date      CDATA #IMPLIED>
                 
  
  <!ELEMENT chapter EMPTY>
  <!ATTLIST chapter id    ID    #REQUIRED
                    href  CDATA #REQUIRED
                    label CDATA #REQUIRED
                    type  (document|faqs|changes|options) "document">
  
  <!ELEMENT group (chapter)+>
  <!ATTLIST group id    ID    #IMPLIED
                  label CDATA #REQUIRED
                  type  (group|faqs) "group">
                  
  <!ELEMENT resource EMPTY>
  <!ATTLIST resource id      ID    #REQUIRED
                     href    CDATA #REQUIRED
                     content CDATA #REQUIRED>
  
  
  
  1.1                  xml-0.0/docs/dtd/changes.dtd
  
  Index: changes.dtd
  ===================================================================
  <?xml encoding='US-ASCII'?>
  
  <!-- STYLEBOOK CHANGES DTD -->
  
  <!ENTITY % markupEntity SYSTEM "markup.ent">
  <!ENTITY % linksEntity SYSTEM "links.ent">
  %markupEntity;
  %linksEntity;
  
  <!ENTITY % content "(#PCDATA|%markup;|%links;)*">
  
  <!ELEMENT changes (release)+>
  <!ATTLIST changes title CDATA #IMPLIED>
  
  <!ELEMENT release (features,fixes)|(features)|(fixes)>
  <!ATTLIST release date CDATA #IMPLIED
            release vers CDATA #IMPLIED>
  
  <!ELEMENT features (feat)+>
  <!ELEMENT fixes (fix)+>
  
  <!ELEMENT feat %content;>
  <!ELEMENT fix %content;>
  
  
  
  1.1                  xml-0.0/docs/dtd/characters.ent
  
  Index: characters.ent
  ===================================================================
  <!-- Portions (C) International Organization for Standardization 1986
       Permission to copy in any form is granted for use with
       conforming SGML systems and applications as defined in
       ISO 8879, provided this notice is included in all copies.
  -->
  <!-- Character entity set. Typical invocation:
       <!ENTITY % HTMLlat1 PUBLIC
         "-//W3C//ENTITIES Latin 1//EN//HTML">
       %HTMLlat1;
  -->
  
  <!-- Latin A -->
  <!ENTITY nbsp     "&#160;">  <!-- U+00A0 ISOnum    - no-break space = non-breaking space                                   -->
  <!ENTITY iexcl    "&#161;">  <!-- U+00A1 ISOnum    - inverted exclamation mark                                             -->
  <!ENTITY cent     "&#162;">  <!-- U+00A2 ISOnum    - cent sign                                                             -->
  <!ENTITY pound    "&#163;">  <!-- U+00A3 ISOnum    - pound sign                                                            -->
  <!ENTITY curren   "&#164;">  <!-- U+00A4 ISOnum    - currency sign                                                         -->
  <!ENTITY yen      "&#165;">  <!-- U+00A5 ISOnum    - yen sign = yuan sign                                                  -->
  <!ENTITY brvbar   "&#166;">  <!-- U+00A6 ISOnum    - broken bar = broken vertical bar                                      -->
  <!ENTITY sect     "&#167;">  <!-- U+00A7 ISOnum    - section sign                                                          -->
  <!ENTITY uml      "&#168;">  <!-- U+00A8 ISOdia    - diaeresis = spacing diaeresis                                         -->
  <!ENTITY copy     "&#169;">  <!-- U+00A9 ISOnum    - copyright sign                                                        -->
  <!ENTITY ordf     "&#170;">  <!-- U+00AA ISOnum    - feminine ordinal indicator                                            -->
  <!ENTITY laquo    "&#171;">  <!-- U+00AB ISOnum    - left-pointing double angle quotation mark = left pointing guillemet   -->
  <!ENTITY not      "&#172;">  <!-- U+00AC ISOnum    - not sign                                                              -->
  <!ENTITY shy      "&#173;">  <!-- U+00AD ISOnum    - soft hyphen = discretionary hyphen                                    -->
  <!ENTITY reg      "&#174;">  <!-- U+00AE ISOnum    - registered sign = registered trade mark sign                          -->
  <!ENTITY macr     "&#175;">  <!-- U+00AF ISOdia    - macron = spacing macron = overline = APL overbar                      -->
  <!ENTITY deg      "&#176;">  <!-- U+00B0 ISOnum    - degree sign                                                           -->
  <!ENTITY plusmn   "&#177;">  <!-- U+00B1 ISOnum    - plus-minus sign = plus-or-minus sign                                  -->
  <!ENTITY sup2     "&#178;">  <!-- U+00B2 ISOnum    - superscript two = superscript digit two = squared                     -->
  <!ENTITY sup3     "&#179;">  <!-- U+00B3 ISOnum    - superscript three = superscript digit three = cubed                   -->
  <!ENTITY acute    "&#180;">  <!-- U+00B4 ISOdia    - acute accent = spacing acute                                          -->
  <!ENTITY micro    "&#181;">  <!-- U+00B5 ISOnum    - micro sign                                                            -->
  <!ENTITY para     "&#182;">  <!-- U+00B6 ISOnum    - pilcrow sign = paragraph sign                                         -->
  <!ENTITY middot   "&#183;">  <!-- U+00B7 ISOnum    - middle dot = Georgian comma = Greek middle dot                        -->
  <!ENTITY cedil    "&#184;">  <!-- U+00B8 ISOdia    - cedilla = spacing cedilla                                             -->
  <!ENTITY sup1     "&#185;">  <!-- U+00B9 ISOnum    - superscript one = superscript digit one                               -->
  <!ENTITY ordm     "&#186;">  <!-- U+00BA ISOnum    - masculine ordinal indicator                                           -->
  <!ENTITY raquo    "&#187;">  <!-- U+00BB ISOnum    - right-pointing double angle quotation mark = right pointing guillemet -->
  <!ENTITY frac14   "&#188;">  <!-- U+00BC ISOnum    - vulgar fraction one quarter = fraction one quarter                    -->
  <!ENTITY frac12   "&#189;">  <!-- U+00BD ISOnum    - vulgar fraction one half = fraction one half                          -->
  <!ENTITY frac34   "&#190;">  <!-- U+00BE ISOnum    - vulgar fraction three quarters = fraction three quarters              -->
  <!ENTITY iquest   "&#191;">  <!-- U+00BF ISOnum    - inverted question mark = turned question mark                         -->
  <!ENTITY Agrave   "&#192;">  <!-- U+00C0 ISOlat1   - latin capital letter A with grave = latin capital letter A grave      -->
  <!ENTITY Aacute   "&#193;">  <!-- U+00C1 ISOlat1   - latin capital letter A with acute                                     -->
  <!ENTITY Acirc    "&#194;">  <!-- U+00C2 ISOlat1   - latin capital letter A with circumflex                                -->
  <!ENTITY Atilde   "&#195;">  <!-- U+00C3 ISOlat1   - latin capital letter A with tilde                                     -->
  <!ENTITY Auml     "&#196;">  <!-- U+00C4 ISOlat1   - latin capital letter A with diaeresis                                 -->
  <!ENTITY Aring    "&#197;">  <!-- U+00C5 ISOlat1   - latin capital letter A with ring above = latin capital letter A ring  -->
  <!ENTITY AElig    "&#198;">  <!-- U+00C6 ISOlat1   - latin capital letter AE = latin capital ligature AE                   -->
  <!ENTITY Ccedil   "&#199;">  <!-- U+00C7 ISOlat1   - latin capital letter C with cedilla                                   -->
  <!ENTITY Egrave   "&#200;">  <!-- U+00C8 ISOlat1   - latin capital letter E with grave                                     -->
  <!ENTITY Eacute   "&#201;">  <!-- U+00C9 ISOlat1   - latin capital letter E with acute                                     -->
  <!ENTITY Ecirc    "&#202;">  <!-- U+00CA ISOlat1   - latin capital letter E with circumflex                                -->
  <!ENTITY Euml     "&#203;">  <!-- U+00CB ISOlat1   - latin capital letter E with diaeresis                                 -->
  <!ENTITY Igrave   "&#204;">  <!-- U+00CC ISOlat1   - latin capital letter I with grave                                     -->
  <!ENTITY Iacute   "&#205;">  <!-- U+00CD ISOlat1   - latin capital letter I with acute                                     -->
  <!ENTITY Icirc    "&#206;">  <!-- U+00CE ISOlat1   - latin capital letter I with circumflex                                -->
  <!ENTITY Iuml     "&#207;">  <!-- U+00CF ISOlat1   - latin capital letter I with diaeresis                                 -->
  <!ENTITY ETH      "&#208;">  <!-- U+00D0 ISOlat1   - latin capital letter ETH                                              -->
  <!ENTITY Ntilde   "&#209;">  <!-- U+00D1 ISOlat1   - latin capital letter N with tilde                                     -->
  <!ENTITY Ograve   "&#210;">  <!-- U+00D2 ISOlat1   - latin capital letter O with grave                                     -->
  <!ENTITY Oacute   "&#211;">  <!-- U+00D3 ISOlat1   - latin capital letter O with acute                                     -->
  <!ENTITY Ocirc    "&#212;">  <!-- U+00D4 ISOlat1   - latin capital letter O with circumflex                                -->
  <!ENTITY Otilde   "&#213;">  <!-- U+00D5 ISOlat1   - latin capital letter O with tilde                                     -->
  <!ENTITY Ouml     "&#214;">  <!-- U+00D6 ISOlat1   - latin capital letter O with diaeresis                                 -->
  <!ENTITY times    "&#215;">  <!-- U+00D7 ISOnum    - multiplication sign                                                   -->
  <!ENTITY Oslash   "&#216;">  <!-- U+00D8 ISOlat1   - latin capital letter O with stroke = latin capital letter O slash     -->
  <!ENTITY Ugrave   "&#217;">  <!-- U+00D9 ISOlat1   - latin capital letter U with grave                                     -->
  <!ENTITY Uacute   "&#218;">  <!-- U+00DA ISOlat1   - latin capital letter U with acute                                     -->
  <!ENTITY Ucirc    "&#219;">  <!-- U+00DB ISOlat1   - latin capital letter U with circumflex                                -->
  <!ENTITY Uuml     "&#220;">  <!-- U+00DC ISOlat1   - latin capital letter U with diaeresis                                 -->
  <!ENTITY Yacute   "&#221;">  <!-- U+00DD ISOlat1   - latin capital letter Y with acute                                     -->
  <!ENTITY THORN    "&#222;">  <!-- U+00DE ISOlat1   - latin capital letter THORN                                            -->
  <!ENTITY szlig    "&#223;">  <!-- U+00DF ISOlat1   - latin small letter sharp s = ess-zed                                  -->
  <!ENTITY agrave   "&#224;">  <!-- U+00E0 ISOlat1   - latin small letter a with grave = latin small letter a grave          -->
  <!ENTITY aacute   "&#225;">  <!-- U+00E1 ISOlat1   - latin small letter a with acute                                       -->
  <!ENTITY acirc    "&#226;">  <!-- U+00E2 ISOlat1   - latin small letter a with circumflex                                  -->
  <!ENTITY atilde   "&#227;">  <!-- U+00E3 ISOlat1   - latin small letter a with tilde                                       -->
  <!ENTITY auml     "&#228;">  <!-- U+00E4 ISOlat1   - latin small letter a with diaeresis                                   -->
  <!ENTITY aring    "&#229;">  <!-- U+00E5 ISOlat1   - latin small letter a with ring above = latin small letter a ring      -->
  <!ENTITY aelig    "&#230;">  <!-- U+00E6 ISOlat1   - latin small letter ae = latin small ligature ae                       -->
  <!ENTITY ccedil   "&#231;">  <!-- U+00E7 ISOlat1   - latin small letter c with cedilla                                     -->
  <!ENTITY egrave   "&#232;">  <!-- U+00E8 ISOlat1   - latin small letter e with grave                                       -->
  <!ENTITY eacute   "&#233;">  <!-- U+00E9 ISOlat1   - latin small letter e with acute                                       -->
  <!ENTITY ecirc    "&#234;">  <!-- U+00EA ISOlat1   - latin small letter e with circumflex                                  -->
  <!ENTITY euml     "&#235;">  <!-- U+00EB ISOlat1   - latin small letter e with diaeresis                                   -->
  <!ENTITY igrave   "&#236;">  <!-- U+00EC ISOlat1   - latin small letter i with grave                                       -->
  <!ENTITY iacute   "&#237;">  <!-- U+00ED ISOlat1   - latin small letter i with acute                                       -->
  <!ENTITY icirc    "&#238;">  <!-- U+00EE ISOlat1   - latin small letter i with circumflex                                  -->
  <!ENTITY iuml     "&#239;">  <!-- U+00EF ISOlat1   - latin small letter i with diaeresis                                   -->
  <!ENTITY eth      "&#240;">  <!-- U+00F0 ISOlat1   - latin small letter eth                                                -->
  <!ENTITY ntilde   "&#241;">  <!-- U+00F1 ISOlat1   - latin small letter n with tilde                                       -->
  <!ENTITY ograve   "&#242;">  <!-- U+00F2 ISOlat1   - latin small letter o with grave                                       -->
  <!ENTITY oacute   "&#243;">  <!-- U+00F3 ISOlat1   - latin small letter o with acute                                       -->
  <!ENTITY ocirc    "&#244;">  <!-- U+00F4 ISOlat1   - latin small letter o with circumflex                                  -->
  <!ENTITY otilde   "&#245;">  <!-- U+00F5 ISOlat1   - latin small letter o with tilde                                       -->
  <!ENTITY ouml     "&#246;">  <!-- U+00F6 ISOlat1   - latin small letter o with diaeresis                                   -->
  <!ENTITY divide   "&#247;">  <!-- U+00F7 ISOnum    - division sign                                                         -->
  <!ENTITY oslash   "&#248;">  <!-- U+00F8 ISOlat1   - latin small letter o with stroke = latin small letter o slash         -->
  <!ENTITY ugrave   "&#249;">  <!-- U+00F9 ISOlat1   - latin small letter u with grave                                       -->
  <!ENTITY uacute   "&#250;">  <!-- U+00FA ISOlat1   - latin small letter u with acute                                       -->
  <!ENTITY ucirc    "&#251;">  <!-- U+00FB ISOlat1   - latin small letter u with circumflex                                  -->
  <!ENTITY uuml     "&#252;">  <!-- U+00FC ISOlat1   - latin small letter u with diaeresis                                   -->
  <!ENTITY yacute   "&#253;">  <!-- U+00FD ISOlat1   - latin small letter y with acute                                       -->
  <!ENTITY thorn    "&#254;">  <!-- U+00FE ISOlat1   - latin small letter thorn                                              -->
  <!ENTITY yuml     "&#255;">  <!-- U+00FF ISOlat1   - latin small letter y with diaeresis                                   -->
  
  
  <!-- C0 Controls and Basic Latin -->
  <!ENTITY quot     "&#34;">   <!-- U+0022 ISOnum    - quotation mark = APL quote                                            -->
  <!ENTITY amp      "&#38;">   <!-- U+0026 ISOnum    - ampersand                                                             -->
  <!ENTITY lt       "&#60;">   <!-- U+003C ISOnum    - less-than sign                                                        -->
  <!ENTITY gt       "&#62;">   <!-- U+003E ISOnum    - greater-than sign                                                     -->
  
  <!-- Latin Extended-A -->
  <!ENTITY OElig    "&#338;">  <!-- U+0152 ISOlat2   - latin capital ligature OE                                             -->
  <!ENTITY oelig    "&#339;">  <!-- U+0153 ISOlat2   - latin small ligature oe                                               -->
  
  <!-- ligature is a misnomer, this is a separate character in some languages -->
  <!ENTITY Scaron   "&#352;">  <!-- U+0160 ISOlat2   - latin capital letter S with caron                                     -->
  <!ENTITY scaron   "&#353;">  <!-- U+0161 ISOlat2   - latin small letter s with caron                                       -->
  <!ENTITY Yuml     "&#376;">  <!-- U+0178 ISOlat2   - latin capital letter Y with diaeresis                                 -->
  
  <!-- Spacing Modifier Letters -->
  <!ENTITY circ     "&#710;" > <!-- U+02C6 ISOpub    - modifier letter circumflex accent                                     -->
  <!ENTITY tilde    "&#732;" > <!-- U+02DC ISOdia    - small tilde                                                           -->
  
  <!-- General Punctuation -->
  <!ENTITY ensp     "&#8194;"> <!-- U+2002 ISOpub    - en space                                                              -->
  <!ENTITY emsp     "&#8195;"> <!-- U+2003 ISOpub    - em space                                                              -->
  <!ENTITY thinsp   "&#8201;"> <!-- U+2009 ISOpub    - thin space                                                            -->
  <!ENTITY zwnj     "&#8204;"> <!-- U+200C RFC 2070  - zero width non-joiner                                                 -->
  <!ENTITY zwj      "&#8205;"> <!-- U+200D RFC 2070  - zero width joiner                                                     -->
  <!ENTITY lrm      "&#8206;"> <!-- U+200E RFC 2070  - left-to-right mark                                                    -->
  <!ENTITY rlm      "&#8207;"> <!-- U+200F RFC 2070  - right-to-left mark                                                    -->
  <!ENTITY ndash    "&#8211;"> <!-- U+2013 ISOpub    - en dash                                                               -->
  <!ENTITY mdash    "&#8212;"> <!-- U+2014 ISOpub    - em dash                                                               -->
  <!ENTITY lsquo    "&#8216;"> <!-- U+2018 ISOnum    - left single quotation mark                                            -->
  <!ENTITY rsquo    "&#8217;"> <!-- U+2019 ISOnum    - right single quotation mark                                           -->
  <!ENTITY sbquo    "&#8218;"> <!-- U+201A NEW       - single low-9 quotation mark                                           -->
  <!ENTITY ldquo    "&#8220;"> <!-- U+201C ISOnum    - left double quotation mark                                            -->
  <!ENTITY rdquo    "&#8221;"> <!-- U+201D ISOnum    - right double quotation mark,                                          -->
  <!ENTITY bdquo    "&#8222;"> <!-- U+201E NEW       - double low-9 quotation mark                                           -->
  <!ENTITY dagger   "&#8224;"> <!-- U+2020 ISOpub    - dagger                                                                -->
  <!ENTITY Dagger   "&#8225;"> <!-- U+2021 ISOpub    - double dagger                                                         -->
  <!ENTITY permil   "&#8240;"> <!-- U+2030 ISOtech   - per mille sign                                                        -->
  <!ENTITY lsaquo   "&#8249;"> <!-- U+2039 ISO prop. - single left-pointing angle quotation mark                             -->
  
  <!-- lsaquo is proposed but not yet ISO standardized -->
  <!ENTITY rsaquo   "&#8250;"> <!-- U+203A ISO prop. -   single right-pointing angle quotation mark                          -->
  
  <!-- rsaquo is proposed but not yet ISO standardized -->
  <!ENTITY euro     "&#8364;"> <!-- U+20AC NEW       -   euro sign                                                           -->
  
  <!-- Latin Extended-B -->
  <!ENTITY fnof     "&#402;">  <!-- U+0192 ISOtech   - latin small f with hook = function = florin                           -->
  
  <!-- Greek -->
  <!ENTITY Alpha    "&#913;">  <!-- U+0391           - greek capital letter alpha                                            -->
  <!ENTITY Beta     "&#914;">  <!-- U+0392           - greek capital letter beta                                             -->
  <!ENTITY Gamma    "&#915;">  <!-- U+0393 ISOgrk3   - greek capital letter gamma                                            -->
  <!ENTITY Delta    "&#916;">  <!-- U+0394 ISOgrk3   - greek capital letter delta                                            -->
  <!ENTITY Epsilon  "&#917;">  <!-- U+0395           - greek capital letter epsilon                                          -->
  <!ENTITY Zeta     "&#918;">  <!-- U+0396           - greek capital letter zeta                                             -->
  <!ENTITY Eta      "&#919;">  <!-- U+0397           - greek capital letter eta                                              -->
  <!ENTITY Theta    "&#920;">  <!-- U+0398 ISOgrk3   - greek capital letter theta                                            -->
  <!ENTITY Iota     "&#921;">  <!-- U+0399           - greek capital letter iota                                             -->
  <!ENTITY Kappa    "&#922;">  <!-- U+039A           - greek capital letter kappa                                            -->
  <!ENTITY Lambda   "&#923;">  <!-- U+039B ISOgrk3   - greek capital letter lambda                                           -->
  <!ENTITY Mu       "&#924;">  <!-- U+039C           - greek capital letter mu                                               -->
  <!ENTITY Nu       "&#925;">  <!-- U+039D           - greek capital letter nu                                               -->
  <!ENTITY Xi       "&#926;">  <!-- U+039E ISOgrk3   - greek capital letter xi                                               -->
  <!ENTITY Omicron  "&#927;">  <!-- U+039F           - greek capital letter omicron                                          -->
  <!ENTITY Pi       "&#928;">  <!-- U+03A0 ISOgrk3   - greek capital letter pi                                               -->
  <!ENTITY Rho      "&#929;">  <!-- U+03A1           - greek capital letter rho                                              -->
  <!ENTITY Sigma    "&#931;">  <!-- U+03A3 ISOgrk3   - greek capital letter sigma                                            -->
  <!ENTITY Tau      "&#932;">  <!-- U+03A4           - greek capital letter tau                                              -->
  <!ENTITY Upsilon  "&#933;">  <!-- U+03A5 ISOgrk3   - greek capital letter upsilon                                          -->
  <!ENTITY Phi      "&#934;">  <!-- U+03A6 ISOgrk3   - greek capital letter phi                                              -->
  <!ENTITY Chi      "&#935;">  <!-- U+03A7           - greek capital letter chi                                              -->
  <!ENTITY Psi      "&#936;">  <!-- U+03A8 ISOgrk3   - greek capital letter psi                                              -->
  <!ENTITY Omega    "&#937;">  <!-- U+03A9 ISOgrk3   - greek capital letter omega                                            -->
  <!ENTITY alpha    "&#945;">  <!-- U+03B1 ISOgrk3   - greek small letter alpha                                              -->
  <!ENTITY beta     "&#946;">  <!-- U+03B2 ISOgrk3   - greek small letter beta                                               -->
  <!ENTITY gamma    "&#947;">  <!-- U+03B3 ISOgrk3   - greek small letter gamma                                              -->
  <!ENTITY delta    "&#948;">  <!-- U+03B4 ISOgrk3   - greek small letter delta                                              -->
  <!ENTITY epsilon  "&#949;">  <!-- U+03B5 ISOgrk3   - greek small letter epsilon                                            -->
  <!ENTITY zeta     "&#950;">  <!-- U+03B6 ISOgrk3   - greek small letter zeta                                               -->
  <!ENTITY eta      "&#951;">  <!-- U+03B7 ISOgrk3   - greek small letter eta                                                -->
  <!ENTITY theta    "&#952;">  <!-- U+03B8 ISOgrk3   - greek small letter theta                                              -->
  <!ENTITY iota     "&#953;">  <!-- U+03B9 ISOgrk3   - greek small letter iota                                               -->
  <!ENTITY kappa    "&#954;">  <!-- U+03BA ISOgrk3   - greek small letter kappa                                              -->
  <!ENTITY lambda   "&#955;">  <!-- U+03BB ISOgrk3   - greek small letter lambda                                             -->
  <!ENTITY mu       "&#956;">  <!-- U+03BC ISOgrk3   - greek small letter mu                                                 -->
  <!ENTITY nu       "&#957;">  <!-- U+03BD ISOgrk3   - greek small letter nu                                                 -->
  <!ENTITY xi       "&#958;">  <!-- U+03BE ISOgrk3   - greek small letter xi                                                 -->
  <!ENTITY omicron  "&#959;">  <!-- U+03BF NEW       - greek small letter omicron                                            -->
  <!ENTITY pi       "&#960;">  <!-- U+03C0 ISOgrk3   - greek small letter pi                                                 -->
  <!ENTITY rho      "&#961;">  <!-- U+03C1 ISOgrk3   - greek small letter rho                                                -->
  <!ENTITY sigmaf   "&#962;">  <!-- U+03C2 ISOgrk3   - greek small letter final sigma                                        -->
  <!ENTITY sigma    "&#963;">  <!-- U+03C3 ISOgrk3   - greek small letter sigma                                              -->
  <!ENTITY tau      "&#964;">  <!-- U+03C4 ISOgrk3   - greek small letter tau                                                -->
  <!ENTITY upsilon  "&#965;">  <!-- U+03C5 ISOgrk3   - greek small letter upsilon                                            -->
  <!ENTITY phi      "&#966;">  <!-- U+03C6 ISOgrk3   - greek small letter phi                                                -->
  <!ENTITY chi      "&#967;">  <!-- U+03C7 ISOgrk3   - greek small letter chi                                                -->
  <!ENTITY psi      "&#968;">  <!-- U+03C8 ISOgrk3   - greek small letter psi                                                -->
  <!ENTITY omega    "&#969;">  <!-- U+03C9 ISOgrk3   - greek small letter omega                                              -->
  <!ENTITY thetasym "&#977;">  <!-- U+03D1 NEW       - greek small letter theta symbol                                       -->
  <!ENTITY upsih    "&#978;">  <!-- U+03D2 NEW       - greek upsilon with hook symbol                                        -->
  <!ENTITY piv      "&#982;">  <!-- U+03D6 ISOgrk3   - greek pi symbol                                                       -->
  
  <!-- General Punctuation -->
  <!ENTITY bull     "&#8226;"> <!-- U+2022 ISOpub    - bullet = black small circle                                           -->
  <!ENTITY hellip   "&#8230;"> <!-- U+2026 ISOpub    - horizontal ellipsis = three dot leader                                -->
  <!ENTITY prime    "&#8242;"> <!-- U+2032 ISOtech   - prime = minutes = feet                                                -->
  <!ENTITY Prime    "&#8243;"> <!-- U+2033 ISOtech   - double prime = seconds = inches                                       -->
  <!ENTITY oline    "&#8254;"> <!-- U+203E NEW       - overline = spacing overscore                                          -->
  <!ENTITY frasl    "&#8260;"> <!-- U+2044 NEW       - fraction slash                                                        -->
  
  <!-- Letterlike Symbols -->
  <!ENTITY weierp   "&#8472;"> <!-- U+2118 ISOamso   - script capital P = power set = Weierstrass p                          -->
  <!ENTITY image    "&#8465;"> <!-- U+2111 ISOamso   - blackletter capital I = imaginary part                                -->
  <!ENTITY real     "&#8476;"> <!-- U+211C ISOamso   - blackletter capital R = real part symbol                              -->
  <!ENTITY trade    "&#8482;"> <!-- U+2122 ISOnum    - trade mark sign                                                       -->
  <!ENTITY alefsym  "&#8501;"> <!-- U+2135 NEW       - alef symbol = first transfinite cardinal                              -->
  
  <!-- Arrows -->
  <!ENTITY larr     "&#8592;"> <!-- U+2190 ISOnum    - leftwards arrow                                                       -->
  <!ENTITY uarr     "&#8593;"> <!-- U+2191 ISOnum    - upwards arrow                                                         -->
  <!ENTITY rarr     "&#8594;"> <!-- U+2192 ISOnum    - rightwards arrow                                                      -->
  <!ENTITY darr     "&#8595;"> <!-- U+2193 ISOnum    - downwards arrow                                                       -->
  <!ENTITY harr     "&#8596;"> <!-- U+2194 ISOamsa   - left right arrow                                                      -->
  <!ENTITY crarr    "&#8629;"> <!-- U+21B5 NEW       - downwards arrow with corner leftwards = carriage return               -->
  <!ENTITY lArr     "&#8656;"> <!-- U+21D0 ISOtech   - leftwards double arrow                                                -->
  <!ENTITY uArr     "&#8657;"> <!-- U+21D1 ISOamsa   - upwards double arrow                                                  -->
  <!ENTITY rArr     "&#8658;"> <!-- U+21D2 ISOtech   - rightwards double arrow                                               -->
  <!ENTITY dArr     "&#8659;"> <!-- U+21D3 ISOamsa   - downwards double arrow                                                -->
  <!ENTITY hArr     "&#8660;"> <!-- U+21D4 ISOamsa   - left right double arrow                                               -->
  
  <!-- Mathematical Operators -->
  <!ENTITY forall   "&#8704;"> <!-- U+2200 ISOtech   - for all                                                               -->
  <!ENTITY part     "&#8706;"> <!-- U+2202 ISOtech   - partial differential                                                  -->
  <!ENTITY exist    "&#8707;"> <!-- U+2203 ISOtech   - there exists                                                          -->
  <!ENTITY empty    "&#8709;"> <!-- U+2205 ISOamso   - empty set = null set = diameter                                       -->
  <!ENTITY nabla    "&#8711;"> <!-- U+2207 ISOtech   - nabla = backward difference                                           -->
  <!ENTITY isin     "&#8712;"> <!-- U+2208 ISOtech   - element of                                                            -->
  <!ENTITY notin    "&#8713;"> <!-- U+2209 ISOtech   - not an element of                                                     -->
  <!ENTITY ni       "&#8715;"> <!-- U+220B ISOtech   - contains as member                                                    -->
  <!ENTITY prod     "&#8719;"> <!-- U+220F ISOamsb   - n-ary product = product sign                                          -->
  <!ENTITY sum      "&#8721;"> <!-- U+2211 ISOamsb   - n-ary sumation                                                        -->
  <!ENTITY minus    "&#8722;"> <!-- U+2212 ISOtech   - minus sign                                                            -->
  <!ENTITY lowast   "&#8727;"> <!-- U+2217 ISOtech   - asterisk operator                                                     -->
  <!ENTITY radic    "&#8730;"> <!-- U+221A ISOtech   - square root = radical sign                                            -->
  <!ENTITY prop     "&#8733;"> <!-- U+221D ISOtech   - proportional to                                                       -->
  <!ENTITY infin    "&#8734;"> <!-- U+221E ISOtech   - infinity                                                              -->
  <!ENTITY ang      "&#8736;"> <!-- U+2220 ISOamso   - angle                                                                 -->
  <!ENTITY and      "&#8743;"> <!-- U+2227 ISOtech   - logical and = wedge                                                   -->
  <!ENTITY or       "&#8744;"> <!-- U+2228 ISOtech   - logical or = vee                                                      -->
  <!ENTITY cap      "&#8745;"> <!-- U+2229 ISOtech   - intersection = cap                                                    -->
  <!ENTITY cup      "&#8746;"> <!-- U+222A ISOtech   - union = cup                                                           -->
  <!ENTITY int      "&#8747;"> <!-- U+222B ISOtech   - integral                                                              -->
  <!ENTITY there4   "&#8756;"> <!-- U+2234 ISOtech   - therefore                                                             -->
  <!ENTITY sim      "&#8764;"> <!-- U+223C ISOtech   - tilde operator = varies with = similar to                             -->
  <!ENTITY cong     "&#8773;"> <!-- U+2245 ISOtech   - approximately equal to                                                -->
  <!ENTITY asymp    "&#8776;"> <!-- U+2248 ISOamsr   - almost equal to = asymptotic to                                       -->
  <!ENTITY ne       "&#8800;"> <!-- U+2260 ISOtech   - not equal to                                                          -->
  <!ENTITY equiv    "&#8801;"> <!-- U+2261 ISOtech   - identical to                                                          -->
  <!ENTITY le       "&#8804;"> <!-- U+2264 ISOtech   - less-than or equal to                                                 -->
  <!ENTITY ge       "&#8805;"> <!-- U+2265 ISOtech   - greater-than or equal to                                              -->
  <!ENTITY sub      "&#8834;"> <!-- U+2282 ISOtech   - subset of                                                             -->
  <!ENTITY sup      "&#8835;"> <!-- U+2283 ISOtech   - superset of                                                           -->
  <!ENTITY nsub     "&#8836;"> <!-- U+2284 ISOamsn   - not a subset of                                                       -->
  <!ENTITY sube     "&#8838;"> <!-- U+2286 ISOtech   - subset of or equal to                                                 -->
  <!ENTITY supe     "&#8839;"> <!-- U+2287 ISOtech   - superset of or equal to                                               -->
  <!ENTITY oplus    "&#8853;"> <!-- U+2295 ISOamsb   - circled plus = direct sum                                             -->
  <!ENTITY otimes   "&#8855;"> <!-- U+2297 ISOamsb   - circled times = vector product                                        -->
  <!ENTITY perp     "&#8869;"> <!-- U+22A5 ISOtech   - up tack = orthogonal to = perpendicular                               -->
  <!ENTITY sdot     "&#8901;"> <!-- U+22C5 ISOamsb   - dot operator                                                          -->
  
  <!-- Miscellaneous Technical -->
  <!ENTITY lceil    "&#8968;"> <!-- U+2308 ISOamsc   - left ceiling = apl upstile                                            -->
  <!ENTITY rceil    "&#8969;"> <!-- U+2309 ISOamsc   - right ceiling                                                         -->
  <!ENTITY lfloor   "&#8970;"> <!-- U+230A ISOamsc   - left floor = apl downstile                                            -->
  <!ENTITY rfloor   "&#8971;"> <!-- U+230B ISOamsc   - right floor                                                           -->
  <!ENTITY lang     "&#9001;"> <!-- U+2329 ISOtech   - left-pointing angle bracket = bra                                     -->
  <!ENTITY rang     "&#9002;"> <!-- U+232A ISOtech   - right-pointing angle bracket = ket                                    -->
  
  <!-- Geometric Shapes -->
  <!ENTITY loz      "&#9674;"> <!-- U+25CA ISOpub    - lozenge                                                               -->
  
  <!-- Miscellaneous Symbols -->
  <!ENTITY spades   "&#9824;"> <!-- U+2660 ISOpub    - black spade suit                                                      -->
  <!ENTITY clubs    "&#9827;"> <!-- U+2663 ISOpub    - black club suit = shamrock                                            -->
  <!ENTITY hearts   "&#9829;"> <!-- U+2665 ISOpub    - black heart suit = valentine                                          -->
  <!ENTITY diams    "&#9830;"> <!-- U+2666 ISOpub    - black diamond suit                                                    -->
  
  
  
  1.1                  xml-0.0/docs/dtd/document.dtd
  
  Index: document.dtd
  ===================================================================
  <?xml encoding='US-ASCII'?>
  
  <!-- STYLEBOOK DOCUMENT DTD -->
  
  <!ENTITY % blocksEntity SYSTEM "blocks.ent">
  %blocksEntity;
  
  <!ELEMENT s1 (s2)*>
  <!ELEMENT s2 (s3|split|%blocks;)*>
  <!ELEMENT s3 (s4|%blocks;)*>
  <!ELEMENT s4 (s5|%blocks;)*>
  <!ELEMENT s5 (%blocks;)*>
  
  <!ELEMENT split (left,right)>
  <!ELEMENT left (s3|%blocks;)*>
  <!ELEMENT right (s3|%blocks;)*>
  
  <!ATTLIST s1 title CDATA #REQUIRED>
  <!ATTLIST s2 title CDATA #REQUIRED>
  <!ATTLIST s3 title CDATA #REQUIRED>
  <!ATTLIST s4 title CDATA #REQUIRED>
  <!ATTLIST s5 title CDATA #REQUIRED>
  
  
  
  1.1                  xml-0.0/docs/dtd/faqs.dtd
  
  Index: faqs.dtd
  ===================================================================
  <?xml encoding='US-ASCII'?>
  
  <!-- STYLEBOOK FAQ DTD -->
  
  <!ENTITY % blocksEntity SYSTEM "blocks.ent">
  %blocksEntity;
  
  <!ELEMENT faqs (faq)+>
  <!ATTLIST faqs title CDATA #REQUIRED>
  
  <!ELEMENT faq (q,a)>
  <!ATTLIST faq title CDATA #IMPLIED>
  
  
  <!ELEMENT q (#PCDATA)>
  <!ELEMENT a (%blocks;)+>
  
  
  
  1.1                  xml-0.0/docs/dtd/links.ent
  
  Index: links.ent
  ===================================================================
  <?xml encoding='US-ASCII'?>
  
  <!-- LINKS ENTITY -->
  
  <!ENTITY % links "link|anchor|jump">
  
  <!ELEMENT anchor EMPTY>
  <!ATTLIST anchor id NMTOKEN #REQUIRED>
  
  <!ELEMENT img EMPTY>
  <!ATTLIST img src CDATA #REQUIRED>
  
  <!ELEMENT link (#PCDATA|img)*>
  <!ATTLIST link idref NMTOKEN #REQUIRED
                 anchor CDATA  #IMPLIED>
  
  <!ELEMENT jump (#PCDATA|img)*>
  <!ATTLIST jump href CDATA #REQUIRED>
  
  
  
  1.1                  xml-0.0/docs/dtd/markup.ent
  
  Index: markup.ent
  ===================================================================
  <?xml encoding='US-ASCII'?>
  
  <!ENTITY % charEntity SYSTEM "characters.ent">
  %charEntity;
  
  
  <!-- MARKUP ENTITY -->
  <!ENTITY % markup "em|ref|code|br">
  
  <!ELEMENT em (#PCDATA)>
  <!ELEMENT ref (#PCDATA)>
  <!ELEMENT code (#PCDATA)>
  <!ELEMENT br EMPTY>
  
  
  1.1                  xml-0.0/docs/fop/readme.xml
  
  Index: readme.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="FOP XSL-FO">
    <s2 title="FOP XSL-FO">
      <p>
        FOP is the world's first print formatter driven by XSL formatting 
        objects. It is a Java 1.1 application that reads a formatting object 
        tree and then turns it into a PDF document. The formatting object 
        tree, can be in the form of an XML document (output by an XSLT 
        engine like Xalan) or can be passed in memory as a DOM Document or (in 
        the case of Xalan) SAX events.
      </p>
      <p>
        Additional documentation to be provided soon. Watch this space.
      </p>
    </s2>
  </s1>
  
  
  1.1                  xml-0.0/docs/resources/bottom.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-0.0/docs/resources/button-1.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-0.0/docs/resources/button-2.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-0.0/docs/resources/button-3.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-0.0/docs/resources/button-a-bk.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-0.0/docs/resources/button-a.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-0.0/docs/resources/button-asf-hi.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-0.0/docs/resources/button-asf-lo.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-0.0/docs/resources/button-b.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-0.0/docs/resources/button-w3c-hi.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-0.0/docs/resources/button-w3c-lo.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-0.0/docs/resources/button-xml-hi.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-0.0/docs/resources/button-xml-lo.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-0.0/docs/resources/close.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-0.0/docs/resources/dot.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-0.0/docs/resources/join.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-0.0/docs/resources/line.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-0.0/docs/resources/logo.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-0.0/docs/resources/right.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-0.0/docs/resources/script.js
  
  Index: script.js
  ===================================================================
  var on=new Array();
  var off=new Array();
  
  function topon(name) {
    document.images["top."+name].src="images/button-"+name+"-hi.gif";
  }
  
  function topoff(name) {
    document.images["top."+name].src="images/button-"+name+"-lo.gif";
  }
  
  function sideon(name) {
    document.images["side."+name].src=on[name].src;
  }
  
  function sideoff(name) {
    document.images["side."+name].src=off[name].src;
  }
  
  function sideload(name) {
    on[name]=new Image();
    on[name].src="images/"+name+"-2.jpg";
    off[name]=new Image();
    off[name].src="images/"+name+"-3.jpg";
  }
  
  
  
  1.1                  xml-0.0/docs/resources/separator.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-0.0/docs/resources/style.css
  
  Index: style.css
  ===================================================================
  p {
    text-align: justify;
  }
    
  
  
  1.1                  xml-0.0/docs/resources/title.gif
  
  	<<Binary file>>
  
  
  1.1                  xml-0.0/docs/stylesheets/book2project.xsl
  
  Index: book2project.xsl
  ===================================================================
  <?xml version="1.0"?>
  
  <xsl:stylesheet xmlns:xsl="http://www.w3.org/XSL/Transform/1.0">
  
    <xsl:template match="/">
      <xsl:apply-templates/>
    </xsl:template>
  
    <xsl:template match="book">
      <project>
        <xsl:apply-templates/>
        <resource source="resources/*.gif" target="images/*.gif"/>
        <resource source="resources/*.css" target="*.css"/>
        <resource source="resources/*.js"  target="*.js"/>
      </project>
    </xsl:template>
  
  <!-- ======================================================================= -->
  <!-- NAMED TEMPLATES                                                         -->
  <!-- ======================================================================= -->
  
  <!-- THE GENERIC DOCUMENT PIPELINE -->
    <xsl:template name="document">
      <xsl:param name="href"/>
      <xsl:param name="id"  />
  
      <create source="{$href}" target="{$id}.html" producer="context" printer="html">
        <parameter name="id" value="{$id}"/>
        <processor name="xslt">
          <parameter name="stylesheet" value="stylesheets/context2document.xsl"/>
        </processor>
        <processor name="import"/>
        <processor name="xslt">
          <parameter name="stylesheet" value="stylesheets/document2html.xsl"/>
        </processor>
      </create>
    </xsl:template>
  
  <!-- THE FAQ DOCUMENT PIPELINE -->
    <xsl:template name="faq">
      <xsl:param name="href"/>
      <xsl:param name="id"  />
  
      <create source="{$href}" target="{$id}.html" producer="context" printer="html">
        <parameter name="id" value="{$id}"/>
        <processor name="xslt">
          <parameter name="stylesheet" value="stylesheets/context2document.xsl"/>
        </processor>
        <processor name="import"/>
        <processor name="xslt">
          <parameter name="stylesheet" value="stylesheets/faq2document1.xsl"/>
        </processor>
        <processor name="xslt">
          <parameter name="stylesheet" value="stylesheets/faq2document2.xsl"/>
        </processor>
        <processor name="xslt">
          <parameter name="stylesheet" value="stylesheets/document2html.xsl"/>
        </processor>
      </create>
    </xsl:template>
  
  <!-- THE TITLE IMAGE PIPELINE -->
    <xsl:template name="title">
      <xsl:param name="href"/>
      <xsl:param name="id"  />
  
      <create source="{$href}" target="images/{$id}.jpg" producer="parser" printer="image">
        <processor name="xslt">
          <parameter name="stylesheet" value="stylesheets/document2title.xsl"/>
        </processor>
      </create>
    </xsl:template>
  
  <!-- THE SIDEBAR BUTTONS PIPELINE -->
    <xsl:template name="buttons">
      <xsl:param name="label"/>
      <xsl:param name="id"   />
  
      <create source="{$label}" target="images/{$id}-1.jpg" producer="context" printer="image">
        <processor name="xslt">
          <parameter name="stylesheet" value="stylesheets/document2button1.xsl"/>
        </processor>
      </create>
      <create source="{$label}" target="images/{$id}-2.jpg" producer="context" printer="image">
        <processor name="xslt">
          <parameter name="stylesheet" value="stylesheets/document2button2.xsl"/>
        </processor>
      </create>
      <create source="{$label}" target="images/{$id}-3.jpg" producer="context" printer="image">
        <processor name="xslt">
          <parameter name="stylesheet" value="stylesheets/document2button3.xsl"/>
        </processor>
      </create>
    </xsl:template>
  
  <!-- ======================================================================= -->
  <!-- TEMPLATE MATCHING RULES                                                 -->
  <!-- ======================================================================= -->
  
  <!-- TEMPLATING FOR <chapter> ELEMENT -->
    <xsl:template match="chapter">
      <xsl:if test="@type='document'">
        <xsl:call-template name="document">
          <xsl:with-param name="href" select="@href"/>
          <xsl:with-param name="id"   select="@id"  />
        </xsl:call-template>
      </xsl:if>
  
      <xsl:if test="@type='faq'">
        <xsl:call-template name="faq">
          <xsl:with-param name="href" select="@href"/>
          <xsl:with-param name="id"   select="@id"  />
        </xsl:call-template>
      </xsl:if>
  
      <xsl:call-template name="title">
        <xsl:with-param name="href" select="@href"/>
        <xsl:with-param name="id"   select="@id"  />
      </xsl:call-template>
  
      <xsl:call-template name="buttons">
        <xsl:with-param name="label" select="@label"/>
        <xsl:with-param name="id"    select="@id"  />
      </xsl:call-template>
    </xsl:template>
  
  <!-- TEMPLATING FOR <hidden> ELEMENT -->
    <xsl:template match="hidden">
      <xsl:if test="@type='document'">
        <xsl:call-template name="document">
          <xsl:with-param name="href" select="@href"/>
          <xsl:with-param name="id"   select="@id"  />
        </xsl:call-template>
      </xsl:if>
  
      <xsl:if test="@type='faq'">
        <xsl:call-template name="faq">
          <xsl:with-param name="href" select="@href"/>
          <xsl:with-param name="id"   select="@id"  />
        </xsl:call-template>
      </xsl:if>
  
      <xsl:call-template name="title">
        <xsl:with-param name="href" select="@href"/>
        <xsl:with-param name="id"   select="@id"  />
      </xsl:call-template>
    </xsl:template>
  
  <!-- TEMPLATING FOR <group> ELEMENT -->
    <xsl:template match="group">
      <xsl:if test="@type='faqs'">
        <create source="{@href}" target="{@id}.html" producer="context" printer="html">
          <parameter name="id" value="{@id}"/>
          <processor name="xslt">
            <parameter name="stylesheet" value="stylesheets/context2faqs.xsl"/>
          </processor>
          <processor name="import"/>
          <processor name="xslt">
            <parameter name="stylesheet" value="stylesheets/faqs2document1.xsl"/>
          </processor>
          <processor name="import"/>
          <processor name="xslt">
            <parameter name="stylesheet" value="stylesheets/faqs2document2.xsl"/>
          </processor>
          <processor name="xslt">
            <parameter name="stylesheet" value="stylesheets/document2html.xsl"/>
          </processor>
        </create>
        <xsl:apply-templates/>
      </xsl:if>
  
      <create source="{@label}" target="images/{@id}.jpg" producer="context" printer="image">
        <processor name="xslt">
          <parameter name="stylesheet" value="stylesheets/group2title.xsl"/>
        </processor>
      </create>
  
      <xsl:call-template name="buttons">
        <xsl:with-param name="label" select="@label"/>
        <xsl:with-param name="id"    select="@id"  />
      </xsl:call-template>
    </xsl:template>
  
  <!-- TEMPLATING FOR <jump> ELEMENT -->
    <xsl:template match="extern">
      <xsl:call-template name="buttons">
        <xsl:with-param name="label" select="@label"/>
        <xsl:with-param name="id"    select="@id"  />
      </xsl:call-template>
    </xsl:template>
  
  
  </xsl:stylesheet>
  
  
  1.1                  xml-0.0/docs/stylesheets/context2document.xsl
  
  Index: context2document.xsl
  ===================================================================
  <?xml version="1.0"?>
  
  <xsl:stylesheet xmlns:xsl="http://www.w3.org/XSL/Transform/1.0">
  
    <xsl:template match="/">
      <xsl:apply-templates/>
    </xsl:template>
  
    <xsl:template match="context">
      <document id="{child::parameter[attribute::name='id']/@value}">
        <xsl:processing-instruction name="import">producer="project"</xsl:processing-instruction>
        <xsl:processing-instruction name="import">producer="parser" source="<xsl:value-of select="@source"/>"</xsl:processing-instruction>
      </document>
    </xsl:template>
  
  </xsl:stylesheet>
  
  
  1.1                  xml-0.0/docs/stylesheets/context2faqs.xsl
  
  Index: context2faqs.xsl
  ===================================================================
  <?xml version="1.0"?>
  
  <xsl:stylesheet xmlns:xsl="http://www.w3.org/XSL/Transform/1.0">
  
    <xsl:template match="/">
      <xsl:apply-templates/>
    </xsl:template>
  
    <xsl:template match="context">
      <document id="{child::parameter[attribute::name='id']/@value}">
        <xsl:processing-instruction name="import">producer="project"</xsl:processing-instruction>
      </document>
    </xsl:template>
  
  </xsl:stylesheet>
  
  
  1.1                  xml-0.0/docs/stylesheets/document2button1.xsl
  
  Index: document2button1.xsl
  ===================================================================
  <?xml version="1.0"?>
  
  <xsl:stylesheet xmlns:xsl="http://www.w3.org/XSL/Transform/1.0">
  
    <xsl:template match="/">
      <xsl:apply-templates/>
    </xsl:template>
  
    <xsl:template match="context">
      <image source="resources/button-a.gif">
        <text font="sanserif" size="12" x="14" y="1" halign="left" valign="top" color="ffffff"
              style="italic" text="{@source}"/>
      </image>
    </xsl:template>
  
  </xsl:stylesheet>
  
  
  1.1                  xml-0.0/docs/stylesheets/document2button2.xsl
  
  Index: document2button2.xsl
  ===================================================================
  <?xml version="1.0"?>
  
  <xsl:stylesheet xmlns:xsl="http://www.w3.org/XSL/Transform/1.0">
  
    <xsl:template match="/">
      <xsl:apply-templates/>
    </xsl:template>
  
    <xsl:template match="context">
      <image source="resources/button-b.gif">
        <text font="sanserif" size="12" x="14" y="1" halign="left" valign="top" color="ffff00"
              style="italic" text="{@source}"/>
      </image>
    </xsl:template>
  
  </xsl:stylesheet>
  
  
  1.1                  xml-0.0/docs/stylesheets/document2button3.xsl
  
  Index: document2button3.xsl
  ===================================================================
  <?xml version="1.0"?>
  
  <xsl:stylesheet xmlns:xsl="http://www.w3.org/XSL/Transform/1.0">
  
    <xsl:template match="/">
      <xsl:apply-templates/>
    </xsl:template>
  
    <xsl:template match="context">
      <image source="resources/button-b.gif">
        <text font="sanserif" size="12" x="14" y="1" halign="left" valign="top" color="ffffff"
              style="italic" text="{@source}"/>
      </image>
    </xsl:template>
  
  </xsl:stylesheet>
  
  
  1.1                  xml-0.0/docs/stylesheets/document2html.xsl
  
  Index: document2html.xsl
  ===================================================================
  <?xml version="1.0"?>
  
  <xsl:stylesheet xmlns:xsl="http://www.w3.org/XSL/Transform/1.0">
  
    <xsl:template match="/">
      <xsl:apply-templates/>
    </xsl:template>
  
    <xsl:template match="document">
      <html>
        <script language="JavaScript" src="script.js">
          <xsl:comment>don't remove this comment</xsl:comment>
        </script>
        <head>
          <link rel="stylesheet" type="text/css" href="style.css" title="style"/>
          <title><xsl:value-of select="s1/@title"/></title>
        </head>
        <body text="#000000" link="#0000ff" vlink="#0000aa" alink="#ff0000"
              topmargin="4" leftmargin="4" marginwidth="4" marginheight="4"
              bgcolor="#ffffff">
          <!-- THE TOP BAR -->
          <table width="620" cellspacing="0" cellpadding="0" border="0">
            <tr>
              <td width="135" height="60" rowspan="3" valign="top" align="left">
                <img width="135" height="60" src="images/logo.gif" hspace="0" vspace="0" border="0"/></td>
              <td width="456" height="5" valign="top" align="left" colspan="4">
                <img width="456" height="5" src="images/line.gif" hspace="0" vspace="0" border="0"/></td>
              <td width="29" height="60"  rowspan="3" valign="top" align="left">
                <img width="29" height="60" src="images/right.gif" hspace="0" vspace="0" border="0"/></td>
            </tr>
            <tr>
              <td width="456" height="35" valign="top" align="left" colspan="4" bgcolor="#0086b2">
                <img src="images/{@id}.jpg" width="456" height="35" hspace="0" vspace="0" border="0" alt="{s1/@title}"/></td>
            </tr>
            <tr>
              <td width="168" height="20" valign="top" align="left">
                <img width="168" height="20" src="images/bottom.gif" hspace="0" vspace="0" border="0"/></td>
              <td width="96" height="20" valign="top" align="left">
                <a href="http://xml.apache.org/" onMouseOver="topon('xml')" onMouseOut="topoff('xml')">
                <img alt="http://xml.apache.org/" width="96" height="20" src="images/button-xml-lo.gif" name="top.xml" hspace="0" vspace="0" border="0"/></a></td>
              <td width="96" height="20" valign="top" align="left">
                <a href="http://www.apache.org/" onMouseOver="topon('asf')" onMouseOut="topoff('asf')">
                <img alt="http://www.apache.org/" width="96" height="20" src="images/button-asf-lo.gif" name="top.asf" hspace="0" vspace="0" border="0"/></a></td>
              <td width="96" height="20" valign="top" align="left">
                <a href="http://www.w3.org/" onMouseOver="topon('w3c')" onMouseOut="topoff('w3c')">
                <img alt="http://www.w3.org/" width="96" height="20" src="images/button-w3c-lo.gif" name="top.w3c" hspace="0" vspace="0" border="0"/></a></td>
            </tr>
          </table>
          <!-- THE TOP BAR ENDS -->
          <table width="620" cellspacing="0" cellpadding="0" border="0">
            <tr>
              <!-- THE SIDE BAR -->
              <td width="120" valign="top" align="left">
                <img width="120" height="14" src="images/join.gif" hspace="0" vspace="0" border="0"/><br/>
                <xsl:apply-templates select="book"/>
                <img width="120" height="14" src="images/close.gif" hspace="0" vspace="0" border="0"/><br/>
              </td>
              <!-- THE SIDE BAR ENDS -->
              <xsl:apply-templates select="s1"/>
            </tr>
          </table><br/>
          <table width="620" border="0" cellspacing="0" cellpadding="0">
            <tr><td bgcolor="#0086b2"><img src="images/dot.gif" width="1" height="1"/></td></tr>
            <tr>
              <td align="center"><font size="-1" color="#0086b2"><i>
                Copyright &#169; 1999, The Apache Software Foundation.
                All Rights Reserved.
              </i></font></td>
            </tr>
          </table>
        </body>
      </html>
    </xsl:template>
  
  <!-- ###################################################################### -->
  <!-- book -->
  
    <xsl:template match="book">
      <xsl:apply-templates/>
    </xsl:template>
  
    <xsl:template match="separator">
      <img alt="----------" width="120" height="6" src="images/separator.gif" hspace="0" vspace="0" border="0"/><br/>
    </xsl:template>
  
    <xsl:template match="chapter">
      <xsl:if test="@id=/document/@id">
        <img width="120" height="12" src="images/{@id}-1.jpg" hspace="0" vspace="0" border="0" alt="{@label}"/><br/>
      </xsl:if>
      <xsl:if test="not(@id=/document/@id)">
        <a href="{@id}.html" onMouseOver="sideon('{@id}')" onMouseOut="sideoff('{@id}')">
        <img onLoad="sideload('{@id}')" width="120" height="12" src="images/{@id}-3.jpg" name="side.{@id}" hspace="0" vspace="0" border="0" alt="{@label}"/></a><br/>
      </xsl:if>
    </xsl:template>
  
    <xsl:template match="group">
      <xsl:if test="@id=/document/@id">
        <img width="120" height="12" src="images/{@id}-1.jpg" hspace="0" vspace="0" border="0" alt="{@label}" /><br/>
      </xsl:if>
      <xsl:if test="not(@id=/document/@id)">
        <a href="{@id}.html" onMouseOver="sideon('{@id}')" onMouseOut="sideoff('{@id}')">
        <img onLoad="sideload('{@id}')" width="120" height="12" src="images/{@id}-3.jpg" name="side.{@id}" hspace="0" vspace="0" border="0" alt="{@label}" /></a><br/>
      </xsl:if>
    </xsl:template>
  
    <xsl:template match="extern">
      <a href="{@href}" onMouseOver="sideon('{@id}')" onMouseOut="sideoff('{@id}')">
      <img onLoad="sideload('{@id}')" width="120" height="12" src="images/{@id}-3.jpg" name="side.{@id}" hspace="0" vspace="0" border="0" alt="{@label}" /></a><br/>
    </xsl:template>
  
  
  <!-- ###################################################################### -->
  <!-- document -->
  
    <xsl:template match="s1">
      <td width="500" valign="top" align="left">
          <xsl:apply-templates/>
      </td>
    </xsl:template>
  
    <xsl:template match="s2">
      <table border="0" width="100%"><tr>
        <td bgcolor="#0086b2" colspan="2">
          <font size="+1" face="arial,helvetica,sans-serif" color="ffffff"><b>
          &#160;<xsl:value-of select="@title"/></b></font>
        </td></tr><tr><td width="10"><xsl:comment> empty </xsl:comment></td>
        <td bgcolor="#ffffff"><xsl:apply-templates/></td></tr>
      </table>
      <br/>
    </xsl:template>
  
    <xsl:template match="s3">
      <table border="0" width="100%"><tr>
        <td bgcolor="#0086b2">
          <font face="arial,helvetica,sans-serif" color="ffffff"><b>
          &#160;<xsl:value-of select="@title"/></b></font>
        </td></tr><tr>
        <td bgcolor="#ffffff"><font size="-1"><xsl:apply-templates/></font></td></tr>
      </table>
      <br/>
    </xsl:template>
  
    <xsl:template match="s4">
      <table border="0" width="100%"><tr>
        <td bgcolor="#eeeeff">
          <font size="-1" face="arial,helvetica,sans-serif" color="ffffff"><b>
          &#160;<xsl:value-of select="@title"/></b></font>
        </td></tr><tr>
        <td bgcolor="#ffffff"><font size="-1"><xsl:apply-templates/></font></td></tr>
      </table>
      <br/>
    </xsl:template>
  
  <!-- ###################################################################### -->
  <!-- blocks -->
  
    <xsl:template match="em">
      <b><xsl:apply-templates/></b>
    </xsl:template>
  
    <xsl:template match="ref">
      <i><xsl:apply-templates/></i>
    </xsl:template>
    
    <xsl:template match="table">
      <table width="100%" border="0" cellspacing="2" cellpadding="2">
        <xsl:apply-templates/>
      </table>
    </xsl:template>
  
    <xsl:template match="tr">
      <tr><xsl:apply-templates/></tr>
    </xsl:template>
  
    <xsl:template match="th">
      <td bgcolor="#0086b2" valign="top" align="center">
        <font color="#ffffff"><b><xsl:apply-templates/></b></font>
      </td>
    </xsl:template>
  
    <xsl:template match="td">
      <td bgcolor="#eeeeff" valign="top" align="left"><xsl:apply-templates/>&#160;</td>
    </xsl:template>
  
    <xsl:template match="tn">
      <td>&#160;</td>
    </xsl:template>
  
    <xsl:template match="source">
      <table width="100%" border="0" cellspacing="0" cellpadding="0">
        <tr><td bgcolor="#0086b2"><img src="images/dot.gif" width="1" height="1"/></td></tr>
        <tr><td><pre><font size="-1"><xsl:apply-templates/></font></pre></td></tr>
        <tr><td bgcolor="#0086b2"><img src="images/dot.gif" width="1" height="1"/></td></tr>
       </table>
    </xsl:template>
  
    <xsl:template match="hr">
      <table width="100%" border="0" cellspacing="0" cellpadding="0">
        <tr><td bgcolor="#0086b2"><img src="images/dot.gif" width="1" height="1"/></td></tr>
       </table>
    </xsl:template>
  
    <xsl:template match="note">
      <p><xsl:apply-templates/></p>
    </xsl:template>
  
  <!-- ###################################################################### -->
  <!-- links -->
  
    <xsl:template match="link">
      <xsl:if test="@anchor=NULL">
        <xsl:if test="string-length(@idref)=0">
          <xsl:apply-templates/>
        </xsl:if>
        <xsl:if test="string-length(@idref)>0">
          <a href="{@idref}.html"><xsl:apply-templates/></a>
        </xsl:if>
      </xsl:if>
  
      <xsl:if test="not(@anchor=NULL)">
        <xsl:if test="string-length(@idref)=0">
          <a href="#{@anchor}"><xsl:apply-templates/></a>
        </xsl:if>
        <xsl:if test="string-length(@idref)>0">
          <a href="{@idref}.html#{@anchor}"><xsl:apply-templates/></a>
        </xsl:if>
      </xsl:if>
    </xsl:template>
  
    <xsl:template match="anchor">
      <a name="{@name}"><xsl:comment>anchor</xsl:comment></a>
    </xsl:template>
  
    <xsl:template match="jump">
      <a href="{@href}"><xsl:apply-templates/></a>
    </xsl:template>
  
  <!-- ###################################################################### -->
  <!-- copy -->
  
    <xsl:template match="@*|node()">
      <xsl:copy>
        <xsl:apply-templates select="@*|node()"/>
      </xsl:copy>
    </xsl:template>
  
  </xsl:stylesheet>
  
  
  1.1                  xml-0.0/docs/stylesheets/document2title.xsl
  
  Index: document2title.xsl
  ===================================================================
  <?xml version="1.0"?>
  
  <xsl:stylesheet xmlns:xsl="http://www.w3.org/XSL/Transform/1.0">
  
    <xsl:template match="/">
      <xsl:apply-templates/>
    </xsl:template>
  
    <xsl:template match="s1|faqs">
      <image width="456" height="35" bgcolor="0086b2">
        <text font="sanserif" size="29" x="454" y="8" halign="right" valign="top" color="004080"
              text="{@title}"/>
        <text font="sanserif" size="29" x="452" y="6" halign="right" valign="top" color="ffffff"
              text="{@title}"/>
      </image>
    </xsl:template>
  
  </xsl:stylesheet>
  
  
  1.1                  xml-0.0/docs/stylesheets/faq2document1.xsl
  
  Index: faq2document1.xsl
  ===================================================================
  <?xml version="1.0"?>
  
  <xsl:stylesheet xmlns:xsl="http://www.w3.org/XSL/Transform/1.0">
  
    <xsl:template match="/">
      <xsl:apply-templates/>
    </xsl:template>
  
    <xsl:template match="faq">
        <faqref  title="{@title}" position="{position()}"/>
        <faq title="{@title}" position="{position()}">
          <xsl:apply-templates/>
        </faq>
    </xsl:template>
  
  <!-- ###################################################################### -->
  <!-- copy -->
  
    <xsl:template match="@*|node()">
      <xsl:copy>
        <xsl:apply-templates select="@*|node()"/>
      </xsl:copy>
    </xsl:template>
  
  
  </xsl:stylesheet>
  
  
  1.1                  xml-0.0/docs/stylesheets/faq2document2.xsl
  
  Index: faq2document2.xsl
  ===================================================================
  <?xml version="1.0"?>
  
  <xsl:stylesheet xmlns:xsl="http://www.w3.org/XSL/Transform/1.0">
  
    <xsl:template match="/">
      <xsl:apply-templates/>
    </xsl:template>
  
    <xsl:template match="faqs">
      <s1 title="{@title}">
        <s2 title="{@title}: Questions">
          <ul><xsl:apply-templates select="faqref"/></ul>
        </s2>
        <s2 title="{@title}: Answers">
          <xsl:apply-templates select="faq"/>
        </s2>
      </s1>
    </xsl:template>
  
    <xsl:template match="faqref">
      <li><link anchor="{@position}"><xsl:value-of select="@title"/></link></li>
    </xsl:template>
  
    <xsl:template match="faq">
      <anchor name="{@position}"/>
      <s3>
        <xsl:apply-templates select="q"/>
        <xsl:apply-templates select="a"/>
      </s3>
    </xsl:template>
  
    <xsl:template match="q">
      <xsl:attribute name="title"><xsl:apply-templates/></xsl:attribute>
    </xsl:template>
  
    <xsl:template match="a">
      <xsl:apply-templates/>
    </xsl:template>
  
  <!-- ###################################################################### -->
  <!-- copy -->
  
    <xsl:template match="@*|node()">
      <xsl:copy>
        <xsl:apply-templates select="@*|node()"/>
      </xsl:copy>
    </xsl:template>
  
  
  </xsl:stylesheet>
  
  
  1.1                  xml-0.0/docs/stylesheets/faqs2document1.xsl
  
  Index: faqs2document1.xsl
  ===================================================================
  <?xml version="1.0"?>
  
  <xsl:stylesheet xmlns:xsl="http://www.w3.org/XSL/Transform/1.0">
  
    <xsl:template match="/">
      <xsl:apply-templates/>
    </xsl:template>
  
    <xsl:template match="document">
      <document id="{@id}">    
        <xsl:processing-instruction name="import">producer="project"</xsl:processing-instruction>
      <xsl:apply-templates select="child::book/group[attribute::id=@id]"/>
      </document>
    </xsl:template>
  
    <xsl:template match="hidden|chapter">
      <index id="{@id}">
        <xsl:processing-instruction name="import">producer="parser" source="<xsl:value-of select="@href"/>"</xsl:processing-instruction>
      </index>
      <xsl:apply-templates select="child::book/group[attribute::id=@id]"/>
    </xsl:template>
  
  </xsl:stylesheet>
  
  
  1.1                  xml-0.0/docs/stylesheets/faqs2document2.xsl
  
  Index: faqs2document2.xsl
  ===================================================================
  <?xml version="1.0"?>
  
  <xsl:stylesheet xmlns:xsl="http://www.w3.org/XSL/Transform/1.0">
  
    <xsl:template match="/">
      <xsl:apply-templates/>
    </xsl:template>
  
    <xsl:template match="document">
      <document id="{@id}">
        <xsl:apply-templates select="book"/>
        <s1 title="...">
          <xsl:apply-templates select="index"/>
        </s1>
      </document>
    </xsl:template>
    
    <xsl:template match="index">
        <xsl:apply-templates/>
    </xsl:template>
    
    <xsl:template match="faqs">
      <s2 title="{@title}">
        <ul><xsl:apply-templates/></ul>
      </s2>
    </xsl:template>
      
    <xsl:template match="faq">
      <li><link idref="{../../@id}" anchor="{position()+1}"><xsl:value-of select="@title"/></link></li>
    </xsl:template>
  
  <!-- ###################################################################### -->
  <!-- copy -->
  
    <xsl:template match="@*|node()">
      <xsl:copy>
        <xsl:apply-templates select="@*|node()"/>
      </xsl:copy>
    </xsl:template>
  
  </xsl:stylesheet>
  
  
  1.1                  xml-0.0/docs/stylesheets/group2title.xsl
  
  Index: group2title.xsl
  ===================================================================
  <?xml version="1.0"?>
  
  <xsl:stylesheet xmlns:xsl="http://www.w3.org/XSL/Transform/1.0">
  
    <xsl:template match="/">
      <xsl:apply-templates/>
    </xsl:template>
  
    <xsl:template match="context">
      <image width="456" height="35" bgcolor="0086b2">
        <text font="sanserif" size="29" x="454" y="8" halign="right" valign="top" color="004080"
              text="{@source}"/>
        <text font="sanserif" size="29" x="452" y="6" halign="right" valign="top" color="ffffff"
              text="{@source}"/>
      </image>
    </xsl:template>
  
  </xsl:stylesheet>
  
  
  1.1                  xml-0.0/docs/website/ack.xml
  
  Index: ack.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Credits">
  <s2 title="Credits">
      <p>
         A collaborative project like this doesn't exist in a vacuum. In order to keep project
         like this running, you need support and help. The <em>xml.apache.org</em> project has been
         fortunate to have the support of the following:
      </p>
      <ul> 
          <li><jump href="http://www.apache.org">The Apache Group</jump><br/>
          <p>
           The xml.apache.org project operates as an Official Project under the Apache
           umbrella. It abides by the same principles and operating procedures as the parent
           organization.
          </p>
          </li>
      
          <li><jump href="http://www.ibm.com">IBM</jump><br/>
          <p>
           IBM provided the initial code base for Xerces (Java, C++, and Perl versions), as
           well as ongoing support for this and other Apache projects (e.g. the Apache HTTP server).
          </p>
          </li>
  
          <li><jump href="http://www.lotus.com">Lotus</jump><br/>
          <p>
           Lotus provided the initial code base for Xalan (Java and C++ versions).
          </p>
          </li>
  
          <li><jump href="http://www.sun.com">Sun Microsystems, Inc.</jump><br/>
          <p>
            Sun will be contributing their ProjectX and XHTML parser technologies.
          </p>
          </li>
  
          <li><jump href="http://www.exoffice.com">Exoffice</jump><br/>
          <p>
            Exoffice will be contributing their OpenXML and XSL:P technologies.
          </p>
          </li>
  
          <li><jump href="http://www.hyperreal.com">Hyperreal</jump>
          <p>
            Hyperreal is the server that this site is served from.
          </p>
          </li>
  
          <li><jump href="http://www.above.net">Above.Net</jump>
          <p>
            Above.Net provides the network bandwidth for the Apache websites.
          </p>
          </li>
      </ul> 
  </s2>
  </s1>
  
  
  
  1.1                  xml-0.0/docs/website/communication.xml
  
  Index: communication.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Communication">
    <s2 title="Communication">
      <p>
        The Project obtains its strength from the communication of its 
        members. In order for members to easily communicate with each other, 
        the Project has a variety of mailing lists. These lists, with the 
        exception of the announcement lists, are not moderated and anybody is 
        more than welcome to join them. However, you must be subscribed to 
        post to a list.
      </p>
      <p>
        To reduce the bandwidth demands on everyone, mail should not contain 
        attachments. It is recommended that you place interesting material 
        (such as patches) either within the body of the message or provide a 
        URL for retrieval.
      </p>
      <p>
        To join the mailing lists, see our <link idref="mail">Mailing List</link>
        page.
      </p>
      <p>
        The Project's list fall into the following categories:
      </p>
    </s2>
    <s2 title="Announcement Lists">
      <p>
        Announcement lists are very low traffic designed to communicate 
        important information, such as final releases of a subproject's 
        code, to a wide audience.
      </p>
    </s2>
    <s2 title="User Lists">
      <p>
        User lists are for users of a product to converse about such things 
        as configuration and operating of the products of the Project.
      </p>
    </s2>
    <s2 title="Developer Lists">
      <p>
        Developer lists are for the developers of the project. On these 
        lists suggestions and comments for code changes are discussed and 
        action items are raised and voted on. For the developer community, 
        these lists are the very center of the project where all the 
        "action" is.
      </p>
    </s2>
    <s2 title="Commit Lists">
      <p>
        The commit lists are where all cvs code commit messages are sent. 
        All committers are required to subscribe to this list so that they 
        can stay aware of changes to the repository. 
      </p>
    </s2>
  </s1>
  
  
  
  1.1                  xml-0.0/docs/website/contact.xml
  
  Index: contact.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Contact Info">
  <s2 title="Contact Info">
      <p>
          If you have questions or comments about this site, please send email to:
  
          <jump href="mailto:webmaster@xml.apache.org">webmaster@xml.apache.org</jump>   
      </p>
      <p>
      The xml.apache.org project is an effort of the Apache Software Foundation. The
      address for general ASF correspondence and licensing questions is:
  
                     <jump href="mailto:apache@apache.org">apache@apache.org</jump>
  
                     You can find more contact information for the Apache Software Foundation on the
                     contact page of the <jump href="http://www.apache.org/">main Apache site</jump>. 
      </p>
  </s2>
  </s1>
  
  
  
  1.1                  xml-0.0/docs/website/cvs.xml
  
  Index: cvs.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="CVS Repositories">
  
      <s2 title="Web Access to the Repository">
      <p>You can browse the xml.apache.org workspaces via the web.
      </p>
      <ul>
          <li><jump href="http://www.apache.org/websrc/cvsweb.cgi/xml-xerces">xml-xerces-workspace</jump></li>
          <li><jump href="http://www.apache.org/websrc/cvsweb.cgi/xml-xalan">xml-xalan-workspace</jump></li>
          <li><jump href="http://www.apache.org/websrc/cvsweb.cgi/xml-cocoon">xml-cocoon-workspace</jump></li>
          <li><jump href="http://www.apache.org/websrc/cvsweb.cgi/xml-fop">xml-fop-workspace</jump></li>
      </ul>
      </s2>
  
      <s2 title="Download the Source">
      <p> Most users of the source code probably don't need to have day to day access to
                     the source code as it changes. For these users we provide easy to unpack source
                     code downloads via our download pages.
      </p>
      </s2>
  
      <s2 title="Access the Source Tree">
          <p>
          So, you've decided that you need access to the source tree to see the latest and
                     greatest code. There's two different forms of CVS access. The first is anonymous
                     and anybody can use it. The second is not and you must have a login to the
                     development server. If you don't know what this means, join the mailing list and find
                     out.
          </p>
          <s3 title="AnonCVS">
              <p> Anyone can checkout source code from our anonymous CVS server. To do so,
                     simply use the following commands (if you are using a GUI CVS client, configure it
                     appropriately):
              </p>
              <source>
  cvs -d :pserver:anoncvs@dev.apache.org:/home/cvspublic
  login
  password: anoncvs
  
  cvs -d :pserver:anoncvs@dev.apache.org:/home/cvspublic
  checkout [module-name]
              </source>
              <p>
              Modules available for access are:
              <ul>
                 <li>xml-xerces</li>
                 <li>xml-xalan</li> 
                 <li>xml-cocoon</li> 
                 <li>xml-fop</li> 
              </ul>
              </p>
          </s3>
      </s2>
  
      <s2 title="Other Ways to Access the Source Code">
      <p>
      For some, using CVS pserver might not be enough. You can access the
                     xml.apache.org source modules via CVSup or Rsync. For more information about
                     how to use these tools with the Apache CVS tree, 
                     see the <jump href="http://www.apache.org/info/how-to-mirror.html">Apache Mirroring Document</jump>. 
      </p>
      </s2>
  
  </s1>
  
  
  
  1.1                  xml-0.0/docs/website/decisions.xml
  
  Index: decisions.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Decision Making">
    <s2 title="Decision Making">
      <p>
        All <link idref="roles">Developers</link> are encouraged to 
        participate in decisions, but the decision itself is made by those 
        that have <link idref="roles">Committer</link> status in the Project. 
        In other words, the Project is a "Minimum Threshold Meritocracy".
      </p>
      <p>
        Any Developer may vote on any issue or action item. However, the only 
        binding votes are those cast by a Committer. If the vote is about a 
        change to the source code or documentation and the primary author is a 
        Developer and not a Commiter, the primary author of what is being 
        changed may also cast a binding vote on that issue.
      </p>
      <p>
        The act of voting carries certain obligations. Voting members are not 
        only stating their opinion, they are also agreeing to help do the 
        work.
      </p>
      <p>
        Each vote can be made in one of three flavors:
      </p>
      <ul>
        <li><em>+1</em> - "Yes," "Agree," or "the action should be performed." 
          On some issues this is only binding if the voter has tested the action 
          on their own system(s).</li>
        <li><em>+/-0</em> - "Abstain," "no opinion". An abstention may have 
          detrimental effects if too many people abstain.</li>
        <li><em>-1</em> - "No." On issues where consensus is required, this 
        vote counts as a <em>veto</em>. All vetos must contain an explanation 
        of why the veto is appropriate. Vetos with no explanation are void. No 
        veto can be overruled. If you disagree with the veto, you should lobby 
        the person who cast the veto. Voters intending to veto an action item 
        should make their opinions known to the group immediately so that the 
        problem can be remedied as early as possible.</li>
      </ul>
      <p>
        An action requiring consensus approval must receive at least <em>3 
        binding +1</em> votes and no binding <em>vetos</em>. An action 
        requiring majority approval must receive at least <em>3 binding +1 
        votes</em> and <em>more +1</em> votes than -1 votes. All other action 
        items are considered to have lazy approval until somebody votes <em>-
        1</em>, after which point they are decided by either consensus or 
        majority vote, depending on the type of action item.
      </p>
    </s2>
  
    <s2 title="Action Items">
      <p>
        All decisions revolve around "Action Items." Action Items consist of 
        the following:
      </p>
      <ul>
        <li>Long Term Plans</li> 
        <li>Short Term Plans</li> 
        <li>Release Plan</li> 
        <li>Release Testing</li> 
        <li>Showstoppers</li> 
        <li>Product Changes</li> 
      </ul>
      <s3 title="Long Term Plans">
        <p>
          Long term plans are simply announcements that group members are 
          working on particular issues related to the Project. These are not 
          voted on, but Developers who do not agree with a particular plan, or 
          think that an alternative plan would be better, are obligated to 
          inform the group of their feelings.
        </p>
      </s3>
      <s3 title="Short Term Plans">
        <p>
          Short term plans are announcements that a developer is working on a 
          particular set of documentation or code files with the implication 
          that other developers should avoid them or try to coordinate their 
          changes.
        </p>
      </s3>
      <s3 title="Release Plan">
        <p>
          A release plan is used to keep all Developers aware of when a 
          release is desired, who will be the release manager, when the 
          repository will be frozen to create a release, and other assorted 
          information to keep Developers from tripping over each other. Lazy 
          majority decides each issue in a release plan.
  
        </p>
      </s3>
      <s3 title="Release Testing">
        <p>
          After a new release is built, it must be tested before being 
          released to the public. Majority approval is required before the 
          release can be made.
        </p>
      </s3>
      <s3 title="Showstoppers">
        <p>
          Showstoppers are issues that require a fix be in place before the 
          next public release. They are listed in the status file in order to 
          focus special attention on these problems. An issue becomes a 
          showstopper when it is listed as such in the status file and remains 
          so by lazy consensus.
        </p>
      </s3>
      <s3 title="Product Changes">
        <p>
          Changes to the products of the Project, including code and 
          documentation, will appear as action items in the status file. All 
          product changes to the currently active repository are subject to 
          lazy consensus. 
        </p>
      </s3>
    </s2>
  </s1>
  
  
  
  1.1                  xml-0.0/docs/website/guidelines.xml
  
  Index: guidelines.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Project Guidelines">
    <s2 title="The xml.apache.org Project Guidelines">
      <p>
        This document defines the guidelines of the <em>xml.apache.org</em> 
        project. It includes definitions of the various categories of 
        membership, who is able to vote, how conflicts are resolved by voting, 
        and the procedures to follow for proposing and making changes to the 
        codebase of the Project.
      </p>
      <p>
        This is a living document. Changes can be made by the Project 
        Management Committee. 
      </p>
      <ul>
        <li><em><link idref="roles">Roles and Responsibilities</link></em>
          Defines the recognized roles in the project.</li>
        <li><em><link idref="communication">Communication</link></em>
          Defines how users and developers communicate.</li>
        <li><em><link idref="decisions">Decision Making</link></em>
          Defines how action items are proposed and voted on.</li>
        <li><em><link idref="source">Source Repositories</link></em>
          Defines how the Project's source code is organized and developed.</li>
        <li><em><link idref="management">Project Management</link></em>
          Defines the roles and responsibilities of the Project Management
          Committee (PMC).</li>
      </ul>
    </s2>
  </s1>
  
  
  
  1.1                  xml-0.0/docs/website/index.xml
  
  Index: index.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="xml.apache.org">
    <s2 title="Welcome to the Apache XML Project">
      <p>
        The goals of the <em>Apache XML Project</em> project are:
      </p>
      <ul>
        <li>
          to provide commercial-quality standards-based XML solutions that are 
          developed in an open and cooperative fashion, 
        </li>
        <li>
          to provide feedback to standards bodies (such as IETF and W3C) from an 
          implementation perspective, and 
        </li>
        <li>
          to be a focus for XML-related activies within Apache projects 
        </li>
      </ul>
      <p>
        The <em>Apache XML Project</em> project currently consists of four sub- 
        projects, each focused on a different aspect of XML:
      </p>
      <ul>
        <li>
          <em>Xerces</em> - XML parsers in Java, C++, and Perl
        </li> 
        <li>
          <em>Xalan</em> - XSLT stylesheet processors, in Java and C++ 
        </li> 
        <li>
          <em>Cocoon</em> - XML-based web publishing, in Java 
        </li> 
        <li>
          <em>FOP</em> - XSL formatting objects, in Java 
        </li> 
      </ul>
      <s3 title="Xerces: XML parsers in Java, C++, and Perl">
        <p>
          Xerces (named after the Xerces Blue butterfly) provides world-class 
          XML parsing and generation. Fully-validating parsers are available for 
          both Java and C++, implementing the W3C XML and DOM (Level 1 and 2) 
          standards, as well as the defacto SAX (version 2) standard. The 
          parsers are highly modular and configurable. Initial support for XML 
          Schema (draft W3C standard) is also provided.
        </p>
        <p>
          A Perl wrapper is provided for the C++ version of Xerces, which allows 
          access to a fully validating DOM XML parser from Perl. It also 
          provides for full access to Unicode strings, since Unicode is a key 
          part of the XML standard.
        </p>
        <p>
          The Xerces implementations are currently in beta form. We are working 
          on merging contributions from the initial contributors into a unified 
          code base. We expect to have a usable release of Xerces by the end of 
          1999.
        </p>
      </s3>
  
      <s3 title="Xalan: XSL stylesheet processors in Java &amp; C++">
        <p>
          Xalan (named after a rare musical instrument) provides high-
          performance XSL stylesheet processing. Xalan fully implements the W3C 
          XSLT recommendation. The stylesheet processor is feature-rich and 
          robust.
        </p>
        <p>
          Xalan is currently available in beta form in Java. We are working on 
          merging contributions from the initial contributors into a unified 
          code base. We expect to have a usable Java release of Xalan by the end 
          of 1999. The schedule for the C++ release is TBD.
        </p>
      </s3>
  
      <s3 title="Cocoon: XML-based web publishing">
        <p>
          Cocoon is a powerful framework for XML web publishing which brings a whole 
          new world of abstraction and ease to consolidated web site creation and
          management based on the XML paradigm and related technologies.
        </p>
      </s3>
  
      <s3 title="FOP: XSL Formatting Object processor in Java">
        <p>
          FOP is the world's first print formatter driven by XSL formatting 
          objects. It is a Java 1.1 application that reads a formatting object 
          tree and then turns it into a PDF document. The formatting object 
          tree, can be in the form of an XML document (output by an XSLT 
          engine like Xalan) or can be passed in memory as a DOM Document or (in 
          the case of Xalan) SAX events.
        </p>
      </s3>
    </s2>
  
    <s2 title="Anyone Can Participate">
      <p>
        The <em>xml.apache.org</em> Project is composed of developers from all
        around the world, both individuals and engineers from major corporations.
        All interested developers are welcome to join and participate. Learn more
        about <link idref="overview">how to get involved</link>. 
      </p>
    </s2>
  </s1>
  
  
  
  1.1                  xml-0.0/docs/website/legal.xml
  
  Index: legal.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Legal Stuff">
  <s2 title="They made us say this">
      <p>
          All material on this website is Copyright (c) 1999 The Apache Software Foundation.
          All Rights Reserved.
      </p>
      <p>
                     IBM is a trademark of International Business Systems, Inc. Lotus is a trademark of
                     Lotus Development Corporation. Sun and Sun Microsystems are trademarks or
                     registered trademarks of Sun Microsystems, Inc. UNIX is a registered trademark in
                     the United States and other countries, exclusively licensed through X/Open
                     Company, Ltd. Windows, WindowsNT, and Win32 are registered trademarks of
                     Microsoft Corp. All other product names mentioned herein and throughout the
                     entire web site are trademarks of their respective owners.
      </p>
  </s2>
  </s1>
  
  
  
  1.1                  xml-0.0/docs/website/library.xml
  
  Index: library.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Reference Library">
  <s2 title="Reference Library">
      <p>
      The <em>xml.apache.org</em> project lives or fails based on its human resources. Users and
      contributors alike help the project with ideas and brainpower. A common
      foundation of knowledge is required to effectively participate in this virtual
      community. The following is a list of documents that we have found helpful for us
      and may be helpful to you:
      </p>
  
  </s2>
      <s2 title="Technical Resources">
      <p>
        These resources are required reading for anybody contributing source code to the
        project.
      </p>
      <ul>
        <li><jump href="http://java.sun.com/docs/books/jls/index.html">The Java Language Specification</jump><br/>
          <p>Written by the creators of the Java Programming Language, this online book is
                      considered by many to be the bible for programming in Java. A must read.
          </p>
        </li>
        <li><jump href="http://java.sun.com/products/jdk/javadoc/index.html">Javadoc</jump><br/>
          <p>Javadoc is the automatic software documentation generator used by Java since it
                      was first released. All Java code written for this project must be documented using
                      Javadoc conventions. 
          </p>
        </li>
        <li><jump href="http://www.cyclic.com/cvs/doc-blandy.html">Introduction to CVS</jump><br/>
          <p>Written by Jim Blandy, this brief introduction gives a first look into CVS. If you
                      have never used CVS before, you'll want to start here. 
          </p>
        </li>
        <li><jump href="http://www.cyclic.com/cvs/doc-cederqvist.html">Version Management with CVS</jump><br/>
          <p>Written by Per Cederqvist at al, this is the main manual for CVS. It provides details
                      on all documented CVS features. 
          </p>
        </li>
      </ul>
      </s2>
  
      <s2 title="Source Code Philosophy Resources">
      <p> 
          The following are a set of articles written about the recent source code movements
          that help illustrate some of the attributes of a collaborative project such as this. You
          may not agree with all of the points of these articles, but an understanding of them
          will help in communicating with everyone on the project.
      </p>
      <ul>
        <li><jump href="http://www.tuxedo.org/%7Eesr/writings/cathedral-bazaar/index.html">The Cathedral and the Bazaar</jump><br/>
          <p>Written by Eric S. Raymond, this is a must read for anyone willing to join or
                      support a volunteer project.
          </p>
        </li>
        <li><jump href="http://www.tuxedo.org/%7Eesr/writings/homesteading/index.html">Homesteading the Noosphere</jump><br/>
          <p>Written by Eric S. Raymond, this is a sequel to "The Cathedral and the Bazaar". It
                      details the property and ownership customs of the open-source culture. This
                      analysis has larg implications for anyone interested in organizing large-scale
                      intellectual collaborations such as this project. 
          </p>
        </li>
      </ul>
      </s2>
  
  </s1>
  
  
  
  1.1                  xml-0.0/docs/website/mail.xml
  
  Index: mail.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Mailing Lists">
  <s2 title="Mailing Lists">
  
      <p>
      Every volunteer project obtains its strength from the people involved in it. Mailing
      lists provide a simple and effective communication mechanism.
  
      You are welcome to join any of these mailing lists (or all of them if you wish). You
      can choose to lurk, or actively participate. It's up to you. Before you join these lists,
      you should look over the resources in the Reference Library section.
      </p>
  </s2>
      <s2 title="The xml.apache.org Announcement List">
      <p>
          <em>Low Traffic</em>
          <jump href="mailto:announcements-subscribe@xml.apache.org">Subscribe</jump>
          <jump href="mailto:announcements-unsubscribe@xml.apache.org">Unsubscribe</jump>
      </p>
      <p>
          If you want to keep informed about what we are up to but you do not have the time
          to read all the messages on the other mailing lists, subscribe to this moderated list to
          get general announcements.
      </p>
      </s2>
  
      <s2 title="The xml.apache.org General Discussion List">
      <p>
          <em>Medium Traffic</em>
          <jump href="mailto:general-subscribe@xml.apache.org">Subscribe</jump>
          <jump href="mailto:general-unsubscribe@xml.apache.org">Unsubscribe</jump>
      </p>
      <p>
          This list is for issues that span across all xml.apache.org projects. Discussions
                  about specific code bases should be redirected to one of the codebase-specific
                  lists below.
      </p>
      </s2>
  
  
      <s2 title="The Xerces Developer List">
      <p>
          <em>Medium Traffic</em>
          <jump href="mailto:xerces-dev-subscribe@xml.apache.org">Subscribe</jump>
          <jump href="mailto:xerces-dev-unsubscribe@xml.apache.org">Unsubscribe</jump>
      </p>
      <p>
          This is the list where participating developers of the Xerces XML parsers meet and
          discuss issues, code changes/additions, etc. Subscribers to this list get notices of
          each and every code change, build results, testing notices, etc.
      </p>
      </s2>
  
      <s2 title="The Xalan Developer List">
      <p>
          <em>Medium Traffic</em>
          <jump href="mailto:xalan-dev-subscribe@xml.apache.org">Subscribe</jump>
          <jump href="mailto:xalan-dev-unsubscribe@xml.apache.org">Unsubscribe</jump>
      </p>
      <p>
          This is the list where participating developers of the Xalan XSLT stylesheet processor meet and
          discuss issues, code changes/additions, etc. Subscribers to this list get notices of
          each and every code change, build results, testing notices, etc.
      </p>
      </s2>
  
      <s2 title="The Cocoon Developer List">
      <p>
          <em>Medium Traffic</em>
          <jump href="mailto:cocoon-dev-subscribe@xml.apache.org">Subscribe</jump>
          <jump href="mailto:cocoon-dev-unsubscribe@xml.apache.org">Unsubscribe</jump>
      </p>
      <p>
          This is the list where participating developers of Cocoon meet and
          discuss issues, code changes/additions, etc. Subscribers to this list get notices of
          each and every code change, build results, testing notices, etc.
      </p>
      </s2>
  
      <s2 title="The FOP Developer List">
      <p>
          <em>Medium Traffic</em>
          <jump href="mailto:fop-dev-subscribe@xml.apache.org">Subscribe</jump>
          <jump href="mailto:fop-dev-unsubscribe@xml.apache.org">Unsubscribe</jump>
      </p>
      <p>
          This is the list where participating developers of FOP XSL-FO Formatting Objects
          processor meet and
          discuss issues, code changes/additions, etc. Subscribers to this list get notices of
          each and every code change, build results, testing notices, etc.
      </p>
      </s2>
  
  
  </s1>
  
  
  
  1.1                  xml-0.0/docs/website/management.xml
  
  Index: management.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Project Management">
    <s2 title="Project Management Committee (PMC) Bylaws">
      <p>
        The Project Management Committee (PMC) was formed by the Apache Board 
        in September 1999. This Committee consists of X founding members, one 
        of whom is the founding Chairman. The term of the Chairman is one 
        year. There is no term limit for members. The list of current members 
        can be found in our <link idref="whoweare">Project Credits</link>.
      </p>
      <s3 title="Roles">
        <p>
          The PMC is responsible for the strategic direction and success of 
          the <em>xml.apache.org</em> Project. This governing body is expected 
          to ensure the project's welfare and guide its overall direction. The 
          PMC may not necessarily participate in the day-to-day coding but is 
          involved in the overall development plans, the alleviation of any 
          bottlenecks, the resolution of conflicts, and the overall technical 
          success of the project.
        </p>
        <p>
          The PMC is answerable to the Apache Board with its Chairman serving 
          as primary liaison.
        </p>
      </s3>
      <s3 title="Meetings">
        <p>
          The PMC meets monthly with a majority of its members to discuss 
          issues, determine strategic direction, and forward progress. These 
          meetings may take place online, via teleconference, or via other 
          means deemed effective by the PMC. The PMC has an annual meeting at 
          which time a new Chairman is elected. The old Chairman maintains 
          membership status.
        </p>
      </s3>
      <s3 title="Membership">
        <p>
          PMC members may resign at any time. The Chairman may resign as 
          Chairman at any time without resigning membership to the PMC. The 
          Chairman or any member may be removed from the PMC by a 3/4 vote of 
          the PMC.
        </p>
      </s3>
      <p>
        New members may be elected to the PMC. In order to be elected, a 
        person must have served as a Committer and be nominated by a PMC 
        Member. Once nominated, all of the PMC will vote and those receiving a 
        3/4 positive vote will become a member.
      </p>
    </s2>
  </s1>
  
  
  1.1                  xml-0.0/docs/website/mission.xml
  
  Index: mission.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Project Mission">
    <s2 title="Mission">
      <p>
        The mission of the <em>xml.apache.org</em> project is:
      </p>
      <ul>
        <li>
          to provide commercial-quality standards-based XML solutions that are 
          developed in an open and cooperative fashion,
        </li> 
        <li>
          to provide feedback to standards bodies (such as IETF and W3C) from 
          an implementation perspective, and
        </li> 
        <li>
          to be a focus for XML-related activies within Apache projects
        </li>
      </ul>
      <p>
  
        The <em>xml.apache.org</em> project currently consists of four sub-projects, each focused on a different aspect
  of XML:</p>
  <ul>
          <li><em>Xerces</em> -- XML parsers in Java, C++, and Perl
        </li> 
          <li><em>Xalan</em> -- XSL stylesheet processors, in Java and C++
        </li> 
          <li><em>Cocoon</em> -- XML-based web publishing, in Java
        </li> 
          <li><em>Fop</em> -- XSL formatting objects, in Java
        </li> 
  </ul>
                        
    </s2>
  </s1>
  
  
  
  1.1                  xml-0.0/docs/website/news.xml
  
  Index: news.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="News and Status">
  
    <s2 title="Xerces status: Source Code and Binaries Available">
      <p>
        Xerces XML parsers in Java, C++, and Perl are currently available in 
        source code and binary form. Check out the
        <jump href="/dist/">download pages</jump> for binaries 
        and source!
      </p>
    </s2>
  
  
    <s2 title="Xalan Status: Source Code and Binaries Available">
      <p>
        Xalan XSLT stylesheet processor in Java is currently available in 
        source code and binary form. Check out the
        <jump href="/dist/">download pages</jump> for binaries and
        source!
      </p>
    </s2>
  
    <s2 title="Cocoon Status: Source Code and Binaries Available Soon">
      <p>
        Cocoon, the XML-based web publishing solution in Java, will be available
        here soon.
      </p>
    </s2>
  
    <s2 title="FOP Status: Source Code Available Soon">
      <p>
        FOP, the XSL:FO formatting objects processor in Java, will be available
        here soon.
      </p>
    </s2>
  
    <s2 title="In the News">
      <ul>
        <li>
          Apache forms xml.apache.org --
          <jump href="http://xml.apache.org/pr/0001.txt">PRESS RELEASE</jump>
        </li>
        <li>
          CNet Article on xml.apache.org --
          <jump href="http://news.cnet.com/news/0-1003-200-1431504.html?tag=st.ne.1002.thed.1003-200-1431504">ARTICLE</jump>
        </li>
        <li>
          SlashDOT comments on xml.apache.org --
          <jump href="http://www.slashdot.org/index.pl?section=apache">COMMENTS</jump>
        </li>
      </ul>
    </s2>
  
  </s1>
  
  
  
  1.1                  xml-0.0/docs/website/overview.xml
  
  Index: overview.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Get Involved!">
  <s2 title="Get Involved!">
      <p>Every volunteer project obtains its strength from the people involved in it. We invite
                     you to participate as much or as little as you choose. The roles and responsibilities
                     that people can assume in the project are based on merit. Everybody's input
                     matters!
      </p>
      <p>There are a variety of ways to participate. Regardless of how you choose to
                     participate, we suggest you join some or all of our <link idref="mail">mailing lists</link>.
      </p>
  
      <s3 title="Use the Products and Give Us Feedback">
      <p>Using the products,reporting bugs, making feature requests, etc. is by far the most
                     important role. It's your feedback that allows the technology to evolve.
      </p>
      <ul>
          <li>join <link idref="mail">mailing lists</link></li>
          <li><jump href="/dist/">Download binary builds</jump></li>
          <li>Report bugs/Request additional features</li>
      </ul>
      </s3>
      <s3 title="Contribute Code or Documentation Patches">
      <p>In this role, you participate in the actual development of the code. If this is the type
                     of role you'd like to play, here are some steps (in addition to the ones above) to get
                     you started:
      </p>
      <ul>
          <li><link idref="guidelines">Read Guidelines</link></li>
          <li><link idref="library">Review Reference Library</link></li>
          <li><jump href="/dist/">Download the source code</jump></li>
          <li><link idref="cvs">Access the CVS repository</link></li>
      </ul>
      </s3>
      </s2>
  </s1>
  
  
  
  1.1                  xml-0.0/docs/website/roles.xml
  
  Index: roles.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Roles and Responsibilities">
    <s2 title="Roles and Responsibilities">
      <p>
        The roles and responsibilities that people can assume in the project 
        are based on merit. Everybody can help no matter what their role. 
        Those who have been long term or valuable contributors to the project 
        obtain the right to vote and commit directly to the source repository.
      </p>
    </s2>
    <s2 title="Users">
      <p>
        Users are the people who use the products of the Project. People in 
        this role aren't contributing code, but they are using the products, 
        reporting bugs, making feature requests, and such. This is by far 
        the most important category of people as, without users, there is no 
        reason for the Project.
      </p>
      <p>
        When a user starts to contribute code or documentation patches, they
        become a developer.
      </p>
    </s2>
    <s2 title="Developers">
      <p>
        Developers are the people who write code or documentation patches or 
        contribute positively to the project in other ways. A developer's 
        contribution is always recognized. In source code, all developers 
        who contribute to a source file may add their name to the list of 
        authors for that file.
      </p>
    </s2>
    <s2 title="Committers">
      <p>
        Developers who give frequent and valuable contributions to a 
        subproject of the Project can have their status promoted to that of 
        a "Committer" for that subproject. A Committer has write access to 
        the source code repository and gains voting rights allowing them to 
        affect the future of the subproject.
      </p>
      <p>
        In order for a Developer to become a Committer, another Committer 
        can nominate that Developer or the Developer can ask for it. Once a 
        Developer is nominated, all of the Committers for a subproject will 
        vote. If there are at least 3 positive votes and no negative votes, 
        the Developer is converted into a Committer and given write access 
        to the source code repository for that subproject.
      </p>
      <p>
        At times, Committers may go inactive for a variety of reasons. A 
        Committer that has been inactive for 6 months or more may lose his 
        or her status as a Committer.
      </p>
      <p>
        A list of our current Committers can be found in our
        <link idref="whoweare">Project Credits</link>.
      </p>
    </s2>
    <s2 title="Project Management Committee (PMC)">
      <p>
        Committers who frequently participate with valuable contributions 
        may have their status promoted to that of a "Project Management 
        Committee Member". This committee is the official managing body of 
        the xml.apache.org Project and is responsible for setting overall 
        project direction. In order to become a Member, someone on the PMC 
        must nominate the Committer. The individual may then be approved 
        with a 3/4 majority of the PMC.
      </p>
      <p>
        To view the Project Management Committee bylaws, 
        <link idref="management">click here</link>.
      </p>
      <p>
        A list of our current PMC Members can be found in our 
        <link idref="whoweare">Project Credits</link>.
      </p>
    </s2>
  </s1>
  
  
  
  1.1                  xml-0.0/docs/website/source.xml
  
  Index: source.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Source Repositories">
    <s2 title="Source Repositories">
      <p>
        The Project's codebase is maintained in shared information 
        repositories using CVS on the dev.apache.org machine. Only Committers 
        have write access to these repositories. Everyone has read access via 
        anonymous CVS.
      </p>
      <p>
        All Java Language source code in the repository must be written in 
        conformance to the
        <jump href="http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html">Code
        Conventions for the Java Programming Language</jump> as published by 
        Sun.
      </p>
    </s2>
    <s2 title="License">
      <p>
        All source code committed to the Project's repositories must be 
        covered by the <em>Apache License version 1.1</em>
        or contain a copyright and license that allows 
        redistribution under the same conditions as the Apache License.
      </p>
    </s2>
    <s2 title="Status Files">
      <p>
        Each of the Project's active source code repositories contain a file 
        named <em>STATUS</em> which is used to keep track of the agenda and 
        plans for work within that repository. The status file includes 
        information about release plans, a summary of code changes committed 
        since the last release, a list of proposed changes that are under 
        discussion, brief notes about items that individual developers are 
        working on or want discussion about, and anything else that may be 
        useful to help the group track progress.
      </p>
      <p>
        The active status files are automatically posted to the developer 
        mailing lists three times per week.
      </p>
    </s2>
    <s2 title="Branches">
      <p>
        Groups are allowed to create a branch for release cycles, etc. They 
        are expected to merge completely back with the main branch as soon as 
        their release cycle is complete.
      </p>
    </s2>
    <s2 title="Changes">
      <p>
        Simple patches to fix bugs can be committed then reviewed. With a 
        commit-then-review process, the Committer is trusted to have a high 
        degree of confidence in the change.
      </p>
      <p>
        Doubtful changes, new features, and large scale overhauls need to be 
        discussed before committing them into the repository. Any change that 
        affects the semantics of an existing API function, the size of the 
        program, configuration data formats, or other major areas must receive 
        consensus approval before being committed.
      </p>
      <p>
        Related changes should be committed as a group, or very closely 
        together. Half complete projects should never be committed to the main 
        branch of a development repository. All code changes must be 
        successfully compiled on the developer's platform before being 
        committed.
      </p>
      <p>
        The current source code tree for a subproject should be capable of 
        complete compilation at all times. However, it is sometimes impossible 
        for a developer on one platform to avoid breaking some other platform 
        when a change is committed. If it is anticipated that a given change 
        will break the build on some other platform, the committer must 
        indicate that in the commit message.
      </p>
      <p>
        A committed change must be reversed if it is vetoed by one of the 
        voting members and the veto conditions cannot be immediately satisfied 
        by the equivalent of a "bug fix" commit. The veto must be rescinded 
        before the change can be included in any public release.
      </p>
    </s2>
    <s2 title="Patches">
      <p>
        When a specific change to a product is proposed for discussion or 
        voting on the appropriate development mailing list, it should be 
        presented in the form of input to the patch command. When sent to the 
        mailing list, the message should contain a Subject beginning with 
        [PATCH] and a distinctive one-line summary corresponding to the action 
        item for that patch.
      </p>
      <p>
        The patch should be created by using the diff -u command from the 
        original software file(s) to the modified software file(s). For 
        example:
      </p>
      <p>
        <code>diff -u Main.java.orig Main.java &gt;&gt; patchfile.txt</code>
      </p>
      <p>
        or
      </p>
      <p>
        <code>cvs diff -u Main.java &gt;&gt; patchfile.txt</code>
      </p>
      <p>
        All patches necessary to address an action item should be 
        concatencated within a single patch message. If later modification to 
        the patch proves necessary, the entire new patch should be posted and 
        not just the difference between the two patches.
      </p>
    </s2>
  </s1>
  
  
  
  1.1                  xml-0.0/docs/website/whoweare.xml
  
  Index: whoweare.xml
  ===================================================================
  <?xml version="1.0"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Who We Are">
    <s2 title="Who We Are">
      <p>
          The <em>xml.apache.org</em> project operates on a meritocracy: the more you do, the more
          responsibility you will obtain. This page lists all of the people who have gone the
          extra mile and are Committers or members of the Project Management Committee.
          If you would like to get involved, the first step is to join the <link idref="mail">mailing lists</link>.
      </p>
    </s2>
      <s2 title="Project Management Committee">
          <ul>
           <li>Scott Boag
            <jump href="mailto:scott_boag@lotus.com">scott_boag@lotus.com</jump></li>
           <li>Tim Bray
            <jump href="mailto:tbray@textuality.com">tbray@textuality.com</jump></li>
           <li>Larry Cable
            <jump href="mailto:larry.cable@eng.sun.com">larry.cable@eng.sun.com</jump></li>
           <li>Mike Dierken
            <jump href="mailto:mike@datachannel.com">mike@datachannel.com</jump></li>
           <li>Andy Heninger
            <jump href="mailto:heninger@apache.org">heninger@apache.org</jump></li>
           <li>Ted Leung
            <jump href="mailto:twl@apache.org">twl@apache.org</jump></li>
           <li>Stefano Mazzocchi
            <jump href="mailto:stefano@apache.org">stefano@apache.org</jump></li>
           <li>Mike Pogue 
            <jump href="mailto:mpogue@apache.org">mpogue@apache.org</jump></li>
           <li>James Tauber 
            <jump href="mailto:jtauber@jtauber.com">jtauber@jtauber.com</jump></li>
           <li>Keith Visco
            <jump href="mailto:kvisco@exoffice.com">kvisco@exoffice.com</jump></li>
           <li>Dirk-Willem Van Gulik
            <jump href="mailto:dirkx@webweaving.org">dirkx@webweaving.org</jump></li>
       </ul>    </s2>
  
      <s2 title="Advisors">
      <ul>
        <li>Brian Behlendorf<jump href="mailto:brian@behlendorf.com">brian@behlendorf.com</jump><br/>
        <p>Brian is a co-founder of the Apache html HTTP Server Project. 
        He is currently as CTO of New Ventures at O'Reilly and Associates.
        </p></li>
      </ul>
      </s2>
  
  
  </s1>
  
  
  
  1.1                  xml-0.0/docs/xalan/readme.xml
  
  Index: readme.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Xalan XSLT">
    <s2 title="Xalan XSLT version 1.0">
      <p>
        Xalan (named after a rare musical instrument) provides high- 
        performance XSL stylesheet processing. Xalan fully implements the W3C 
        XSLT recommendation. The stylesheet processor is feature-rich and 
        robust. 
      </p>
      <p>
        Xalan is currently available in beta form in Java. We are working on 
        merging contributions from the initial contributors into a unified 
        code base. We expect to have a usable Java release of Xalan by the end 
        of 1999. The schedule for the C++ release is TBD. To learn more about 
        the various Xalan releases, click here. 
      </p>
      <p>
        Additional documentation to be provided soon. Watch this space.
      </p>
    </s2>
  </s1>
  
  
  1.1                  xml-0.0/docs/xerces-c/apidocs.xml
  
  Index: apidocs.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="API Documentation">
  	<s2 title="API Docs for SAX and DOM9">
  
      <p>XML4C 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 XML4C 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 XML4C 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 XML4C.</p>
      <p><jump href="apiDocs/index.html"><em>Click here to access the Xerces-C API documentation.</em></jump></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>
  
  	</s2>
  
  
  </s1>
  
  
  
  1.1                  xml-0.0/docs/xerces-c/caveats.xml
  
  Index: caveats.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Caveats and Limitations">
  
  	<s2 title="Encodings">
  		<ul>
  			<li>Encodings cannot be arbitrarily set programmatically,
       i.e. we only go by the encoding that is auto-sensed
       or found in encoding=""</li>
  		</ul>
  	</s2>
  
  	<s2 title="Validation">
  		<ul>
  			<li>Validation of notations/enumerations is not complete.
       For instance you can have a notation or enumeration
       type attribute that does not refer to the valid
       notations or enum values listed in the attribute
       type.</li>
  		</ul>
  	</s2>
  
  	<s2 title="Miscellaneous">
  		<ul>
  			<li>SAXPrint does not output the &lt;?XML ... ?&gt; prologue
       line (this means that it cannot process its own
  output). This is because the SAX API doesn't provide
  a callback handler for the prologue.</li>
  			<li>Only URL's of the form 'file://' are currently
       supported. Others will be supported in future
       versions (we're adding code to call libwww for this support).</li>
  			<li>Error text is not translatable yet, its only in
       English (we're working on this).</li>
  			<li>There is no catalog support.</li>
  		</ul>
  	</s2>
  
  </s1>
  
  
  
  1.1                  xml-0.0/docs/xerces-c/faq-distrib.xml
  
  Index: faq-distrib.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/faqs.dtd">
  
  <faqs title="Parsing with Xerces-C">
  	<faq title="FAQ?">
  		<q>Will we be writing this section?</q>
  		<a> 
  		    <p>Yes.  Stay tuned.</p>
  		</a>
  	</faq>
  
  </faqs>
  
  
  
  
  1.1                  xml-0.0/docs/xerces-c/faq-other.xml
  
  Index: faq-other.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/faqs.dtd">
  
  <faqs title="Other Xerces-C Questions">
  	<faq title="Other?">
  		<q>Will we be writing this section?</q>
  		<a> 
  		    <p>Yes.  Stay tuned.</p>
  		</a>
  	</faq>
  
  </faqs>
  
  
  
  
  1.1                  xml-0.0/docs/xerces-c/faq-parse.xml
  
  Index: faq-parse.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/faqs.dtd">
  
  <faqs title="Parsing with Xerces-C">
  	<faq title="FAQ?">
  		<q>Will we be writing this section?</q>
  		<a> 
  		    <p>Yes.  Stay tuned.</p>
  		</a>
  	</faq>
  
  </faqs>
  
  
  
  
  1.1                  xml-0.0/docs/xerces-c/feedback.xml
  
  Index: feedback.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Feedback Procedures">
  	<s2 title="Questions or Comments">
  		<p>For all questions or comments, write to the Xerces 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 Xerces-C (1.0.0?) </li>
  			<li>Which OS platform/version you are using (NT4+SP4? Win98? Solaris2.6?) </li>
  			<li>Which compiler/version you are using (MSVC6? gcc?) </li>
  			<li>Sample XML file that causes the bug</li>
  			<li>Sample Schema file (if required to recreate the bug)</li>
  			<li>Sample DTD file (if required to recreate the bug)</li>			
  		</ul>
  	</s2>
  
  	<s2 title="Acknowledgements">
  
      <p>Ever since this source code base was initially created, many people have
      helped to port the code to different platforms and provide
      constructive feedback to fix bugs and enhance features.</p>
  
      <p>Listed below are some names (in alphabetical order) of people
         to whom we would like to give special thanks. </p>
      <ul>
          <li>Anupam Bagchi</li>
          <li>John Bellardo</li>
          <li>Arundhati Bhowmick</li>
          <li>Paul Ferguson</li>
          <li>Andy Heninger</li>
          <li>Rahul Jain</li>
          <li>Andy Levine</li>
          <li>Michael Ottati</li>
          <li>Mike Pogue</li>
          <li>Dean Roddey</li>
          <li>Steven Rosenthal</li>
          <li>Gereon Steffens</li>
          <li>Tom Watson</li>
          <li>Roger Webster</li>
      </ul>
  	</s2>
  
  
  
  </s1>
  
  
  
  1.1                  xml-0.0/docs/xerces-c/install.xml
  
  Index: install.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Installation">
  
  
      <s2 title="Window NT/98">
          <p>
          Binary installation of this release of Xerces-C is simply to unzip the .zip
          archive
          under Windows environment (using WinZip, or any other UnZip utility like
          WinZip).
          </p>
          <source>
       unzip xerces-c_1_0.zip </source>
          
          <p>
          This will create a 'xerces-c_1_0' sub-directory (in the current directory)
          which contains the Xerces-C distribution. </p>
          
          <p>
          You will need to add the 'xerces-c_1_0\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_xerces-c_1_0>\bin to the PATH variable.  To do this
          under Windows 95/98 add the line:</p>
          
          <source>
     SET PATH=&lt;full_path_to_xerces-c_1_0>\bin;%PATH%  </source>
  
           <p>
           to your AUTOEXEC.BAT file, or run the set in your shell window.
           </p>
      </s2>
      
      <s2 title="UNIX">
          <p>
          Binary installation of this release is to extract the files from the compressed
          .tar
          archive (using 'tar'). </p>
  
          <source>
      cd $HOME
      uncompress xml4cxml4csrc3_0_0.tar.Z
      tar -xvf xml4cxml4csrc3_0_0.tar </source>
  
          <p>
          This will create an ' xerces-c_1_0' sub-directory (in the home directory)
          which contains the XML4C distribution. You will need to add the
          xerces-c_1_0/bin directory to your PATH environment variable:
          </p>
  
          <p>For Bourne Shell, K Shell or Bash, type: </p>
          <source>
      export PATH="$PATH:$HOME/xerces-c_1_0/bin" </source>
  
          <p>For C Shell type:</p>
          <source>
      setenv PATH "$PATH:$HOME/xerces-c_1_0/bin"</source>
  
          <p>If you wish to make this setting permanent, you need to change your profile
          by
          changing your setup files which can be either .profile or .kshrc.</p>
  
          <p>In addition, you will also need to set the environment variables XML4CROOT,
          ICUROOT and the library search path. (LIBPATH on AIX, LD_LIBRARY_PATH on
          Solaris and Linux, SHLIB_PATH on HP-UX).</p>
  
          <p>Note: XML4CROOT and ICUROOT are needed only if you intend to
          recompile the samples or build your own applications. The library path is
          necessary to link the shared libraries at runtime.</p>
  
          <p>For Bourne Shell, K Shell or Bash, type:</p>
  
  <source>
      export XML4CROOT=&lt;wherever you installed XML4C>
      export ICUROOT=&lt;wherever you installed ICU>
      export LIBPATH=$XML4CROOT/lib:$LIBPATH (on AIX)
      export LD_LIBRARY_PATH=$XML4CROOT/lib:$LD_LIBRARY_PATH (on Solaris, Linux)
      export SHLIB_PATH=$XML4CROOT/lib:$SHLIB_PATH (on HP-UX)</source>
  
          <p>For C Shell, type:</p>
  
  <source>
      setenv XML4CROOT "&lt;wherever you installed XML4C>"
      setenv ICUROOT "&lt;wherever you installed ICU>"
      setenv LIBPATH "$XML4CROOT/lib:$LIBPATH" (on AIX)
      setenv LD_LIBRARY_PATH "$XML4CROOT/lib:$LD_LIBRARY_PATH" (on Solaris, Linux)
      setenv SHLIB_PATH "$XML4CROOT/lib:$SHLIB_PATH" (on HP-UX)</source>
  
          <p>IMPORTANT NOTE: If you need to build the samples after installation,
          make sure you read and follow the build instructions given in the FAQ.</p>
          
     </s2>
  </s1>
  
  
  1.1                  xml-0.0/docs/xerces-c/program.xml
  
  Index: program.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Programming Guide">
  	<s2 title="SAX Programming Guide">
          <s3 title="Constructing a parser">
          <p>In order to use XML4C 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 XML4C.</p>
          <source><![CDATA[
  int main (int argc, char* args[]) {
  
     try {
         XMLPlatformUtils::Initialize();
     } 
     catch (const XMLException&amp; toCatch) {
         cout << "Error during initialization! :\n"
             << toCatch.getMessage() << "\n";
                 return 1; 
     } 
  
     char* xmlFile = "x1.xml";
     ValidatingSAXParser* parser = new
                                   ValidatingSAXParser();
  
     DocumentHandler* docHandler = new HandlerBase();
     ErrorHandler* errHandler = (ErrorHandler*) docHandler;
     parser->setDocumentHandler(docHandler);
     parser->setErrorHandler(errHandler);
  
     try
     {
         parser->parse(xmlFile);
     }
  
     catch (const XMLException& toCatch)
     {
         cout << "\nFile not found: '" << xmlFile << "'\n"
                 << "Exception message is: \n"
                 << toCatch.getMessage() << "\n" ;
         return -1;
     } 
  }
          ]]></source>
  
          </s3>
          <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 Xerces-C SAX API does not
                     guarantee client code compatibility with other C++ XML parsers.</p>
  
                     <p>The SAX API presents a callback based API to the parser. An application the
                     uses SAX provides an instance of a handler class to the parser. When the parser
                     detects XML constructs, it calls the methods of the handler class, passing them
                     information about the construct that was detected. The most commonly used
                     handler classes are DocumentHandler which is 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;full_path_to_xerces-c&gt;\include\SAX.</p>
  
                     <p>As a convenience, Xerces-C 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 Xerces-C 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
                     which will print element names, and print fatal error messages. The source code
                     for the sample applications show additional examples of how to write handler
                     classes.</p>
  
                     <p>This is the header file MySAXHandler.hpp:</p>
                     <source><![CDATA[
  #include <sax/HandlerBase.hpp>
  
     class MySAXHandler : public HandlerBase {
          private:
          public: 
     };
  ]]>                </source>
  
                     <p>This is the implementation file MySAXHandler.cpp:</p>
  
                     <source><![CDATA[ 
  #include "MySAXHandler.hpp"
  #include <iostream.h>
  
  MySAXHandler::MySAXHandler()
  {
  }
  
  MySAXHandler::startElement(const XMLCh* const name,
                            AttributeList&amp; attributes)
  {
   cout << "I saw element: " << name << endl;
  }
  
  MySAXHandler::fatalError(const SAXParseException&
                          exception)
  {
  cout << "Fatal Error: " << exception.getMessage() << 
          " at line: " << exception.getLineNumber() <<
           endl;
  }
                     ]]></source>
                      <p>The XMLCh and AttributeList types are supplied by Xerces-C and are documented
                     in the include files. Examples of their usage appear in the source code to the
                     sample applications.</p>  
  
          </s3>
  	</s2>
  
  	<s2 title="DOM Programming Guide">
          <s3 title="Java and C++ DOM comparisons">
          <p>    The C++ DOM API is very similar in design and use to the Java DOM API
                     bindings. As a consequence, conversion of existing Java code that makes use of
                     the DOM to C++ is a straightforward process.
           </p>
           <p>
                     This section outlines the differences between Java and C++ bindings.
           </p>
          </s3>
  
          <s3 title="Accessing the API from application code">
           <table>
                  <tr><td><source><![CDATA[
  // From C++
  #include <dom/DOM.hpp>
                  ]]></source></td></tr>
                  <tr><td><source><![CDATA[
  // From Java
  import org.w3c.dom.*
                  ]]></source></td></tr>
           </table>
  
          <p>The header file &lt;dom/DOM.hpp&gt; includes all of the individual headers for the
                     DOM API classes. </p>
  
          </s3>
  
  
          <s3 title="Class Names">
          <p>The C++ class names are prefixed with "DOM_". The intent is to prevent conflicts
                     between DOM class names and other names that may already be in use by an
                     application or other libraries that a DOM based application must link with.</p>
          <p>The use of C++ namespaces would also have solved this conflict problem, but for
                     the fact that many compilers do not yet support them.</p>
  
           <table>
                  <tr><td><source><![CDATA[
  DOM_Document   myDocument;   // C++
  DOM_Node       aNode;
  DOM_Text       someText;                
                  ]]></source></td></tr>
  
                  <tr><td><source><![CDATA[
  Document       myDocument;   // Java
  Node           aNode;
  Text           someText;                
                  ]]></source></td></tr>
           </table>
  
          <p>The Java class names can defined for use from C++ with a typedef. 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[
  typedef DOM_Document  Document;
  typedef DOM_Node      Node;
  
  Document   myDocument;        // Now C++ usage is
                                //indistinguishable from
  Java
  
  Node       aNode;
                  ]]></source></td></tr>
           </table>
  
          </s3>
  
  
          <s3 title="Objects and Memory Management">
          <p>The C++ DOM implementation uses automatic memory management,
                     implemented using reference counting.  As a result, the C++ code for most DOM
                     operations is very similar to the equivalent Java code, right down to the use of
                     factory methods in the DOM document class for nearly all object creation, and
                     the lack of any explicit object deletion.</p>
          <p>Consider the following code snippets </p>
           <table>
                  <tr><td><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[
  // This is Java
  
  Node       aNode;
  aNode = someDocument.createElement("ElementName");
  Node docRootNode = someDoc.getDocumentElement();
  docRootNode.AppendChild(aNode);
                  ]]></source></td></tr>
           </table>
  
          <p>The Java and the C++ are identical on the surface, except for the class names,
                     and this similarity remains true for most DOM code. </p>
          <p>However, Java and C++ handle objects in somewhat different ways, making it
                     important to understand a little bit of what is going on beneath the surface.</p>
          <p>In Java, the variable anode is an object reference , essentially a pointer. It is
                     initially == null, and references an object only after the assignment statement in
                     the second line of the code.</p>
          <p>In C++ the variable anode is, from the C++ language's perspective, an actual live 
                     object. It is constructed when the first line of the code executes, and
                     DOM_Node::operator = () executes at the second line. The C++ class
                     DOM_Node essentially a form of a smart-pointer; it implements much of the
                     behavior of a Java Object Reference variable, and delegates the DOM behaviors
                     to an implementation class that lives behind the scenes, in the implementation. </p>
          <p>Key points to remember when using the C++ DOM classes:</p>
  
          <ul>
          <li>Create them as local variables, or as member variables of some other
                          class. Never "new" a DOM object into the heap or make an ordinary C
                          pointer variable to one, as this will greatly confuse the automatic memory
                          management. </li>
          <li>The "real" DOM objects - nodes, attributes, CData sections, whatever,
                          do live on the heap, are created with the create... methods on class
                          DOM_Document. DOM_Node and the other DOM classes serve as
                          reference variables to the underlying heap objects.</li>
          <li>The visible DOM classes may be freely copied (assigned), passed as
                          parameters to functions, or returned by value from functions.</li>
          <li>Memory management of the underlying DOM heap objects is
                          automatic, implemented by means of reference counting. So long as
                          some part of a document can be reached, directly or indirectly, via
                          reference variables that are still alive in the application program, the
                          corresponding document data will stay alive in the heap. When all
                          possible paths of access have been closed off (all of the application's
                          DOM objects have gone out of scope) the heap data itself will be
                          automatically deleted. </li>
          <li>There are restrictions on the ability to subclass the DOM classes. </li>
          </ul>
  
          </s3>
  
          <s3 title="DOMString">
          <p>Class DOMString provides the mechanism for passing string data to and from the
                     DOM API. DOMString is not intended to be a completely general string class,
                     but rather to meet the specific needs of the DOM API.</p>
          <p>The design derives from two primary sources: from the DOM's CharacterData
                     interface and from class java.lang.string</p>
          <p>Main features are:</p>
  
          <ul>
              <li>Unicode, with fixed sized 16 bit storage elements.</li>
              <li>Automatic memory management, using reference counting.</li>
              <li>DOMStrings are mutable - characters can be inserted, deleted or
                          appended.</li>
          </ul>
          <p></p>
          <p>When a string is passed into a method of the DOM, when setting the value of a
                     Node, for example, the string is cloned so that any subsequent alteration or
                     reuse of the string by the application will not alter the document contents. 
                     Similarly, when strings from the document are returned to an application via the
                     DOM API, the string is cloned so that the document can not be inadvertently
                     altered by subsequent edits to the string.</p>
          <note>The ICU classes are a more general solution to UNICODE character
                     handling for C++ applications.  ICU is an Open Source Unicode library,
                     available on the <jump href="http://www.software.ibm.com/developerworks/opensource/icu/index.html">IBM DeveloperWorks website</jump>.</note>
          </s3>
  
          <s3 title="Equality Testing">
          <p>The DOMString equality operators (and all of the rest of the DOM class
                     conventions) are modeled after the Java equivalents. The equals() method
                     compares the content of the string, while the == operator checks whether the
                     string reference variables (the application program variables) refer to the same
                     underlying string in memory. This is also true of DOM_Node, DOM_Element,
                     etc., in that operator == tells whether the variables in the application are referring
                     to the same actual node or not. It's all very Java-like </p>
          <ul>
              <li>bool operator == ()  is true if the DOMString variables refer to the same
                          underlying storage. </li>
              <li>bool equals()  is true if the strings contain the same characters. </li>
          </ul>
          <p>Here is an example of how the equality operators work: </p>
          <source><![CDATA[
  DOMString a = "Hello";
  DOMString b = a;
  DOMString c = a.clone();
  if (b == a)           //  This is true
  if (a == c)           //  This is false
  if (a.equals(c))       //  This is true
  b = b + " World";
  if (b == a)           // Still true, and the string's 
                        //    value is "Hello World"
  if (a.equals(c))      // false.  a is "Hello World"; 
                        //    c is still "Hello".
          ]]></source>
          </s3>
  
          <s3 title="Downcasting">
          <p>Application code sometimes must cast an object reference from DOM_Node to
                     one of the classes deriving from DOM_Node, DOM_Element, for example.  The
                     syntax for doing this in C++ is different from that in Java.</p>
  
           <table>
                  <tr><td><source><![CDATA[
  // This is C++
  DOM_Node       aNode = someFunctionReturningNode();
  DOM_Element    el = (Element &)Node;
                  ]]></source></td></tr>
           </table>
  
           <table>
                  <tr><td><source><![CDATA[
  // This is Java
  Node       aNode = someFunctionReturningNode();
  Element    el = (Element)Node;
                  ]]></source></td></tr>
           </table>
  
          <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[
  // This is C++
  
  DOM_Node       aNode = someFunctionReturningNode();
  DOM_Element    el;    // by default, el will == null.
  
  if (anode.getNodeType() == DOM_Node::ELEMENT_NODE)
     el = (Element &)Node;
  else
     // aNode does not refer to an element.
     //  Do something to recover here.
                  ]]></source></td></tr>
           </table>
  
          </s3>
  
          <s3 title="Subclassing">
          <p>The C++ DOM classes,  DOM_Node, DOM_Attr, DOM_Document, etc., are not
                     designed to be subclassed by an application program. </p>
          <p>As an alternative, the DOM_Node class provides a User Data field for use by
                     applications as a hook for extending nodes by referencing additional data or
                     objects.   See the API description for DOM_Node for details.</p>
          </s3>
  
  	</s2>
  
  
  </s1>
  
  
  
  1.1                  xml-0.0/docs/xerces-c/readme.xml
  
  Index: readme.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Xerces C++">
  
  	<s2 title="Xerces-C++ version 1.0">
  	
  <p>Xerces-C is a validating XML parser written in a portable subset of C++. 
  Xerces-C 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. Xerces-C 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. 
  Source code, samples and API documentation are provided with the parser. For 
  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> 	  
  </s2>
  
  	<s2 title="Xerces Applications of the Xerces Parser">
  
  <p>Xerces has rich generating and validating capabilities. The parser is used for:</p>
  
  <ul>
      <li>Building XML-savvy Web servers</li>
      <li>Building next generation of vertical applications that use XML as 
        their data format</li> 
      <li>On-the-fly validation for creating XML editors</li>  
      <li>Ensuring the integrity of e-business data expressed in XML</li> 
      <li>Building truly internationalized XML applications</li>
  </ul>
      </s2>
  
      <s2 title="Features">
  <ul>
  <li>Conforms to XML Spec 1.0</li>
  <li>Tracking of latest DOM (Level 1.0 currently), SAX and namespace specs</li> 
  <li>Source code, samples, and docs provided</li>
  <li>Programmatic generation, validation of XML</li> 
  <li>Pluggable catalogs, validators, encodings</li> 
  <li>High performance</li>
  <li>Customizable error handling</li>
  </ul>
      </s2>
  
      <s2 title="Supported Platforms">
      <ul>
          <li>Win32 (MSVC 6.0 compiler)</li>
          <li>Linux (RedHat 6.0)</li>
      </ul>
      </s2>
  
      <s2 title="Platforms Coming Soon">
      <ul>
          <li>AIX 4.1.5 and higher</li>
          <li>HP-UX 10.2 (aCC and CC)</li>
          <li>HP-UX 11 (aCC and CC)</li>
          <li>Solaris 2.6</li>
          <li>and more!</li>
      </ul>
      </s2>
  
  </s1>
  
  
  1.1                  xml-0.0/docs/xerces-c/releases.xml
  
  Index: releases.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Releases">
  	<s2 title="November 5, 1999">
  		<ul>
  			<li>Created initial code base from IBM's XML4C.</li>
  			<li>Modified documentation to reflect new name (Xerces-C)</li>
  		</ul>
  	</s2>
  
  
  </s1>
  
  
  
  1.1                  xml-0.0/docs/xerces-c/samples.xml
  
  Index: samples.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Samples">
  
  	<s2 title="Building the Samples">
  	<p>XML4C2 comes packaged with six 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>
  
  	<p>Once you have set up your PATH variable, you can run the
  	samples by opening a command window (or your shell prompt for
  	UNIX environments). Sample XML data files are provided in the
  	samples/data directory.</p>
  
  	<p>The installation process for the samples is same on all UNIX
  	platforms.
  	Note that runConfigure is just a helper script and you are free to
  	use ./configure with the correct parameters to make it work
  	on any platform-compiler combination of your choice.</p>
  	</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 &lt;xml4c2InstallDir&gt;\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 &lt;xml4c2InstallDir&gt;/samples
  		./runConfigure &lt;PLATFORM&gt;
  		cd SAXCount
  		gmake
  		</source>
  		<p>where &lt;PLATFORM&gt; is the platform-compiler combination you are working on.
  		This will create the object files in the current directory and the executable named
  		SAXCount in ' &lt;xml4c2InstallDir&gt;/bin' directory.</p>
  
  		<p>To delete all the generated object files and executables, type</p>
  		<source>
  		gmake clean
  		</source>
  		</s3>
  
  		<s3 title="Running SAXCount">
  
  		  <p>The SAXCount sample parses an XML file and prints out a count of the number of
  		  elements in the file. To run SAXCount, enter the following </p>
  		  <source>
  			   SAXCount &lt;filename&gt;
  		  </source>
  		  <p>To use the validating parser, use </p>
  		  <source>
  			   SAXCount -v &lt;filename&gt;
  		  </source>
  		  <p>Here is a sample output from SAXCount</p>
  		  <source>
  		  cd &lt;xml4c2InstallDir&gt;/samples/data
  		  SAXCount -v personal.xml
  		  personal.xml: 60 ms (37 elems, 12 attrs, 134 spaces, 134 chars)
  		  </source>
  		  <p>Running SAXCount with the validating parser gives a different result because
  		  ignorable white-space is counted separately from regular characters.</p>
  		  <source>
  		  SAXCount personal.xml
  		  personal.xml: 10 ms (37 elems, 12 attrs, 0 spaces, 268 chars)
  	      </source>
  		  <p>Note that the sum of spaces and chracters in both versions is the same.</p>
  
  		  <note>The time reported by the program may be different depending on your
  		  machine processor.
  		  </note>
  		</s3>
  
  	</s2>
  
  
  
  
  
  
  
  	<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 &lt;xml4c2InstallDir&gt;\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 &lt;xml4c2InstallDir&gt;/samples
  		./runConfigure &lt;PLATFORM&gt;
  		cd SAXCount
  		gmake
  		</source>
  		<p>where &lt;PLATFORM&gt; is the platform-compiler combination you are working on.
  		This will create the object files in the current directory and the executable named
  		SAXPrint in '&lt;xml4c2InstallDir&gt;/bin' directory.</p>
  
  		<p>To delete all the generated object files and executables, type</p>
  		<source>
  		gmake clean
  		</source>
  		</s3>
  
  		<s3 title="Running SAXPrint">
  
  		  <p>The SAXPrint sample parses an XML file and prints out a count of the number of
  		  elements in the file. To run SAXPrint, enter the following </p>
  		  <source>
  			   SAXPrint &lt;filename&gt;
  		  </source>
  		  <p>To use the validating parser, use </p>
  		  <source>
  			   SAXPrint -v &lt;filename&gt;
  		  </source>
  		  <p>Here is a sample output from SAXPrint</p>
  		  <source>
  		  cd &lt;xml4c2InstallDir&gt;/samples/data
  		  SAXPrint -v personal.xml
  
  		  <personnel>
  
  			  <person id="Big.Boss">
  				<name><family>Boss</family> <given>Big</given></name>
  				<email>chief@foo.com</email>
  				<link subordinates="one.worker two.worker three.worker four.worker five.worker"></link>
  			  </person>
  
  			  <person id="one.worker">
  				<name><family>Worker</family> <given>One</given></name>
  				<email>one@foo.com</email>
  				<link manager="Big.Boss"></link>
  			  </person>
  
  			  <person id="two.worker">
  				<name><family>Worker</family> <given>Two</given></name>
  				<email>two@foo.com</email>
  				<link manager="Big.Boss"></link>
  			  </person>
  
  			  <person id="three.worker">
  				<name><family>Worker</family> <given>Three</given></name>
  				<email>three@foo.com</email>
  				<link manager="Big.Boss"></link>
  			  </person>
  
  			  <person id="four.worker">
  				<name><family>Worker</family> <given>Four</given></name>
  				<email>four@foo.com</email>
  				<link manager="Big.Boss"></link>
  			  </person>
  
  			  <person id="five.worker">
  				<name><family>Worker</family> <given>Five</given></name>
  				<email>five@foo.com</email>
  				<link manager="Big.Boss"></link>
  			  </person>
  
  		  </personnel>
  
  
  		  </source>
  		  <note>Note that SAXPrint does not reproduce the original XML file. Also SAXPrint and
  		                    DOMPrint produce different results because of the way the two APIs store data
                    and capture events.</note>
  		</s3>
  
  	</s2>
  
  
  
  
  
  
  	<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 &lt;xml4c2InstallDir&gt;\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 &lt;xml4c2InstallDir&gt;/samples
  		./runConfigure &lt;PLATFORM&gt;
  		cd DOMCount
  		gmake
  		</source>
  		<p>where &lt;PLATFORM&gt; is the platform-compiler combination you are working on.
  		This will create the object files in the current directory and the executable named
  		DOMCount in ' &lt;xml4c2InstallDir&gt;/bin' directory.</p>
  
  		<p>To delete all the generated object files and executables, type</p>
  		<source>
  		gmake clean
  		</source>
  		</s3>
  
  		<s3 title="Running DOMCount">
  
  		  <p>The DOMCount sample parses an XML file and prints out a count of the number of
  		  elements in the file. To run DOMCount, enter the following </p>
  		  <source>
  			   DOMCount &lt;filename&gt;
  		  </source>
  		  <p>To use the validating parser, use </p>
  		  <source>
  			   DOMCount -v &lt;filename&gt;
  		  </source>
  		  <p>Here is a sample output from DOMCount</p>
  		  <source>
  		  cd &lt;xml4c2InstallDir&gt;/samples/data
  		  DOMCount -v personal.xml
  		  personal.xml: 20 ms (37 elems)
  		  </source>
  
  		  <p>The output of both versions should be same.</p>
  
  		  <note>The time reported by the system may be different, depending on your
            processor type.
  		  </note>
  		</s3>
  
  	</s2>
  
  
  
  
  
  	<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 &lt;xml4c2InstallDir&gt;\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 &lt;xml4c2InstallDir&gt;/samples
  		./runConfigure &lt;PLATFORM&gt;
  		cd DOMPrint
  		gmake
  		</source>
  		<p>where &lt;PLATFORM&gt; is the platform-compiler combination you are working on.
  		This will create the object files in the current directory and the executable named
  		DOMPrint in ' &lt;xml4c2InstallDir&gt;/bin' directory.</p>
  
  		<p>To delete all the generated object files and executables, type</p>
  		<source>
  		gmake clean
  		</source>
  		</s3>
  
  		<s3 title="Running DOMPrint">
  
  		  <p>The DOMPrint sample parses an XML file, using either a validating or
                     non-validating DOM parser configuration, builds a DOM tree, and then walks the
                     tree and outputs the contents of the nodes in 'a' canonical format. To run
                     DOMPrint, enter the following:</p>
  		  <source>
  			   DOMPrint [-v] &lt;filename&gt;
  		  </source>
  		  <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 &lt;xml4c2InstallDir&gt;/samples/data
                 DOMPrint -v personal.xml
  		  </source>
  		  <p>Here is a sample output from DOMPrint</p>
  		  <source>
  		  cd &lt;xml4c2InstallDir&gt;/samples/data
  		  DOMPrint -v personal.xml
  
  
  		 &lt;?xml version='1.0' encoding='utf-8?&gt;
  		 <!-- Revision: 63 1.7 samples/data/personal.xml, xml4c2Docs, xml4c2, xml4c2_1_0_d2 -->
  		 <personnel>
  
  		   <person id="Big.Boss">
  			 <name><family>Boss</family> <given>Big</given></name>
  			 <email>chief@foo.com</email>
  			 <link subordinates="one.worker two.worker three.worker four.worker five.worker"></link>
  		   </person>
  
  		   <person id="one.worker">
  			 <name><family>Worker</family> <given>One</given></name>
  			 <email>one@foo.com</email>
  			 <link manager="Big.Boss"></link>
  		   </person>
  
  		   <person id="two.worker">
  			 <name><family>Worker</family> <given>Two</given></name>
  			 <email>two@foo.com</email>
  			 <link manager="Big.Boss"></link>
  		   </person>
  
  		   <person id="three.worker">
  			 <name><family>Worker</family> <given>Three</given></name>
  			 <email>three@foo.com</email>
  			 <link manager="Big.Boss"></link>
  		   </person>
  
  		   <person id="four.worker">
  			 <name><family>Worker</family> <given>Four</given></name>
  			 <email>four@foo.com</email>
  			 <link manager="Big.Boss"></link>
  		   </person>
  
  		   <person id="five.worker">
  			 <name><family>Worker</family> <given>Five</given></name>
  			 <email>five@foo.com</email>
  			 <link manager="Big.Boss"></link>
  		   </person>
  
  		   </personnel>
  
  		  </source>
  		  <p>Note that DOMPrint does not reproduce the original XML file. Also DOMPrint and
  		   SAXPrint produce different results because of the way the two APIs store data
             and capture events.</p>
  
  		</s3>
  
  	</s2>
  
  
  
  
  
  
  
  	<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 &lt;xml4c2InstallDir&gt;\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 &lt;xml4c2InstallDir&gt;/samples
  		./runConfigure &lt;PLATFORM&gt;
  		cd MemParse
  		gmake
  		</source>
  		<p>where &lt;PLATFORM&gt; is the platform-compiler combination you are working on.
  		This will create the object files in the current directory and the executable named
  		MemParse in ' &lt;xml4c2InstallDir&gt;/bin' directory.</p>
  
  		<p>To delete all the generated object files and executables, type</p>
  		<source>
  		gmake clean
  		</source>
  		</s3>
  
  		<s3 title="Running MemParse">
  
  		  <p>This program uses the Validating SAX Parser to parse a memory buffer
                     containing XML statements, and reports the number of elements and attributes
                     found. </p>
  		  <source>
  			   MemParse [-nv]
  		  </source>
  		  <p>The -nv option is used to invoke the NonValidating SAX Parser instead.
  
                     When invoked without any arguments: </p>
  		  <source>
  			   cd &lt;xml4c2InstallDir&gt;/samples/data
                 MemParse
  		  </source>
  		  <p>The output is the following:</p>
  		  <source>
  
  		  &lt;?xml version='1.0' encoding='ascii'?&gt;
  		  &lt;!DOCTYPE company [
  		  &lt;!ELEMENT company     (product,category,developedAt)&gt;
  		  &lt;!ELEMENT product     (#PCDATA)&gt;
  		  &lt;!ELEMENT category    (#PCDATA)&gt;
  		  &lt;!ATTLIST category idea CDATA #IMPLIED&gt;
  		  &lt;!ELEMENT developedAt (#PCDATA)&gt;
  		  ]&gt;
  
  
  		 <company>
  			 <product>XML4C</product>
  			 <category idea='great'>XML Parsing Tools</category>
  			 <developedAt>
  			   IBM Center for Java Technology, Silicon Valley, Cupertino, CA
  			 </developedAt>
  		 </company>
  
  		Parsing took 0 ms (4 elements, 1 attributes, 16 spaces, 95 characters).
  
  		  </source>
  
  			<p>You can also invoke it with '-nv' parameter to turn off validation.</p>
  		</s3>
  
  	</s2>
  
  
  
  
  	<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 &lt;xml4c2InstallDir&gt;\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 &lt;xml4c2InstallDir&gt;/samples
  		./runConfigure &lt;PLATFORM&gt;
  		cd Redirect
  		gmake
  		</source>
  		<p>where &lt;PLATFORM&gt; is the platform-compiler combination you are working on.
  		This will create the object files in the current directory and the executable named
  		Redirect in ' &lt;xml4c2InstallDir&gt;/bin' directory.</p>
  
  		<p>To delete all the generated object files and executables, type</p>
  		<source>
  		gmake clean
  		</source>
  		</s3>
  
  		<s3 title="Running Redirect">
  
  		  <p>This program illustrates how a XML application can use 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>
  
  					<p>The program then counts and reports the number of elements and attributes in
                     the given XML file.</p>
  		  <source>
  			   Redirect [-v] &lt;XML file&gt;
  		  </source>
  		  <p>The -v option is used to invoke the Validating SAX Parser instead.</p>
  
                     <p>When invoked as follows:</p>
  		  <source>
  			   cd &lt;xml4c2InstallDir&gt;/samples/data
                 Redirect -v personal.xml
  		  </source>
  		  <p>The output is the following:</p>
  		  <source>
  		  cd &lt;xml4c2InstallDir&gt;/samples/data
  		  Redirect -v personal.xml
  		  personal.xml: 30 ms (37 elems, 12 attrs, 134 spaces, 134 chars)
  		  </source>
  
  		  <p>External files required to run this sample are 'personal.xml', 'personal.dtd' and
                     'redirect.dtd', which are all present in the 'samples/data' directory. Make sure
                     that you run redirect in the samples/data directory.</p>
  
                     <p>The 'resolveEntity' callback in this sample looks for an external entity with
                     system id as 'personal.dtd'. When it is asked to resolve this particular external
                     entity, it creates and returns a new InputSource for the file 'redirect.dtd'.</p>
  
                     <p>A real-world XML application can similarly do application specific processing
                     when encountering external entities. For example, an application might want to
                     redirect all references to entities outside of its domain to local cached copies.</p>
  
  		</s3>
  
  	</s2>
  
  
  
  
  </s1>
  
  
  
  1.1                  xml-0.0/docs/xerces-j/api.xml
  
  Index: api.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="API Documentation">
      <s2 title="Javadoc Generated Documentation">
          <p>Xerces-J comes packaged with API documentation for SAX and DOM, 
          the two most common interfaces for programming XML.  In addition, 
          we provide documentation for classes that are not part of the SAX 
          and DOM API's, but are useful for writing Xerces-J programs. </p>
          <p>This documentation is generated automatically from the Javadoc-style 
          comments inside the source files.  Click on one of the links below to 
          go to the appropriate API documentation.</p>
      </s2>
      <s2 title="Xerces-J API Documentation">
          <ul>
              <li><jump href="./apiDocs/index.html">Full API documentation</jump></li>
              <li><jump href="./apiDocs/overview-tree.html">Hierarchy for all the packages</jump></li>
          </ul>
      <s3 title="Package org.apache.xerces.parsers">
        <s4 title="Classes">
          <ul>
              <li>DOMParser</li>
              <li>SAXParser</li>
          </ul>
        </s4>
        <s4 title="Interfaces">
          <ul>
              <li>Attr
                  <br/>The Attr interface represents an attribute in an Element object</li>
              <li>CDATASection
                  <br/>CDATA sections are used to escape blocks of text containing characters
                  that would otherwise be regarded as markup</li>
              <li>CharacterData
                  <br/>The CharacterData interface extends Node with a set of attributes and
                  methods for accessing character data in the DOM</li>
              <li>Comment
                  <br/>This represents the content of a comment</li>
              <li>Document
                  <br/>The Document interface represents the entire HTML or XML document</li>
              <li>DocumentFragment
                  <br/>DocumentFragment is a "lightweight" or "minimal" Document object</li>
              <li>DocumentType
                  <br/>Each Document has a doctype attribute whose value is either null or a
                  DocumentType object</li>
              <li>DOMImplementation
                  <br/>The DOMImplementation interface provides  methods for performing
                  operations independent of a particular document object model instance</li>
              <li>Element
                  <br/>The majority of objects (apart from text) in a document are Element nodes</li>
              <li>Entity
                  <br/>This interface represents an entity, either parsed or unparsed, in a XML
                  document</li>
              <li>EntityReference
                  <br/>EntityReference objects may be inserted into the structure model</li>
              <li>NamedNodeMap
                  <br/>Objects implementing the NamedNodeMap interface are used to represent
                  collections of nodes that can be accessed by name</li>
              <li>Node
                  <br/>The Node interface is the primary datatype for the entire Document Object
                  Model</li>
              <li>NodeList
                  <br/>The NodeList interface provides the abstraction of an ordered collection
                  of nodes</li>
              <li>Notation
                  <br/>This interface represents a notation declared in the DTD</li>
              <li>ProcessingInstruction
                  <br/>The ProcessingInstruction is a way to keep processor-specific
                  information in the text of the document</li>
              <li>Text
                  <br/>The Text interface represents the textual content (termed character data in
                  XML) of an Element or Attr</li>
          </ul>
        </s4>
        <s4 title="Exceptions">
          <ul>
              <li>DOMException
              <br/>Encapsulate an "exceptional" DOM error </li>
          </ul>
        </s4>
      </s3>
      <s3 title="Package org.xml.sax">
        <s4 title="Classes">
          <ul>
              <li>HandlerBase
                  <br/>Default base class for handlers</li>
              <li>InputSource
                  <br/>A single input source for an XML entity </li>
          </ul>
        </s4>
        <s4 title="Interfaces">
          <ul>
              <li>AttributeList
                  <br/>Interface for an element's attribute specifications</li>
              <li>DocumentHandler
                  <br/>Receive notification of general document events</li>
              <li>DTDHandler
                  <br/>Receive notification of basic DTD-related events</li>
              <li>EntityResolver
                  <br/>Basic interface for resolving entities</li>
              <li>ErrorHandler
                  <br/>Basic interface for SAX error handlers </li>
              <li>Locator
                  <br/>Interface for associating a SAX event with a document location</li>
              <li>Parser
                  <br/>Basic interface for SAX (Simple API for XML) parsers</li>
          </ul>
        </s4>
        <s4 title="Exceptions">
          <ul>
              <li>SAXException
                  <br/>Encapsulate a general SAX error or warning</li>
              <li>SAXParseException
                  <br/>Encapsulate an XML parse error or warning </li>
          </ul>
        </s4>
      </s3>
      <s3 title="Package org.xml.sax.helpers">
        <s4 title="Classes">
          <ul>
              <li>AttributeListImpl
                  <br/>Convenience implementation for AttributeList</li>
              <li>LocatorImpl
                  <br/>Convenience implementation for Locator</li>
              <li>ParserFactory
                  <br/>Java-specific class for dynamically loading SAX parsers</li>
          </ul>
        </s4>
     </s3>
      <s3 title="Package org.apache.xerces.dom.traversal">
        <s4 title="Classes">
          <ul>
              <li>DocumentTraversal
                  <br/>DocumentTraversal contains methods that creates Iterators to traverse a
                  node and its children</li>
              <li>DocumentTWIF
                  <br/>DocumentTWIF contains methods that create Iterators to traverse a node
                  and its children</li>
              <li>NodeFilter
                  <br/>Filters are objects that know how to "filter out" nodes</li>
              <li>NodeIterator
                  <br/>NodeIterators are used to step through a set of nodes</li>
              <li>TreeWalker
                  <br/>TreeWalker objects are used to navigate a document tree or subtree using
                  the view of the document </li>
          </ul>
        </s4>
      </s3>
    </s2>
  </s1>
  
  
  
  1.1                  xml-0.0/docs/xerces-j/caveats.xml
  
  Index: caveats.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Caveats">
  	<s2 title="Caveats and Limitations">
  		<p>This is a list of the limitations in this release of Xerces-J:</p>
  		<ul>
  			<li>Due to a transcoding bug in the Sun JDK's 
  			(1.1.6, 1.1.7, 1.1.8, 1.2)  handling of EBCDIC data 
  			(specifically, end of line characters), you must use 
  			IBM's JDK 1.1.6, if you want to use EBCDIC support. 
  			The IBM JDK has the bug fixed.  We don't know when the 
  			bug fix will get into the Sun JDK's. </li>
  		</ul>
  	</s2>
  </s1>
  
  
  
  1.1                  xml-0.0/docs/xerces-j/faq-build.xml
  
  Index: faq-build.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/faqs.dtd">
  
  <faqs title="Building and Running FAQs">
  	<faq title="Swing?">
  		<q>Which version of Swing is required?</q>
  		<a> <p>This release uses Swing 1.1 (JFC 1.1). 
  			Swing is only used by the sample programs and is not 
  			required by the parser itself.</p>
  		</a>
  	</faq>
  	<faq title="Recompling?">
  		<q>How do I recompile the source files?</q>
  		<a> <p>blah
  			</p>
  		</a>
  	</faq>
  	<faq title="Regenerating?">
  		<q>How do I regenerate the api documentation?</q>
  		<a> <p>blah
  			</p>
  		</a>
  	</faq>
  	<faq title="Packaging?">
  		<q>How do I package the parser?</q>
  		<a> <p>blah
  			</p>
  		</a>
  	</faq>
  	<faq title="Visual Age?">
  		<q>How do I import Xerces-J into Visual Age for Java</q>
  		<a> 		
  		<ul>
            <li>Why does VisualAge for Java 2.0 report problems when I import the Xerces-J parser?
  			<br/>The current version of the Xerces-J parser uses Swing 1.1, 
  		  	while VisualAge for Java 2.0 comes with Swing 1.0.2. The free update for the 
              Professional version of VisualAge for Java 2.0 installs Swing 1.0.3. 
  			The most important difference between Swing 1.0.2 - 1.0.3 and 1.1 is 
  			the Java package was changed from com.sun.java.swing.* to javax.swing.*.
  			<br/>To fix the errors, you must download the Java Foundation Classes 1.1 
  			with Swing 1.1 from Sun's Java home page and import the &quot;swingall.jar&quot; 
  			file into VisualAge for Java 2.0. The Swing 1.1 package can be found at 
              the following URL:
  			<br/>http://java.sun.com/products/jfc/index.html 
  			<br/>Refer to the VisualAge for Java 2.0 documentation for information about 
  			how to import a JAR file into the repository and add that code to your workspace.
            </li>
            <li>Are there any other tips for importing the Xerces-J parser into VisualAge 
  		  	for Java 2.0?
  			<br/>The most useful tip applies to *any* updated code that you import 
  			into the VisualAge for Java 2.0 product. Before updating code, do the following:
              <br/>1. version the old code
  			<br/>2. delete it from your workspace
  			<br/>3. import the new code
              <br/>Deleting code from your workspace does not actually delete the code 
  				permanently -- the versioned code is moved to the repository where it can be 
  				retrieved later. Be aware, though, that removing code from your 
             		workspace will cause problems with all of the other classes that use that code. 
  				VisualAge for Java 2.0 will flag them as errors but this situation is temporary. 
  				When you import the new code, the errors found when deleting the old code will be fixed.
  				<br/>If you are unsure as to how to perform any of these steps, refer to the VisualAge 
  				for Java 2.0 documentation.
  			</li>
            </ul>
  		</a>
  	</faq>
  	<faq title="100% Pure Java?">
  		<q>Is this Xerces-J version 100% pure Java compliant?</q>
  		<a> <p>blah
  			</p>
  		</a>
  	</faq>
  	<faq title="Running on the Mac?">
  		<q>How do I get Xerces-J to run on the Mac under MRJ?</q>
  		<a> <p><em>Prerequisites</em> (available from 
  			<jump href="http://developer.apple.com/java/">http://developer.apple.com/java/</jump>):</p>
          <ul>
            <li>MRJ 2.1 (this is the most recent version of the JVM)</li>
            <li>MRJ SDK 2.1 (this is the most recent version of the Java developer tools)</li>
          </ul>
          <p><em>Instructions </em>(other variations would work also):</p>
          <ol>
            <li>Download the .tar.gz file containing Xerces-J.</li>
            <li>Use Stuffit Expander(tm), Suntar, or some other Macintosh tool that
  		  	<br/>supports the .tar.gz format to expand the downloaded file.</li>
            <li>JBindery, part of MRJ SDK 2.1, is used to create a double-clickable 
  		  	Java application with the necessary configuration information built in. 
  			It is analogous to writing a .bat or .sh script. </li>
            <li><em>To run the dom.DOMWriter example:</em></li>
            <ol>
              <li>Double click on JBindery to start it up.</li>
              <li>Click on the Classpath panel.</li>
              <li>Click on the &quot;Add .zip File&quot; button and add both the 
  				&quot;Xerces-J.jar&quot; and &quot;Xerces-JSamples.jar&quot; files.</li>
              <li>Click on the Command panel.</li>
              <li>Enter &quot;dom.DOMWriter&quot; as the Class name. Enter 
  				&quot;data/personal.xml&quot; in the Optional parameters box.</li>
              <li>Click on Save Settings button, pick a name such as &quot;Run dom.DOMWriter&quot; 
  				for the file, and <em>be sure</em> that &quot;Save as Application&quot; 
  				is selected (this is the default) and save the file.</li>
              <li>Quit JBindery.</li>
              <li>You can now double click on the file you created in step f to run the XJParse example.</li>
            </ol>
  		</ol>
  		</a>
  	</faq>
  	<faq title="Visual Cafe Error?">
  		<q>Why do I get <code>ArrayIndexOutOfBoundsException</code> in the Symantec Visual Cafe debugger?</q>
  		<a> <p>Visual Cafe's debugger is set to trap <code>ArrayIndexOutOfBoundsException</code>'s by 
          	default. Xerces-J uses <code>ArrayIndexOutOfBoundsException</code> internally to signal 
  			exceptional, but not erroneous conditions. In order to run Xerces-J2 inside 
         		Visual Cafe's debugger, you need to turn off the trapping of these 
  			exceptions.</p>
  			<p><em>To do this:</em></p>
          	<ol>
            		<li>Select the &quot;Options&quot; item in the "Project" menu.</li>
            		<li>Select the &quot;Debugger&quot; tab in the dialog which appears.</li>
            		<li>Select &quot;Exceptions&quot; from the popup menu.</li>
            		<li>Remove the check from the checkbox for <code>java.lang.ArrayIndexOutOfBoundsException</code>.</li>
          	</ol>
  		</a>
  	</faq>
  </faqs>
  
  
  
  1.1                  xml-0.0/docs/xerces-j/faq-common.xml
  
  Index: faq-common.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/faqs.dtd">
  
  <faqs title="Common Problems">
  	<faq title="Parsing Generated an Error">
  		<q>I tried to use Xerces-J to parse HTML, and it generated an error. What did I do wrong?</q>
  		<a><p>Unfortunately, HTML does not, in general, follow the XML grammar rules. 
                Most HTML is actually not well-formed XML. Therefore, the XML parser 
  			  generates XML well-formedness errors.</p>
  			  <p>Typical errors include:</p>
                <ul>
                  <li>Missing end tags, e.g. &lt;P&gt; with no &lt;/P&gt; (end tags are not required in HTML)</li>
                  <li>Missing closing slash on &lt;IMG HREF="foo" <em>/</em>&gt; (not required in HTML)</li>
                  <li>Missing quotes on attribute values, e.g. &lt;IMG width="600"&gt; (not generally required in HTML)</li>
                </ul>
  		</a>
  	</faq>
  	<faq title="UTF-8 Character Error">
  		<q>I get an error: &quot;invalid UTF-8 character&quot;</q>
  		<a><p>There are many Unicode characters that are not allowed in an XML document, 
                according to the XML spec. Typical disallowed characters are control 
  			  characters, even if you escape them using the Character Reference form: 
  			  &amp;#xxxx; . See the XML spec, sections 
  			  <jump href="http://www.w3.org/TR/REC-xml#charsets">2.2</jump> and 
  			  <jump href="http://www.w3.org/TR/REC-xml#sec-references">4.1</jump> 
  			  for details. If the parser is generating this error, it is very likely 
  			  that there's a character in there that you can not see.
                You can generally use a UNIX command like &quot;od -hc&quot; to find it.</p>
  			  
  		</a>
  	</faq>
  	<faq title="Error Accessing EBCDIC XML Files">
  		<q>I get an error when I access EBCDIC XML files -- what's happening?</q>
  		<a><p>If an XML document/file is not UTF-8, then you MUST specify the encoding. 
                When transcoding a UTF8 document to EBCDIC, remember to change this:</p>
                <ul>
                  <li>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt; 
  				<br/>to something like this:
  				<br/>&lt;?xml version=&quot;1.0&quot; encoding=&quot;ebcdic-cp-us&quot;?&gt;
  				</li>
                </ul>
  		</a>
  	</faq>
  	<faq title="EOF Character Error">
  		<q>I get an error on the EOF character (0x1A) -- what's happening?</q>
  		<a><p>No, the parser isn't broken. You're probably using the <em>LPEX</em> 
  		editor, which automatically inserts an End-of-file character at the end of your 
  		XML document (other editors might do this as well). Unfortunately, the 
  		EOF character (0x1A) is an illegal character according to the XML specification, 
  		and Xerces-J correctly generates an error.</p>
  		</a>
  	</faq>
  </faqs>
  
  
  
  1.1                  xml-0.0/docs/xerces-j/faq-general-doc.xml
  
  Index: faq-general-doc.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <faqs title="General FAQs">
  	<faq title="New Features?">
  		<q>What are the new features in this parser?</q>
  		<a>
  			<p>To be provided.
  			</p>
  		</a>
  	</faq>
  	<faq title="Validation">
  		<q>How do I turn on validation?</q>
  		<a>
  			<p>To be provided.
  			</p>
  		</a>
  	</faq>
  	<faq title="Migrating from other parsers">
  		<q>How do I migrate my code from another XML parser?</q>
  		<a>
  			<p>To be provided.
  			</p>
  		</a>
  	</faq>
  	<faq title="International Encodings">
  		<q>What international encodings are supported by Xerces-J?</q>
  		<a>
  			<ul>
            		<li>UTF-8</li>
            		<li>UTF-16 Big Endian, UTF-16 Little Endian</li>
            		<li>IBM-1208</li>
            		<li>ISO Latin-1 (ISO-8859-1)</li>
            		<li>ISO Latin-2 (ISO-8859-2) [Bosnian, Croatian, Czech, 
  					<br/>Hungarian, Polish, Romanian, Serbian (in Latin transcription),
  					<br/>Serbocroatian, Slovak, Slovenian, Upper and Lower Sorbian]</li>
            		<li>ISO Latin-3 (ISO-8859-3) [Maltese, Esperanto]</li>
            		<li>ISO Latin-4 (ISO-8859-4)</li>
            		<li>ISO Latin Cyrillic (ISO-8859-5)</li>
            		<li>ISO Latin Arabic (ISO-8859-6)</li>
            		<li>ISO Latin Greek (ISO-8859-7)</li>
            		<li>ISO Latin Hebrew (ISO-8859-8)</li>
            		<li>ISO Latin-5 (ISO-8859-9) [Turkish]</li>
            		<li>Extended Unix Code, packed for Japanese (euc-jp, eucjis)</li>
            		<li>Japanese Shift JIS (shift-jis)</li>
            		<li>Chinese (big5)</li>
            		<li>Chinese for PRC (mixed 1/2 byte) (gb2312)</li>
            		<li>Japanese ISO-2022-JP (iso-2022-jp)</li>
            		<li>Cyrllic (koi8-r)</li>
            		<li>Extended Unix Code, packed for Korean (euc-kr)</li>
            		<li>Russian Unix, Cyrillic (koi8-r)</li>
            		<li>Windows Thai (cp874)</li>
            		<li>Latin 1 Windows (cp1252)</li>
            		<li>cp858</li>
            		<li>EBCDIC encodings:</li>
            			<ul>
              			<li>EBCDIC US (ebcdic-cp-us)</li>
              			<li>EBCDIC Canada (ebcdic-cp-ca)</li>
              			<li>EBCDIC Netherland (ebcdic-cp-nl)</li>
              			<li>EBCDIC Denmark (ebcdic-cp-dk)</li>
              			<li>EBCDIC Norway (ebcdic-cp-no)</li>
              			<li>EBCDIC Finland (ebcdic-cp-fi)</li>
              			<li>EBCDIC Sweden (ebcdic-cp-se)</li>
              			<li>EBCDIC Italy (ebcdic-cp-it)</li>
              			<li>EBCDIC Spain, Latin America (ebcdic-cp-es)</li>
              			<li>EBCDIC Great Britain (ebcdic-cp-gb)</li>
              			<li>EBCDIC France (ebcdic-cp-fr)</li>
              			<li>EBCDIC Hebrew (ebcdic-cp-he)</li>
              			<li>EBCDIC Switzerland (ebcdic-cp-ch)</li>
              			<li>EBCDIC Roece (ebcdic-cp-roece)</li>
              			<li>EBCDIC Yugoslavia (ebcdic-cp-yu)</li>
              			<li>EBCDIC Iceland (ebcdic-cp-is)</li>
              			<li>EBCDIC Urdu (ebcdic-cp-ar2)</li>
              			<li>Latin 0 EBCDIC</li>
              			<li>EBCDIC Arabic (ebcdic-cp-ar1)</li>
            			</ul>
          		</ul>
  			</a>
  	</faq>
  </faqs>
  
  
  
  1.1                  xml-0.0/docs/xerces-j/faq-general.xml
  
  Index: faq-general.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/faqs.dtd">
  
  <faqs title="General FAQs">
  	<faq title="New Features?">
  		<q>What are the new features?</q>
  		<a>
  			<p>To be provided.
  			</p>
  		</a>
  	</faq>
  	<faq title="Validation">
  		<q>How do I turn on validation?</q>
  		<a>
  			<p>To be provided.
  			</p>
  		</a>
  	</faq>
  	<faq title="Migrating from other XML parsers">
  		<q>How do I migrate my code from other XML parsers?</q>
  		<a>
  			<p>To be provided.
  			</p>
  		</a>
  	</faq>
  	<faq title="International Encodings">
  		<q>What international encodings are supported by Xerces-J?</q>
  		<a>
  			<ul>
            		<li>UTF-8</li>
            		<li>UTF-16 Big Endian, UTF-16 Little Endian</li>
            		<li>IBM-1208</li>
            		<li>ISO Latin-1 (ISO-8859-1)</li>
            		<li>ISO Latin-2 (ISO-8859-2) [Bosnian, Croatian, Czech, 
  					<br/>Hungarian, Polish, Romanian, Serbian (in Latin transcription),
  					<br/>Serbocroatian, Slovak, Slovenian, Upper and Lower Sorbian]</li>
            		<li>ISO Latin-3 (ISO-8859-3) [Maltese, Esperanto]</li>
            		<li>ISO Latin-4 (ISO-8859-4)</li>
            		<li>ISO Latin Cyrillic (ISO-8859-5)</li>
            		<li>ISO Latin Arabic (ISO-8859-6)</li>
            		<li>ISO Latin Greek (ISO-8859-7)</li>
            		<li>ISO Latin Hebrew (ISO-8859-8)</li>
            		<li>ISO Latin-5 (ISO-8859-9) [Turkish]</li>
            		<li>Extended Unix Code, packed for Japanese (euc-jp, eucjis)</li>
            		<li>Japanese Shift JIS (shift-jis)</li>
            		<li>Chinese (big5)</li>
            		<li>Chinese for PRC (mixed 1/2 byte) (gb2312)</li>
            		<li>Japanese ISO-2022-JP (iso-2022-jp)</li>
            		<li>Cyrllic (koi8-r)</li>
            		<li>Extended Unix Code, packed for Korean (euc-kr)</li>
            		<li>Russian Unix, Cyrillic (koi8-r)</li>
            		<li>Windows Thai (cp874)</li>
            		<li>Latin 1 Windows (cp1252)</li>
            		<li>cp858</li>
            		<li>EBCDIC encodings:</li>
            		<ul>
              		<li>EBCDIC US (ebcdic-cp-us)</li>
              		<li>EBCDIC Canada (ebcdic-cp-ca)</li>
              		<li>EBCDIC Netherland (ebcdic-cp-nl)</li>
              		<li>EBCDIC Denmark (ebcdic-cp-dk)</li>
              		<li>EBCDIC Norway (ebcdic-cp-no)</li>
              		<li>EBCDIC Finland (ebcdic-cp-fi)</li>
              		<li>EBCDIC Sweden (ebcdic-cp-se)</li>
              		<li>EBCDIC Italy (ebcdic-cp-it)</li>
              		<li>EBCDIC Spain, Latin America (ebcdic-cp-es)</li>
              		<li>EBCDIC Great Britain (ebcdic-cp-gb)</li>
              		<li>EBCDIC France (ebcdic-cp-fr)</li>
              		<li>EBCDIC Hebrew (ebcdic-cp-he)</li>
              		<li>EBCDIC Switzerland (ebcdic-cp-ch)</li>
              		<li>EBCDIC Roece (ebcdic-cp-roece)</li>
              		<li>EBCDIC Yugoslavia (ebcdic-cp-yu)</li>
              		<li>EBCDIC Iceland (ebcdic-cp-is)</li>
              		<li>EBCDIC Urdu (ebcdic-cp-ar2)</li>
              		<li>Latin 0 EBCDIC</li>
              		<li>EBCDIC Arabic (ebcdic-cp-ar1)</li>
            		</ul>
          	</ul>
  		</a>
  	</faq>
  </faqs>
  
  
  
  1.1                  xml-0.0/docs/xerces-j/faq-write.xml
  
  Index: faq-write.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/faqs.dtd">
  
  <faqs title="Writing Application FAQs">
  	<faq title="Constructing a Parser">
  		<q>How do I construct a parser in Xerces-J v1.0?</q>
  		<a><p>
  There are two ways the parser classes can be
  	  instantiated: The first way is to <em>create a string</em>
  	  containing the fully qualified name of the parser class. Pass
  	  this string to the <code>org.xml.sax.helpers.ParserFactory.makeParser()</code>
  	  method to instantiate it. This method is useful if your application will need to switch between different parser configurations. The code snippet shown below is using this method to instantiate a DOMParser.</p> 
  
  	   <source>
  import org.xml.sax.Parser;
  import org.xml.sax.helpers.ParserFactory; 
  import org.apache.xerces.parsers.DOMParser;
  import org.w3c.dom.Document;
  import org.xml.sax.SAXException;
  import java.io.IOException; 
  
    ...
  
  String parserClass = &quot;org.apache.xerces.parsers.DOMParser&quot;;
  
  String xmlFile = &quot;file:///Xerces-J/data/personal.xml&quot;; 
  
  Parser parser = ParserFactory.makeParser(parserClass);
  
  try {
      parser.parse(xmlFile);
  } catch (SAXException se) {
      se.printStackTrace();
  } catch (IOException ioe) {
  	ioe.printStackTrace();
  }
  // The next line is only for DOM Parsers
  
  Document doc = ((DOMParser) parser).getDocument(); 
  
    ...
  	 </source>
  
  	 <p>The second way to instantiate a parser class is to <em>explicitly
  	 instantiate</em> the parser class, as shown in this example,
  	 which is creating a DOM Parser. Use this way when you know
  	 exactly which parser configuration you need, and you are sure
  	 that you will not need to switch configurations.</p>
  
  	 <source>
  import org.apache.xerces.parsers.DOMParser;
  import org.w3c.dom.Document;
  import org.xml.sax.SAXException;
  import java.io.IOException;
  
    ...
  
  String xmlFile = &quot;file:///Xerces-J/data/personal.xml&quot;; 
  
  DOMParser parser = new DOMParser();
  
  try {
      parser.parse(xmlFile);
  
  } catch (SAXException se) {
      se.printStackTrace();
  } catch (IOException ioe) {
      ioe.printStackTrace();
  }
  // The next line is only for DOM Parsers
  Document doc = parser.getDocument();
  
    ...
  	 </source>
  
  	<p>Once you have the Document object, you can call any method on it as defined by the DOM specification.</p>
     </a>
  	</faq>
  	<faq title="Creating a DOM Parser">
  		<q>How do I create a DOM parser?</q>
          <a><p>Use one of the methods in the question above, and use 
  		<code>org.apache.xerces.parsers.DOMEParser</code> as the name of the class. </p>
  		<p>To access the DOM tree, you can call the
  		<code>getDocument()</code> method on the parser instance.</p> 
  		</a>
  	</faq>
  	<faq title="Creating a SAX Parser">
  		<q>How do I create a SAX parser?</q>
  		<a><p>Use one of the methods in the question above, and use 
  		<code>org.apache.xerces.parsers.SAXParser</code> as the name of the class. </p>
  		<p>Once you have the parser instance, you can use the standard SAX 
  		methods to set the various handlers provided by SAX. </p>
  		</a>
  	</faq>
  	<faq title="Controlling parser options">
  		<q>How do I control the various parser options?</q>
  		<a><p>For this release, all of the parser control API's have
  		been switched over to the SAX2 Configurable interface.  This
  		provide a uniform and extensible mechanism for setting and
  		querying parser options.  Here are guides to the set of
  		available <link idref="features">features</link> and
  		<link idref="properties">properties</link>.</p>
  		</a>
  	</faq>
  	<faq title="Using lazy dom">
  		<q>How do I use the lazy evaluating DOM implementation?</q>
  		<a><p>The DOM parser class
  		<code>org.apache.xerces.parsers.DOMParser</code> now uses a DOM
  		implementation that can take advantage of lazy evaluation to
  		improve performance.  The setNodeExpansion call on these
  		classes controls the use of lazy evaluation. There are two
  		values for the argument to setNodeExpansion: FULL and
  		DEFERRED(the default). </p> 
  	    <p>If node expansion is set to FULL, then the DOM classes
  	    behave as they always have, creating all nodes in the DOM tree
  	    by the end of parsing.</p> 
  
  	    <p>If node expansion is set to DEFERRED, nodes in the DOM tree
  	    are only created when they are accessed. This means that a
  	    call to getDocument will return a DOM tree that consists only
  	    of the Document node. When your program accesses a child of
  	    Document, the children of the Document node will be
  	    created. All the immediate children of a Node are created when
  	    any of that Node's children are accessed. This shortens the
  	    time it takes to parse an XML file and create a DOM tree. This
  	    also increases the time it takes to access a node that has not
  	    been created. After nodes have been created, they are cached,
  	    so this overhead only occurs on the first access to a
  	    Node. </p> 
  		</a>
  	</faq>
  	<faq title="Handling Errors">
  		<q>How do handle errors?</q>
  		<a><p>When you create a parser instance, the default error handler does nothing. 
  		This means that your program will fail silently when it encounters an error. 
  		You should register an error handler with the parser by supplying a class 
  		which implements the <code>org.xml.sax.ErrorHandler</code>
  		interface. This is true regardless of whether your parser is a
  		DOM based or SAX based parser.</p>
  		</a>
  	</faq>
  	<faq title="Controlling Entity Representation">
  		<q>How can I control the way that entities are represented in
  		the DOM?</q>
  		<a><p>
          The feature <code>http://apache.org/xml/features/dom/create-entity-ref-nodes</code>
          controls how entities appear in the DOM tree. When this
          feature is set to true (the default), an occurance of an
          entity reference in the XML document will be represented by a
          subtree with an EntityReference node at the root whose
          children represent the entity expansion.</p>
  
      	<p>If the property is false, an entity reference in the XML
      	document is represented by only the nodes that represent the
      	entity expansion.</p> 
  
          <p>In either case, the entity expansion will be a DOM tree
          representing the structure of the entity expansion, not a text
          node containing the entity expansion as text.</p>
  		</a>
  	</faq>
  	<faq title="Non-Validating">
  		<q>Why does "non-validating" not mean "well-formedness checking only"?</q>
  		<a><p>Using a "non-validating" parser does not mean that only well-formedness 
          checking is done! There are still many things that the XML specification 
  		requires of the parser, including entity substitution, defaulting of 
  		attribute values, and attribute normalization.</p>
          <p>This table describes what "non-validating" really means for Xerces-J parsers. 
  		In this table, "no DTD" means no internal or external DTD subset is present.</p>
  		
          <table>
  			<tr><tn/>
  				<th colspan="2" align="center">non-validating parsers</th>
  				<th colspan="2" align="center">validating parsers</th>
            	</tr>
            	<tr>
  				<tn/>
  				<th>DTD present</th>
  				<th>no DTD</th>
  				<th>DTD present</th>
  				<th>no DTD</th>
            	</tr>
            	<tr>
  				<th>DTD is read</th>
  				<td>Yes</td>
  				<td>No</td>
  				<td>Yes</td>
  				<td>Error</td>
            	</tr>
            	<tr>
  				<th>entity substitution</th>
  				<td>Yes</td>
  				<td>No</td>
  				<td>Yest</td>
  				<td>Error</td>
            	</tr>
            	<tr>
  				<th>defaulting of attributes</th>
  				<td>Yes</td>
  				<td>No</td>
  				<td>Yes</td>
  				<td>Error</td>
            	</tr>
            	<tr>
  				<th>attribute normalization</th>
  				<td>Yes</td>
  				<td>No</td>
  				<td>Yes</td>
  				<td>Error</td>
            	</tr>
            	<tr>
  				<th>checking against model</th>
  				<td>No</td>
  				<td>No</td>
  				<td>Yes</td>
  				<td>Error</td>
            	</tr>
          </table>
  		</a>
  	</faq>
  	<faq title="Associating Data with a Node">
  		<q>How do associate my own data with a node in the DOM tree?</q>
  		<a><p>The class <code>org.apache.xerces.dom.NodeImpl</code> provides a 
  			<code>void setUserData(Object o)</code> and an <code>Object getUserData()</code>
           	method that you can use to attach any object to a node in the DOM tree.</p>
  		</a>
  	</faq>
  	<faq title="Parsing Several Documents">
  		<q>How do I more efficiently parse several documents sharing a common DTD?</q>
  		<a>	<p>DTDs are not currently cached by the parser. The common DTD, since it is 
          	specified in each XML document, will be re-parsed once for each document.</p>
  			<p>However, there are things that you can do now, to make the process of 
  			reading DTD's more efficient:</p>
          	<ul>
            		<li>keep your DTD and DTD references local</li>
            		<li>use internal DTD subsets, if possible</li>
            		<li>load files from server to local client before parsing</li>
            		<li>Cache document files into a local client cache. You should do an 
  					HTTP header request to check whether the document has changed, 
  					before accessing it over the network.</li>
            		<li>Do not reference an external DTD or internal DTD subset at all. 
  					In this case, no DTD will be read.</li>
          	</ul>
  		</a>
  	</faq>
      <faq title="How do access the DOM Level 2 functionality">
      <q></q>
      <a></a>
      </faq>
  </faqs>
  
  
  
  1.1                  xml-0.0/docs/xerces-j/features.xml
  
  Index: features.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Features">
  	<s2 title="Setting Features">
          <anchor id="features"/>
  		<p>To set a feature on either org.apache.xerces.parsers.SAXParser or 
  		org.apache.xerces.parsers.DOMParser, you should use the SAX2 Configurable 
  		interface (org.xml.sax.Configurable).</p>
  		<p>For example, to turn on the validation feature, do:</p>
  		<source>
  SAXParser p=new SAXParser();
  try {
    p.setFeature("http://xml.org/sax/features/validation",true);
  } catch (SAXException e) {
    System.out.println("error in setting up parser feature");
  } 
  		</source>
  
  	</s2>
  	<s2 title="General Features">
  		<p>http://xml.org/sax/features/validation </p>
  		<table>
  			<tr><th>true</th><td>Validate the document.</td></tr>
  			<tr><th>false</th><td>Do not validate the document.</td></tr>
  			<tr><th>Default</th><td>false</td></tr>
  			<tr><th>Note</th>
  				<td>If this feature is set to true, the document must specify a grammar. 
     				If this feature is set to false, the document may specify a grammar 
    				and that grammar will be parsed but no validation of the document 
     				contents will be performed.</td></tr>
  			<tr><th>See</th>
  				<td>http://apache.org/xml/features/validation/dynamic
  				<br/>http://xml.org/sax/features/namespaces</td></tr>
  		</table>
  		<p>http://xml.org/sax/features/external-general-entities</p>
  		<table>
  			<tr><th>true</th><td>Include external general (text) entities.</td></tr>
  			<tr><th>false</th><td>Do not include external general entities.</td></tr>
  			<tr><th>Default</th><td>true</td></tr>
  			<tr><th>See</th>
  				<td>http://xml.org/sax/features/external-parameter-entities</td></tr>
  		</table>
  		<p>http://xml.org/sax/features/external-parameter-entities</p>
  		<table>
  			<tr><th>true</th><td>Include external parameter entities and the external DTD subset.</td></tr>
  			<tr><th>false</th><td>Do not include external parameter entities or the external DTD subset.</td></tr>
  			<tr><th>Default</th><td>true</td></tr>
  			<tr><th>See</th>
  				<td>http://xml.org/sax/features/external-parameter-entities</td></tr>
  		</table>
  		<p>http://xml.org/sax/features/namespaces</p>
  		<table>
  			<tr><th>true</th><td>Perform namespace processing: prefixes will be stripped off element and 
    				 attribute names and replaced with the corresponding namespace URIs. By 
    				 default, the two will simply be concatenated, but the namespace-sep core 
    				 property allows the application to specify a delimiter string for 
    				 separating the URI part and the local part.</td></tr>
  			<tr><th>false</th><td>Do not perform namespace processing.</td></tr>
  			<tr><th>Default</th><td>false</td></tr>
  			<tr><th>Note</th><td>If the validation feature is set to true, then the document must contain 
     				a grammar that supports the use of namespaces.</td></tr>
  			<tr><th>See</th>
  				<td>http://xml.org/sax/features/validation
  				<br/>http://xml.org/sax/properties/namespace-sep</td></tr>
  		</table>
  		<p>http://xml.org/sax/features/use-locator</p>
  		<table>
  			<tr><th>true</th><td>Provide a Locator using the DocumentHandler setDocumentLocator callback.</td></tr>
  			<tr><th>false</th><td>Explicitly allow the parser not to provide a Locator (but it still may).</td></tr>
  			<tr><th>Default</th><td>true</td></tr>
  			<tr><th>Note</th><td>Xerces-J always provides a Locator to the document handler.</td></tr>
  		</table>
  		<p>http://apache.org/xml/features/validation/dynamic</p>
  		<table>
  			<tr><th>true</th><td>The parser will validate the document only if a grammar is specified.</td></tr>
  			<tr><th>false</th><td>Validation is determined by the state of the 
   				  http://xml.org/sax/features/validation feature.</td></tr>
  			<tr><th>Default</th><td>false</td></tr>
  			<tr><th>See</th><td>http://xml.org/sax/features/validation</td></tr>
  		</table>
  		<p>http://apache.org/xml/features/validation/warn-on-duplicate-attdef</p>
  		<table>
  			<tr><th>true</th><td>Warn on duplicate attribute declaration.</td></tr>
  			<tr><th>false</th><td>Do not warn on duplicate attribute declaration.</td></tr>
  			<tr><th>Default</th><td>true</td></tr>
  		</table>
  		<p>http://apache.org/xml/features/validation/warn-on-undeclared-elemdef</p>
  		<table>
  			<tr><th>true</th><td>Warn if element referenced in content model is not declared.</td></tr>
  			<tr><th>false</th><td>Do not warn if element referenced in content model is not declared.</td></tr>
  			<tr><th>Default</th><td>true</td></tr>
  		</table>
  		<p>http://apache.org/xml/features/allow-java-encodings</p>
  		<table>
  			<tr><th>true</th><td>Allow Java encoding names in XMLDecl and TextDecl line.</td></tr>
  			<tr><th>false</th><td>Do not allow Java encoding names in XMLDecl and TextDecl line.</td></tr>
  			<tr><th>Default</th><td>false</td></tr>
  			<tr><th>Note</th><td>A true value for this feature allows the encoding of the file to be 
   				  specified as a Java encoding name as well as the standard ISO encoding 
   				  name. Be aware that other parsers may not be able to use Java encoding 
   				  names. If this feature is set to false, an error will be generated if 
   				  Java encoding names are used.</td></tr>			
  		</table>
  		<p>http://apache.org/xml/features/continue-after-fatal-error</p>
  		<table>
  			<tr><th>true</th><td>Continue after fatal error.</td></tr>
  			<tr><th>false</th><td>Stops parse on first fatal error.</td></tr>
  			<tr><th>Default</th><td>false</td></tr>
  		</table>	
  	</s2>
  	<s2 title="DOM Features">
  		<p>http://apache.org/xml/features/dom/defer-node-expansion</p>
  		<table>
  			<tr><th>true</th><td>Lazy DOM node expansion.</td></tr>
  			<tr><th>false</th><td>Full DOM node expansion.</td></tr>
  			<tr><th>Default</th><td>true</td></tr>
  			<tr><th>Note</th><td>This feature only applies when the 
    				 http://apache.org/xml/properties/dom/document-class-name property is
     				 set to a value other than the name of the default document factory.
     				 If this feature is set to true, the DOM nodes in the returned 
     				 document are expanded as the tree is traversed. This feature allows 
     				 the parser to return a document faster than if the tree is fully 
     				 expanded during parsing and improves memory usage when the whole 
     				 tree is not traversed.</td></tr>
  			<tr><th>See</th><td>http://apache.org/xml/properties/dom/document-class-name</td></tr>
  		</table>	
  		<p>http://apache.org/xml/features/dom/create-entity-ref-nodes</p>
  		<table>
  			<tr><th>true</th><td>Create EntityReference nodes in the DOM tree.</td></tr>
  			<tr><th>false</th><td>Do not create EntityReference nodes in the DOM tree.</td></tr>
  			<tr><th>Default</th><td>true</td></tr>
  			<tr><th>Note</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>
  		</table>	
  	</s2>
  	<s2 title="SAX Features">
  		<p>http://xml.org/sax/features/use-locator</p>
  		<table>
  			<tr><th>true</th><td>Provide a Locator using the DocumentHandler setDocumentLocator callback.</td></tr>
  			<tr><th>false</th><td>Explicitly allow the parser not to provide a Locator (but it still may).</td></tr>
  			<tr><th>Default</th><td>true</td></tr>
  			<tr><th>Note</th><td>Xerces-J always provides a Locator to the document handler</td></tr>
  		</table>
  	</s2>
  </s1> 
  
  
  
  
  1.1                  xml-0.0/docs/xerces-j/feedback.xml
  
  Index: feedback.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Feedback Procedures">
  	<s2 title="Questions or Comments">
  		<p>For all questions or comments, write to the Xerces 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 Xerces-J (1.0.0?) </li>
  			<li>Version number of JDK (1.1.8? 1.2?)</li>
  			<li>Sample XML file that causes the bug</li>
  			<li>Sample Schema file (if required to recreate the bug)</li>
  			<li>Sample DTD file (if required to recreate the bug)</li>			
  		</ul>
  	</s2>
  </s1>
  
  
  
  1.1                  xml-0.0/docs/xerces-j/install.xml
  
  Index: install.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Installation">
  	<s2 title="Unpacking the files">
  		<p>Xerces-J is packaged as a ZIP file for Windows NT and 95/98 and 
  		as a tar.gz file for AIX and all UNIX flavors. You  need to unzip 
  		the Windows distribution into a directory using either unzip or pkzip 
  		or a GUI utility like winzip. The UNIX distribution should first be 
  		uncompressed (using the GNU <ref>gunzip</ref> command). Then run tar -xvf on the 
  		resulting .tar file to extract the files.</p>
  		<s3 title="Windows NT/95/98"> 
  			<ul>
  				<li>unzip Xerces-J-bin.zip</li>
  				<li>This command creates a "xerces" sub-directory in the current 
  				directory containing all the files.</li>
  			</ul>
  		</s3>
  		<s3 title="UNIX (all flavors) "> 
  			<ul>
  				<li>gunzip Xerces-J-bin.tar.gz</li>
  				<li>tar xvf Xerces-bin.tar</li>
  				<li>These commands create a "xerces" sub-directory in the 
  				current directory containing all the files.</li>
  			</ul>
  		</s3>
  	</s2>
  	<s2 title="Files in this release">
  		<table>
  			<tr><td>bin/Xerces-J.jar</td><td>Jar file containing all the parser class files</td></tr>
  			<tr><td>bin/Xerces-J-samples.jar</td><td>Jar file containing all sample class files</td></tr>
  			<tr><td>Readme.html</td><td>This file</td></tr>
  			<tr><td>license.html</td><td>license for Xerces-J Version 1.0</td></tr>
  			<tr><td>w3c_copyright_software.html</td><td>W3C Copyright Notice for DOM</td></tr>
  			<tr><td>apidocs/</td><td>Directory containing Javadoc API for parser framework</td></tr>
  			<tr><td>docs/</td><td>Directory containing other documentation</td></tr>
  			<tr><td>data/</td><td>Directory containing sample XML data files</td></tr>
  			<tr><td>src/</td><td>Source files</td></tr>
  			<tr><td>samples/</td><td>Directory containing sample programs</td></tr>
  		</table>
  	</s2>
  </s1>
  
  
  
  1.1                  xml-0.0/docs/xerces-j/properties.xml
  
  Index: properties.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Properties">
  	<s2 title="Seting Features">
    <anchor id="properties"/>
  		<p>To set a property on either org.apache.xerces.parsers.SAXParser 
  		or org.apache.xerces.parsers.DOMParser, you should use the SAX2 
  		Configurable interface (org.xml.sax.Configurable).</p>
  		<source>
  DOMParser p=new DOMParser();
  try {        
    p.setProperty("http://xml.org/sax/properties/namespace-sep","|");
  } catch (SAXException e) {
    System.out.println("error in setting up parser property");             
  }
  		</source>
  	</s2>
  	<s2 title="General Properties">
  		<p>http://xml.org/sax/properties/namespace-sep</p>
  		<table>
  			<tr>
  				<th>Type:</th>
  				<td>java.lang.String</td>
  			</tr>
  			<tr>
  				<th>Access:</th>
  				<td>read-write</td>
  			</tr>
  			<tr>
  				<th>Desc:</th>
  				<td>The separator string that will appear between the namespace 
  				URI and the local part of the name when namespace processing is being 
  				performed. If the value is the empty string, the two parts will be 
  				concatenated. </td>
  			</tr>
  			<tr>
  				<th>Default:</th>
  				<td>""</td>
  			</tr>
  			<tr>
  				<th>See:</th>
  				<td>http://xml.org/sax/features/namespaces</td>
  			</tr>
  		</table>
  	</s2>
  	<s2 title="DOM Parser Properties">
  		<p>http://apache.org/xml/properties/dom/current-element-node</p>
  		<table>
  			<tr>
  				<th>Type:</th>
  				<td>org.w3c.dom.Node</td>
  			</tr>
  			<tr>
  				<th>Access:</th>
  				<td>read-only</td>
  			</tr>
  			<tr>
  				<th>Desc:</th>
  				<td>The current DOM element node while parsing.</td>
  			</tr>
  			<tr>
  				<th>Note:</th>
  				<td>This property is useful for determining the location 
  					with a DOM document when an error occurs.</td>
  			</tr>
  			<tr>
  				<th>See:</th>
  				<td>http://xml.org/sax/properties/dom-node</td>
  			</tr>
  		</table>
  		<p>http://apache.org/xml/properties/dom/document-class-name</p>
  		<table>
  			<tr>
  				<th>Type:</th>
  				<td>java.lang.String</td>
  			</tr>
  			<tr>
  				<th>Access:</th>
  				<td>read-write</td>
  			</tr>
  			<tr>
  				<th>Desc:</th>
  				<td>The fully qualified class name of the DOM implementation. 
  					The implementation used must have a zero argument constructor.</td>
  			</tr>
  			<tr>
  				<th>Default:</th>
  				<td>"org.apache.xerces.dom.DocumentImpl"</td>
  			</tr>
  			<tr>
  				<th>Note:</th>
  				<td>When the document class name is set to a value other 
  					than the name of the default document factory, the 
  					deferred node expansion feature does not work. </td>
  			</tr>
  			<tr>
  				<th>See:</th>
  				<td>http://apache.org/xml/features/dom/defer-node-expansion</td>
  			</tr>
  		</table>
  	</s2>
  	<s2 title="SAX Parser Properties">
  		<p>http://xml.org/sax/handlers/DeclHandler</p>
  		<table>
  			<tr>
  				<th>Type:</th>
  				<td>org.xml.sax.misc.DeclHandler</td>
  			</tr>
  			<tr>
  				<th>Access:</th>
  				<td>read-write</td>
  			</tr>
  			<tr>
  				<th>Desc:</th>
  				<td>Set the handler for DTD declarations.</td>
  			</tr>
  		</table>
  		<p>http://xml.org/sax/handlers/LexicalHandler</p>
  		<table>
  			<tr>
  				<th>Type:</th>
  				<td>org.xml.sax.misc.LexicalHandler</td>
  			</tr>
  			<tr>
  				<th>Access:</th>
  				<td>read-write</td>
  			</tr>
  			<tr>
  				<th>Desc:</th>
  				<td>Set the handler for lexical parsing events.</td>
  			</tr>
  		</table>
  		<p>http://xml.org/sax/handlers/NamespaceHandler</p>
  		<table>
  			<tr>
  				<th>Type:</th>
  				<td>org.xml.sax.misc.NamespaceHandler</td>
  			</tr>
  			<tr>
  				<th>Access:</th>
  				<td>read-write</td>
  			</tr>
  			<tr>
  				<th>Desc:</th>
  				<td>Set the handler for lexical parsing events.</td>
  			</tr>
  		</table>
  	</s2>
  </s1>
  
  
  
  1.1                  xml-0.0/docs/xerces-j/readme.xml
  
  Index: readme.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Xerces Java">
  	<s2 title="Xerces-J 1.0.0 Release">
  		<p>The Xerces-J 1.0.0 release contains advanced
  		parser functionality, such as XML Schema, DOM Level 2, and SAX version 2,
  		in addition to supporting the industry-standard DOM Level 1 and SAX version 1
  		APIs.</p>
  		<p>Xerces-J v1.0.0 is the first in a series of ongoing updates -- 
  		Watch <jump href="http://xml.apache.org">xml.apache.org</jump> 
  		for new updates. Note that because some of the standards, notably
  		XML Schema, are still not complete, the stable API will definitely be 
  		different from its current form in Xerces-J v1.0.0. This is your chance to give us 
  		feedback on the features that are important to you, and let us know
  		whether the APIs that we are providing are the right ones. Please 
  		direct your feedback to the Xerces mailing list.</p>
  	</s2>
  	<s2 title="License Information">
  		<p>The Xerces-J version 1.0.0 release is available in both source code
  			and precompiled binary (JAR files) form.</p>
  	</s2>
  	<s2 title="Applications of the Xerces-J Parser">
  		<p>The rich generating and validating capabilities allow the Xerces-J 
  		Parser to be used for: </p>
  		<ul>
  			<li>Building XML-savvy Web servers </li>
  			<li>The next generation of vertical applications which will use 
  				XML as their data format. </li>
  			<li>On-the-fly validation for creating XML editors </li>
  			<li>Ensuring the integrity of e-business data expressed in XML </li>
  			<li>Building truly internationalized XML applications. </li>
  		</ul>
  	</s2>
  	<s2 title="XML Schema (alpha) Support">
  		<p>This release includes preliminary support for the W3C XML Schema 
  		Language. The <link idref="schema">Schema</link> page contains a 
  		complete description of the 
  		schema capabilities of this release. We intend to track the W3C XML 
  		Schema Language in subsequent updates of Xerces-J.</p>
  	</s2>
  	<s2 title="DOM Level 2 (alpha) Support">
  		<p>This release include support for the 
  		<jump href="http://www.w3.org/TR/WD-DOM-Level-2">DOM Level 2 Core</jump> and 
  		<jump href="http://www.w3.org/TR/WD-DOM-Level-2">DOM Level 2 Traversal</jump> APIs. 
  		We will be expanding our DOM Level 2 support to include all of DOM Level 2. At the moment, the DOM 
  		Level 2 Traversal API's live in the org.apache.xerces.dom.domx.traversal 
  		package.</p>
  	</s2>
  	<s2 title="SAX 2 (alpha) Support">
  		<p>This release includes support for the <jump href="http://www.megginson.com/SAX/SAX2/">
  		SAX Version 2</jump> API's which are being discussed on the 
  		<jump href="http://www.lists.ic.ac.uk/hypermail/xml-dev/">XML-DEV</jump> mailing list. 
  		These API's are still 
  		under development, so they are subject to change in the future.</p>
  	</s2>
  	<s2 title="Configuration Mechanism">
  		<p>Xerces-J version 1.0.0 uses a collection of methods to configure 
  		various settings in the parser. This release includes a new mechanism 
  		for setting parser switches. This mechanism uses the SAX2 Configurable 
  		interface. We have defined a series of properties and features for the 
  		options available in Xerces-J. The list of features can be found 
  		<link idref="features">here</link>.</p>
  	</s2>
  </s1>
  
  
  
  1.1                  xml-0.0/docs/xerces-j/releases.xml
  
  Index: releases.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Releases">
  	<s2 title="November 5, 1999">
  		<ul>
  			<li>Created initial code base from IBM's XML4J.</li>
  			<li>Modified documentation to reflect new name (Xerces)</li>
  		</ul>
  	</s2>
  
  
  </s1>
  
  
  
  1.1                  xml-0.0/docs/xerces-j/sam-iterator.xml
  
  Index: sam-iterator.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="IteratorView Sample">
  	<s2 title="IteratorView">
  		<p>The IteratorView is an interactive UI sample that displays the DOM tree. It
  		shows the progress of the iteration by moving the selection within the DOM tree.
  		Buttons act as a control panel, allowing the user to interactively iterate through
  		the tree,  remove nodes, add nodes, and view the results immediately in the tree.</p>
  		<p>The IteratorView uses an example filter, NameNodeFilter, that can be controlled
  		from the UI and a DOMTreeFull class that displays the full DOM tree with all
  		the nodes.</p>
  
  		<p>The controls are called through to to the corresponding iterator function. If you
  		are familiar with  the DOM Level 2 Traversal specification, these controls are
  		fairly easy to understand</p>
  
  		<s3 title="Iterator Group">
  		<ul>
  			<li>Next - calls the next() functions and selects the next node in the tree.</li>
  			<li>Previous - calls the previous() function a and selects the previous node in
       		the tree.</li>
  		</ul>
  		</s3>
  		<s3 title="Selected Node Group">
       	<ul>
  			<li>remove - remove the selected Node and update the DOM tree. You
      		 must press an iterator button to see next or  previous node selection. </li>
       		<li>add - add a text node, to see the results of adding a node on the iterator.
       		position. Again you must first press next or previous </li>
  		</ul>
  		</s3>
  		<s3 title="Iterator Settings Group">
       	<ul>
  			<li>createNodeIterator - calls the factory method to create a new iterator 
     			with the corresponding whatToShow and NodenameFilter settings.</li>
  				<ul>
  					<li>The root is set to be the root of the document, so it 
  					starts at the top level each time.</li>
  				</ul>
  			 
  			<li>whatToShow - you can singly or multiply select values and the 
  			iterator is constrained to showing these types.</li>
  			<li>NodeNameFilter - An empty string is converted to null and given 
  			to the NodeNameFilter class.</li>
  				<ul>
  					<li>An empty string matches all nodes.</li>
  					<li>A non-empty string is forced to match node names.</li>
  				</ul>
  			
  		</ul> 
        </s3>
      </s2>      
  	<s2 title="Running IteratorView">                           
  		<code>
      		java dom.traversal.IteratorView &lt;fileName&gt; 
  	 	</code>
  	</s2>
  </s1>
  
  
  
  1.1                  xml-0.0/docs/xerces-j/sam-tree.xml
  
  Index: sam-tree.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="TreeWalker Sample">
      <s2 title="TreeWalker">
          <p>The TreeWalkerviewView is an interactive UI sample that displays the DOM
          tree. It show the progress of the tree traversal by moving the selection within the
          DOM tree. Buttons act as a control panel, allowing the user to interactively
          traverse the tree,  remove nodes, add nodes, and view the results immediately in
          the tree. </p>
          <p>The TreeWalkerviewView uses an example filter, NameNodeFilter, that can be
          controlled from the UI and a DOMTreeFull class that displays the full DOM tree
          with all the nodes.</p>
          <p>The controls are called through to to the corresponding TreeWalker function. If
          you are familiar with the DOM Level 2 Traversal specification, these controls are
          fairly easy to understand.</p>
          <s3 title="Document Order Traversal Group">
              <ul>
                  <li>Next - calls the next() functions and selects the next in the  tree.</li>
                  <li>Previous - calls the previous() function a and selects the previous node in
                  the DOM tree.</li>
              </ul>
          </s3>
          <s3 title="Walk Group">
          <p>Parent, Previous Sibling, Next Sibling, First Child, Last Child - call the
          corresponding function in TreeWalker and show the result as a selected Node.</p>
          </s3>
          <s3 title="Selected Node Group">
              <ul>
                  <li>current - set the current node to the selected node.</li>
                  <li>remove - remove the selected node and update the tree. 
            You must press a button to see next or previous node selection.</li>
                  <li>add - add a text node. 
            You must press a button to see next or previous node selection.</li>
              </ul>
          </s3>
          <s3 title="Filter Settings Group">
              <ul>
                  <li>createNodeTreeWalker - calls the factory method to create a new
                  TreeWalker with the corresponding whatToShow and NodenameFilter
                  settings. The selected node becomes the TreeWalker root.</li>
                  <li>whatToShow - you can singly or multiply select these values by pressing
                  the control key and the TreeWalker is constrained to these types.</li>
                  <li>NodeNameFilter - an empty string is converted to null and given to the
                  NodeNameFilter example filter class provided.</li>
                      <ul>
                          <li>An empty string (null) matches ALL nodes.</li>
                          <li>A non-empty string is  forced to match node names.</li>
                      </ul>
              </ul>
            </s3>     
      </s2>                                                    
      <s2 title="Running TreeWalker">
          <code>
              java dom.traversal.TreeWalkerView &lt;fileName&gt; 
          </code>
      </s2>
  </s1>
  
  
  
  1.1                  xml-0.0/docs/xerces-j/samples.xml
  
  Index: samples.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Samples">
  	<s2 title="Introduction">
  		<p>There are two new samples to test and demonstrate the new DOM2 
  		Transversal implementation: </p>
  		<ul>
  			<li><link idref="iterator">IteratorView</link></li>
  			<li><link idref="tree">TreeWalker</link></li>
  		</ul>
  	</s2>
  	<s2 title="Caveats">
  		<note>Make sure that Xerces-J and a JDK are loaded on 
  		your computer before running any of the sample parsers.</note>
  		<note>Xerces-J: Running the sample applications 
  		requires that you have already loaded the Xerces-J software on 
  		your computer.</note>
  		<note>Java: Running the sample parsers require that your computer has a 
  			correctly installed JDK. If you do not already have a JDK already on your computer download
  		one from Sun's Java website: <jump href="http://java.sun.com">
  		http://java.sun.com</jump> or from IBM's website
  		<jump href="http://www.ibm.com/developer/java/">http://www.ibm.com/developer/java/</jump> 
  		where you can find an "Enhanced Windows	JDK" that is optimized for the Windows platform. 
  		The sample applications
  		described in the following pages support Java 1 - JDK 1.1.6. 1.1.7, 1.1.8 or
  		Java 2 - JDK 1.2.2. </note>
  		<note>UNIX: Command lines in the pages linked below use the Windows path
  		separator ';' (semicolon) and directory separator '\' (backslash).. 
  		On UNIX, use the ':' (colon) character to separate the JAR files in the classpath,
  		and replace Windows directory separator '\' (backslash) with '/' (forward slash).</note>
  	</s2>
  	<s2 title="IteratorView Sample">
  		<p>The IteratorView is an interactive UI sample that displays the DOM tree. It
  		shows the progress of the iteration by moving the selection within the DOM tree.
  		Buttons act as a control panel, allowing the user to interactively iterate through
  		the tree,  remove nodes, add nodes, and view the results immediately in the tree.</p>
  		<p>The IteratorView uses an example filter, NameNodeFilter, that can be controlled
  		from the UI and a DOMTreeFull class that displays the full DOM tree with all
  		the nodes.</p>
  		<p><link idref="iterator">IteratorView page</link></p>
  	</s2>
  	<s2 title="TreeWalker Sample">
  		<p>The TreeWalkerviewView is an interactive UI sample that displays the DOM
  		tree. It show the progress of the tree traversal by moving the selection within the
  		DOM tree. Buttons act as a control panel, allowing the user to interactively
  		traverse the tree,  remove nodes, add nodes, and view the results immediately in
  		the tree.</p>
  
  		<p>The TreeWalkerviewView uses an example filter, NameNodeFilter, that can be
  		controlled from the UI and a DOMTreeFull class that displays the full DOM tree
  		with all the nodes.</p>
  		<p><link idref="tree">TreeWalkerView page</link></p>
  	</s2>
  </s1>
  
  
  
  1.1                  xml-0.0/docs/xerces-j/schema.xml
  
  Index: schema.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Schema">
  	<s2 title="Disclaimer">
  		<p>This package contains an implementation of the W3C XML 
  		Schema language. This implementation is experimental. The 
  		XML Schema language is still in working draft stage: you 
  		should not consider this implementation complete or correct. 
  		The limitations of this implementation are detailed below -- 
  		please read this document before using this package.</p>
  	</s2>
  	<s2 title="Introduction">
  		<p>This package contains an implementation of a subset 
  		of the W3C XML Schema Language as specified in the 24 
  		September 1999 Working Draft. The parsers contained in this 
  		package are able to read and validate XML documents with the 
  		grammar specified in either DTD or XML Schema format.</p>
  		<p>We are making this package available in order to get 
  		feedback on the features in the XML Schema language 
  		design and on representing an XML document's grammar 
  		as part of the document's DOM tree. We intend to update 
  		this package until it implements all of the functionality 
  		of the then current XML Schema Working Draft. If you are 
  		interested in a particular unimplemented feature, we welcome 
  		your feedback on the Xerces mailing list.</p>
  	</s2>
  	<s2 title="Limitations">
  		<p>The XML Schema implementation in this package is a 
  		subset of the features defined in the 24 September 1999 
  		XML Schema Working Drafts.</p>
  	</s2>
  	<s2 title="Structure Limitations">
  		<ul>
  			<li>elementDecls, archeTypes, modelGroups and attributeGroup 
  			share the same namespace</li>
  			<li>All archetypes, elements, modelGroups and attributeGroups 
  			must be declared before they are used.</li>
  			<li>On archetypes the following are unsupported:</li>
  				<ul>
  					<li>open, refine-able, and closed models</li>
  					<li>nested element decls</li>
  				</ul>
  			<li>None of the items in section 5, import, inclusion, export, 
  			or refinement, are supported.</li>
  		</ul>
  	</s2>
  	<s2 title="Datatype Limitations">
  		<ul>
  			<li>Datatype checking conforms to underlying Java types, not 
  			necessarily to schema rules:
  				<table>
  					<tr><th>Schema type</th><th>Java type</th></tr>
  					<tr><td>boolean</td><td>Boolean</td></tr>
  					<tr><td>integer</td><td>Integer</td></tr>
  					<tr><td>decimal</td><td>Double</td></tr>
  					<tr><td>real</td><td>Double</td></tr>
  				</table>
  			</li>
  			<li>The NMTOKEN, NMTOKENS, Name, NCName, ID, IDREF,
  			ENTITY, ENTITIES, NOTATION are only supported on attributes. At
  			the moment they cannot be applied to element content.</li>
  			<li>The timeInstant, timeDuration, recurringInstant, date, time, 
  			binary, uri, and language datatypes are not supported.</li>
  			<li>Datatype qualifiers on attributes are not supported.</li>
  	 </ul>
  	</s2>
  	<s2 title="Other Limitations">
  		<p>The schema is specified by the first xmlns attribute on the root 
  		element of the document. There must be an attribute declaration for 
  		this xmlns attribute. </p>
  	</s2>
  	<s2 title="Usage">
  		<p>In this release, schema validation has been integrated with the 
  		regular SAXParser and DOMParser classes. No special classes are 
  		required to parse documents that use a schema.</p>
  		<p>Documents that use XML Schema grammars specify the location of the
  		grammar using an xmlns attribute attached to the root / top-level element 
  		in the document. Here is an example: </p>
  		<source>
  &lt;document xmlns=&amp;document.xsd&gt;
  ...
  &lt;/document&gt;
  		</source>
  		<p>Another requirement is that the XML Schema document's grammar must 
  		have a &lt;!DOCTYPE ...&gt; line specifying the DTD for XML Schema grammar. 
  		The DOCTYPE must specify the following system identifier:<br/>
  		<code>
  http://www.w3.org/XML/Group/1999/09/23-xmlschema/structures/structures.dtd
  		</code>
  		</p>
  		<p>Also, there must be an attribute declaration for the xmlns attribute 
  		used to find the schema (document in the example above).</p>
  		<p>Review the sample file, "data/personal.xsd" for an example of an XML 
  		Schema grammar.</p>
  	</s2>
  </s1>
  
  
  
  1.1                  xml-0.0/docs/xerces-p/readme.xml
  
  Index: readme.xml
  ===================================================================
  <?xml version="1.0" standalone="no"?>
  <!DOCTYPE s1 SYSTEM "../dtd/document.dtd">
  
  <s1 title="Xerces Perl">
    <s2 title="Xerces-P version 1.0">
      <p>
        A Perl wrapper is provided for the C++ version of Xerces, which allows 
        access to a fully validating DOM XML parser from Perl. It also 
        provides for full access to Unicode strings, since Unicode is a key 
        part of the XML standard. 
      </p>
      <p>
        Additional documentation to be provided soon. Watch this space.
      </p>
    </s2>
  </s1>
  
  

Mime
View raw message