forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: xml-forrest/src/documentation/content/xdocs validation.xml
Date Fri, 15 Nov 2002 07:26:19 GMT
crossley    2002/11/14 23:26:19

  Modified:    src/documentation/content/xdocs validation.xml
  Minor tweaks as i read it.
  Link to Cocoon documentation "Entity resolution with catalogs".
  Revision  Changes    Path
  1.5       +9 -8      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.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- validation.xml	15 Nov 2002 05:28:57 -0000	1.4
  +++ validation.xml	15 Nov 2002 07:26:19 -0000	1.5
  @@ -100,7 +100,7 @@
           The <code>failonerror</code> properties only work for files validated
           with &lt;xmlvalidate&gt;, not (yet) for those validated
  -        with&lt;jing&gt;, where <code>failonerror</code> defaults to
  +        with &lt;jing&gt;, where <code>failonerror</code> defaults
  @@ -114,7 +114,7 @@
           associating public identifiers (<code>-//APACHE//DTD Documentation
             V1.1//EN</code> above) with DTDs.
           If you <link href="your-project.html#adding_new_content_type">add a new content
type</link>, you
  -        should add the DTD to <code>${project.schema-dir}/dtd/</code>, and
  +        should add the DTD to <code>${project.schema-dir}/dtd/</code> and add
           an entry to the <code>${project.schema-dir}/catalog</code> file.  This
           section describes the details of this process.
  @@ -229,7 +229,7 @@
               entities</link>.  They are like macros, whose content will be
             inserted when a parameter-entity reference, like
  -          <code>%common-charents;</code> or <code>%document;</code>,
  +          <code>%common-charents;</code> or <code>%document;</code>
  @@ -250,7 +250,7 @@
               5: Customizing DocBook</link> of Norman Walsh's "DocBook: The
  -          Definitive Guide" gives a fuller overview of the process of
  +          Definitive Guide" gives a complete overview of the process of
             customizing a DTD.
  @@ -274,7 +274,8 @@
             Catalog file.</p>
             See <link href="&catalog_intro;">this article</link> for a good
  -          introduction to catalogs.
  +          introduction to catalogs and the Cocoon documentation
  +          <link href="">Entity
resolution with catalogs</link>.
             Forrest provides a standard catalog file,
  @@ -299,11 +300,11 @@
             with catalog B.  In our case, A is a custom project's catalog snippet,
             and B is the Forrest catalog.  Secondly, Cocoon does not (without
             tweaking) deal with more than one catalog file, so if your project
  -          defines <code>${project.schema-dir}/catalog</code>, then you will
  +          defines <code>${project.schema-dir}/catalog</code> then you will
             likely get errors about 'cannot resolve book-cocoon-v10.dtd'.  Until
             this is fixed (all help appreciated!) it is currently simpler just to
             hand-validate custom XML files, use
  -          <code>project.validate.xdocs.excludes</code>to prevent validation
  +          <code>project.validate.xdocs.excludes</code> to prevent validation
             new doc types and comment out the DOCTYPE declaration so Cocoon
             doesn't complain.

View raw message