dleslie     00/10/17 05:54:58

  Modified:    java/xdocs/sources/xalan commandline.xml extensions.xml
                        getstarted.xml samples.xml whatsnew.xml
  Log:
  Revised per Shane's review comments.
  
  Revision  Changes    Path
  1.6       +2 -2      xml-xalan/java/xdocs/sources/xalan/commandline.xml
  
  Index: commandline.xml
  ===================================================================
  RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/commandline.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- commandline.xml   2000/10/16 21:56:57     1.5
  +++ commandline.xml   2000/10/17 12:54:57     1.6
  @@ -97,7 +97,7 @@
   -XML (Use XML formatter and add XML header)
   -TEXT (Use simple Text formatter)
   -HTML (Use HTML formatter)
  --PARAM name expression (Set a stylesheet parameter)
  +-PARAM name value (Set a stylesheet parameter)
   -DIAG put out timing diagnostics</source>
         <p>Use -IN to specify the XML source document.</p> 
         <p>Use -XSL to specify the XSL stylesheet file.</p>
  @@ -106,6 +106,6 @@
         <p>Use -HTML to write 4.0 transitional HTML (some elements, such as 
&lt;br&gt;, are
         not well formed XML).</p>
         <p>To set stylesheet parameters from the command line, use <br/>
  -      <code>TestXSLT -PARAM <ref>name expression</ref></code></p>
  +      <code>java org.apache.xalan.xslt.Process -PARAM <ref>name 
value</ref></code></p>
      </s2>
   </s1>
  
  
  
  1.6       +1 -3      xml-xalan/java/xdocs/sources/xalan/extensions.xml
  
  Index: extensions.xml
  ===================================================================
  RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/extensions.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- extensions.xml    2000/10/16 21:56:57     1.5
  +++ extensions.xml    2000/10/17 12:54:57     1.6
  @@ -35,7 +35,7 @@
       <td><em>Requirements</em></td>
     </tr>
     <tr>
  -    <td>Mozilla Rhino<br/><br/></td>
  +    <td>Mozilla Rhino (JavaScript)<br/><br/></td>
       <td>1.5<br/><br/></td>
       <td>js.jar available from 
                                    http://www.mozilla.org/rhino<br/><br/></td>
  @@ -143,7 +143,6 @@
   <s3 title="1. Declare the lxslt namespace">
   <p><br/><code>xmlns:lxslt="http://xml.apache.org/xslt";</code></p>
   <p>The lxslt namespace provides support for the lxslt:component element and 
lxslt:script subelement.</p>
  -<note>You may also use the LotusXSL alias for this namespace: 
"http://xsl.lotus.com/";.</note>
   </s3>
   <s3 title="2. Declare a unique namespace for each extension prefix">
   <p><br/><code>xmlns:<ref>prefix</ref>=<ref>URI</ref></code></p>
  @@ -314,7 +313,6 @@
   <p>The java namespace supports the use of extension functions implemented in 
Java. You cannot use this syntax with extension elements or with extensions 
implemented in JavaScript or another scripting language.</p>
   <s3 title="Declare the Xalan java namespace">
   <p><code>xmlns:lxslt="http://xml.apache.org/xslt/java";</code></p>
  -<note>You may also use the LotusXSL alias for this namespace: 
"http://xsl.lotus.com/java";.</note>
   </s3>
   <s3 title="Use the java namespace when you make extension function calls">
   <p>Use "java" as the prefix with the syntax described in <link 
anchor="ext-func-calls">Extension function Java calls</link>.</p>
  
  
  
  1.5       +1 -1      xml-xalan/java/xdocs/sources/xalan/getstarted.xml
  
  Index: getstarted.xml
  ===================================================================
  RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/getstarted.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- getstarted.xml    2000/10/16 16:48:07     1.4
  +++ getstarted.xml    2000/10/17 12:54:57     1.5
  @@ -20,7 +20,7 @@
   <p>You can get the JDK or JRE from <jump 
href="http://www.ibm.com/java/jdk";>ibm.com/java/jdk/</jump> or <jump 
href="http://www.java.sun.com";>java.sun.com</jump>.</p> 
   <p>Download <resource-ref idref="xslt4j-dist-zip"/> or <resource-ref 
idref="xslt4j-dist-targz"/>. Both of these files contain <resource-ref 
idref="xslt4j-current"/> (with xalan.jar) and xerces.jar from <resource-ref 
idref="xml4j-used"/>. You can use a zip or tar utility to expand these files 
into a full build.</p>
   
  -<p>If you plan to run <link idref="extensions">XSLT extensions</link>, you 
need bsf.jar, which is included in the &xslt4j; distribution. If you plan to 
run XSLT extensions implemented in JavaScript or another scripting language, 
you will need one or more additional files as indicated in <link 
idref="extensions" anchor="supported-lang">extensions language 
requirements</link>.</p>
  +<p>If you plan to run <link idref="extensions">XSLT extensions</link>, you 
need bsf.jar, which is included in the &xslt4j; distribution. If you plan to 
run XSLT extensions implemented in Javascript or another scripting language, 
you will need one or more additional files as indicated in <link 
idref="extensions" anchor="supported-lang">extensions language 
requirements</link>.</p>
   </s2><anchor name="classpath"/>
   <s2 title="Setting up the system class path">
   <p>At the very minimum, you must include xalan.jar and xerces.jar (or 
another conformant XMLReader -- see <link idref="usagepatterns" 
anchor="xmlreader">Setting the XMLReader</link>) on the system class path. To 
run the sample applications, include xalansamples.jar (all samples other than 
the servlet) and xalanservlet.jar. To run extensions, include bsf.jar. All 
these JAR files are distributed with &xslt4j;. For extensions implemented in 
JavaScript or another scripting language, see <link idref="extensions" 
anchor="supported-lang">extensions language requirements</link> to identify any 
additional JAR files you must place on the class path and where you can get 
them.</p>
  
  
  
  1.11      +3 -3      xml-xalan/java/xdocs/sources/xalan/samples.xml
  
  Index: samples.xml
  ===================================================================
  RCS file: /home/cvs/xml-xalan/java/xdocs/sources/xalan/samples.xml,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- samples.xml       2000/10/16 21:56:58     1.10
  +++ samples.xml       2000/10/17 12:54:57     1.11
  @@ -111,7 +111,7 @@
          and prints the output to System.out. The stylesheet parameter appears 
as a text node in the output.</p>
       <p>Run this sample from the UseStylesheetParam subdirectory with</p> 
       <p><code>java UseStylesheetParam <ref>param</ref></code></p>
  -    <p>where <ref>param</ref> is the stylesheet parameter (a string of your 
choice).</p>  
  +    <p>where <ref>param</ref> is the stylesheet parameter value (a string of 
your choice).</p>  
       </s2><anchor name="sax2sax"/>
     <s2 title="SAX2SAX">
     <p>What it does: Explicitly set the SAX XMLReader and SAX ContentHandler 
for processing the stylesheet, processing the XML input, and producing the 
output.</p>
  @@ -230,7 +230,7 @@
         redirected output from the XML input file.</p>
         </s3><anchor name="ext2"/>
         <s3 title="2-basicJscript">
  -      <p>What it does: Uses an extension element and extension function 
implemented in Javascript to compute a
  +      <p>What it does: Uses an extension element and extension function 
implemented in JavaScript to compute a
         deadline for responding to a customer inquiry.</p>
         <p>Run this sample from the extensions subdirectory with</p>
         <p><code>java org.apache.xalan.xslt.Process -in 
2-basicJscript.xml</code>
  @@ -251,7 +251,7 @@
           <br/>&nbsp;&nbsp;<code>-xsl 4-numlistJava.xsl</code></p>    
         </s3><anchor name="ext5"/>
         <s3 title="5-numlistJscript">
  -      <p>What it does: Uses a Javascript  extension to transform a set of 
name elements into a numbered and
  +      <p>What it does: Uses a JavaScript  extension to transform a set of 
name elements into a numbered and
         alphabetized list. This sample performs the same operations as the 
preceding Java extension.</p>
       <p>Run this sample from the extensions subdirectory with</p>
         <p><code> java org.apache.xalan.xslt.Process -in numlist.xml</code>
  
  
  
  1.12      +9 -4      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.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- whatsnew.xml      2000/10/16 21:56:58     1.11
  +++ whatsnew.xml      2000/10/17 12:54:58     1.12
  @@ -62,12 +62,12 @@
     <li><link anchor="packages">Package layout</link></li>
   </ul><anchor name="design"/>
     <s2 title="New Design">
  -  <p>&xslt4j2; represents a fundamental redesign of Xalan. The primary 
objective of this redesign is an easier-to-use, more understandable, and more 
modular API that that encourages wider participation in its ongoing development 
by the open-source XML developer community, and that lends itself to 
"streaming," the production of transformation output while the input is still 
being parsed.</p>
  +  <p>With respect to &xslt4j; 1.x, &xslt4j2; represents a fundamental 
redesign of Xalan. The primary objective of this redesign is an easier-to-use, 
more understandable, and more modular API that that encourages wider 
participation in its ongoing development by the open-source XML developer 
community, and that lends itself to "streaming," the production of 
transformation output while the input is still being parsed.</p>
   <p>As a result of this redesign, the changes are global in nature. The API 
and the basic usage patterns are different. For the details, see <link 
idref="usagepatterns">Basic Usage Patterns</link>.</p>
   <p>To start with, &xslt4j2; implements the <resource-ref idref="trax"/> 
interfaces. A number of open-source XML tool developers have collaborated on 
TRaX, a conceptual framework and a standard API for performing XML 
transformations. We strongly encourage you to use the TRaX framework and 
interfaces when you use &xslt4j2; to perform XML transformations.</p>
   <p>The basic organization of TRaX is quite simple: use a Processor to 
process transformation instructions (the stylesheet), producing a Templates 
object. Use the Templates object to instantiate a Transformer, with which you 
can apply the Templates object to XML input, producing a result tree. For more 
detail, see <link idref="usagepatterns" anchor="basic">Basic steps</link>.</p>
       <p>&xslt4j2; builds on <resource-ref idref="sax2"/>, <resource-ref 
idref="dom2"/>, and the <resource-ref idref="jaxp"/>. For example, &xslt4j2; 
incorporates the SAX parsing event model in its support for the incremental 
production of transformation output.</p>
  -    <p>In conjunction with TRaX, &xslt4j; gathers basic operational settings 
from Java system property settings. System properties, for example, identify 
the stylesheet processor and XMLReader to use, and the serializers that are 
available for various output methods. You can set these system properties on 
the command line, in your applications, or by editing the properties files that 
&xslt4j; uses for system properties that you do not set. The default settings 
in these files (as shipped) point to the Xalan StylesheetProcessor, the 
serializers shipped with Xerces, and the Xerces SAXParser.</p>
  +    <p>In conjunction with TRaX, &xslt4j; gathers basic operational settings 
from Java system property settings. System properties, for example, identify 
the stylesheet processor and XMLReader to use, and the serializers that are 
available for various output methods. You can set these system properties on 
the command line, in your applications, or by editing the properties files that 
&xslt4j; uses for system properties that you do not set. The default settings 
in these files (as shipped) point to the Xalan StylesheetProcessor, the 
serializers shipped with Xalan, and the Xerces SAXParser.</p>
   </s2><anchor name="packages"/>
     <s2 title="Package layout">
     <p>The new class package structure is flatter and maps closely to the TRaX 
framework. For example, you use the
  @@ -104,6 +104,10 @@
         </gloss>
      <p>Other packages include:</p>
      <gloss>
  +     <label><jump 
href="apidocs/org/apache/xalan/xslt/package-summary.html">org.apache.xalan.xslt</jump></label>
  +      <item>Xalan <link idref="commandline">command-line utility</link> for 
performing transformations.</item>
  +    </gloss>   
  +   <gloss>
        <label><jump 
href="apidocs/org/apache/xalan/stree/package-summary.html">org.apache.xalan.stree</jump></label>
         <item>Implementation of DOM source tree optimized for node retrieval 
and XSLT processing.</item>
       </gloss>
  @@ -136,11 +140,11 @@
         </gloss> 
      <p>Other packages that are included in the xml-xalan source tree and 
xalan.jar:</p> 
          <gloss>
  -    <label><jump href="">javax.xml.parsers</jump></label>
  +    <label><jump 
href="apidocs/org/javax/xml/parsers/package-summary.html">javax.xml.parsers</jump></label>
         <item>The xml.apache.org implementation of <resource-ref 
idref="jaxp"/>.</item>
         </gloss>
      <gloss>
  -      <label><jump href="">serialize</jump> packages</label>
  +      <label><jump 
href="apidocs/org/apache/serialize/package-summary.html">org.apache.serialize</jump>
 and <jump 
href="apidocs/org/apache/xml/serialize/transition/package-summary.html">org.apache.xml.serialize.transition</jump>
 packages</label>
         <item>Output transformation result trees as a stream.</item>
         </gloss>
      <gloss>
  @@ -151,5 +155,6 @@
        <label><jump 
href="apidocs/org/w3c/dom/package-summary.html">org.w3.dom</jump> 
packages</label>
        <item>DOM level 2 interfaces.</item>
      </gloss>
  +   <note>As actions are taken by the relevant standards organizations, the 
TrAX and serializer packages are subject to change in future releases.</note>
   </s2>
   </s1>
  
  
  

Reply via email to