cocoon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: xml-cocoon2/documentation/xdocs contrib.xml
Date Tue, 23 Oct 2001 08:08:31 GMT
crossley    01/10/23 01:08:31

  Modified:    documentation/xdocs Tag: cocoon_20_branch contrib.xml
  changed disscussion of "" to be "cocoon.xconf"
  fix broken external link to
  Revision  Changes    Path
  No                   revision
  No                   revision   +2 -2      xml-cocoon2/documentation/xdocs/contrib.xml
  Index: contrib.xml
  RCS file: /home/cvs/xml-cocoon2/documentation/xdocs/contrib.xml,v
  retrieving revision
  retrieving revision
  diff -u -r1.1.2.1 -r1.1.2.2
  --- contrib.xml	2001/10/05 09:31:12
  +++ contrib.xml	2001/10/23 08:08:30
  @@ -158,7 +158,7 @@
    <s2 title="Documentation Requirements for @docname@ Distribution">
     <p>All new features (processor, logicsheets, config options etc.) should be documented
  -   appropriately (in XML or in in the case of config options).</p>
  +   appropriately (in XML or in <code>cocoon.xconf</code> in the case of config
     <p>Use something like <code>xdocs/index.xml</code> as a rough guide,
      the new page(s) to <code>xdocs/site-book.xml</code> and <code>xdocs/docs-book.xml</code>,
  @@ -368,7 +368,7 @@
       matter, use a 
       <link href="">validating parser</link>
       (one that is tried and true is
  -    <link href="http://www.jclark/sp/">SP/nsgmls</link>).
  +    <link href="">SP/nsgmls</link>).
       This procedure will detect errors without having to go through the whole
       <code>build docs</code> process to find them. Do not expect @docname@
       or the build system to detect the validation errors for you - they can

In case of troubles, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message