cvs commit: xml-xalan/java/xdocs/sources/xalan whatsnew.xml

[dl...@locus.apache.org]

dleslie     00/09/06 14:22:07

  Modified:    java/xdocs/sources/xalan whatsnew.xml
  Log:
  Editorial updates.
  
  Revision  Changes    Path
  1.4       +2 -1      xml-xalan/java/xdocs/sources/xalan/whatsnew.xml
  
  Index: whatsnew.xml
  ===================================================================
  RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/whatsnew.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- whatsnew.xml	2000/08/28 21:29:08	1.3
  +++ whatsnew.xml	2000/09/06 21:22:04	1.4
  @@ -107,7 +107,8 @@
     <p>The trax.Processor static newInstance() method with "xslt" as its argument instantiates the processor designated by the trax.processor.xslt system property. If this system property has not already been set, trax.Processor sets it from a file. For &xslt4j;, this system property should be set to org.apache.xalan.processor.StylesheetProcessor.</p>
   </s2><anchor name="process"/>
     <s2 title="2. Process the stylesheet, producing a Templates object">
  -  <p>The Templates object is an immutable runtime representation of the structure and content of a stylesheet (which may incorporate via includes and imports multiple stylesheet sources).</p>
  +  <p>The Templates object is an immutable runtime representation of the structure and content of a stylesheet (which may include
  +  and import multiple stylesheet sources).</p>
   <p>A given Templates object may be used repeatedly and by multiple concurrent threads for the transformation of XML input. Each Templates object also incorporates XSLTSchema, which encapsulates the underlying XSLT stylesheet schema.</p>
     <p>You may provide the stylesheet as a SAX input source (from a file or stream) or as a DOM tree.</p>
     <p>Use the Processor process() method with a SAX input source (as in the example above), or the processFromNode() method with a DOM tree to generate a Templates object.</p>