forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject cvs commit: xml-forrest/src/documentation/content/xdocs validation.xml
Date Sat, 16 Nov 2002 08:22:31 GMT
crossley    2002/11/16 00:22:31

  Modified:    src/documentation/content/xdocs validation.xml
  Log:
  Explain how to configure your project OASIS catalog via the "local-catalog"
  parameter in your ${project.content-dir}/WEB-INF/cocoon.xconf
  
  Revision  Changes    Path
  1.8       +14 -9     xml-forrest/src/documentation/content/xdocs/validation.xml
  
  Index: validation.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/validation.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- validation.xml	15 Nov 2002 09:19:38 -0000	1.7
  +++ validation.xml	16 Nov 2002 08:22:31 -0000	1.8
  @@ -24,8 +24,8 @@
         <p>
           By default, Forrest will try to validate your XML before generating
           HTML or a webapp from it, and fail if any XML files are not valid.
  -        Validation can be performed manually by typing 'forrest validate' in
  -        the project root.
  +        Validation can be performed manually by typing
  +        '<code>forrest validate</code>' in the project root.
         </p>
         <p>
           For an XML file to be valid, it <em>must</em> have a DOCTYPE
  @@ -279,11 +279,16 @@
             <link href="http://xml.apache.org/cocoon/userdocs/concepts/catalog.html">Entity
resolution with catalogs</link>.
           </note>
           <p>
  -          Forrest provides a standard catalog file,
  -          <code>xml-forrest/src/resources/schema/catalog</code>, for document
  -          types it provides.  Projects can augment this with their own catalog
  -          file in <code>${project.schema-dir}/catalog</code>.  Here is what
ours
  -          should look like:
  +          Forrest provides a standard catalog file at
  +          <code>xml-forrest/src/resources/schema/catalog</code> for the document
  +          types that Forrest provides.  Projects can augment this with their
  +          own catalog file in <code>${project.schema-dir}/catalog</code>.
  +          Add the "local-catalog" parameter to your
  +          <code>${project.content-dir}/WEB-INF/cocoon.xconf</code> as described
  +          in that file.
  +        </p>
  +        <p>
  +          Here is what our OASIS catalog should look like:
           </p>
           <source>
             -- OASIS TR 9401 Catalog for our project --
  @@ -317,7 +322,7 @@
           </p>
           <p>
             We now have a custom DTD and a catalog mapping which lets Forrest
  -          locate the DTD.  Now if we were to run <code>forrest validate</code>,
  +          locate the DTD.  Now if we were to run '<code>forrest validate</code>'
             our download file would validate along with all the others.
           </p>
         </section>
  
  
  

Mime
View raw message