You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xalan.apache.org by dl...@apache.org on 2001/08/10 21:16:43 UTC

cvs commit: xml-xalan/c/xdocs/sources/xalan extensions.xml extensionslib.xml readme.xml samples.xml

dleslie     01/08/10 12:16:43

  Modified:    c/xdocs/sources entities.ent
               c/xdocs/sources/xalan extensions.xml extensionslib.xml
                        readme.xml samples.xml
  Log:
  Updates for 1.2
  
  Revision  Changes    Path
  1.20      +1 -1      xml-xalan/c/xdocs/sources/entities.ent
  
  Index: entities.ent
  ===================================================================
  RCS file: /home/cvs/xml-xalan/c/xdocs/sources/entities.ent,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- entities.ent	2001/08/09 20:10:36	1.19
  +++ entities.ent	2001/08/10 19:16:43	1.20
  @@ -3,7 +3,7 @@
   <!ENTITY xslt4c "Xalan-C++">
   <!ENTITY xslt4c-dist "Xalan-C_1_2">
   <!ENTITY xslt4c-current "Xalan-C++ version 1.2">
  -<!ENTITY xslt4c-windlls "DOMSupport.dll, PlatformSupport.dll, XalanDOM.dll, XalanSourceTree,dll, XercesParserLiaison.dll, XMLSupport.dll, XPath.dll, XSLT.dll, XalanTransformer.dll">
  +<!ENTITY xslt4c-windlls "DOMSupport.dll, PlatformSupport.dll, XalanDOM.dll, XalanSourceTree,dll, XercesParserLiaison.dll, XMLSupport.dll, XPath.dll, XSLT.dll, XalanTransformer.dll, XalanExtensions.dll">
   <!ENTITY xslt4c-linuxlib "libxalan-c1_2.so">
   <!ENTITY xslt4c-aixlib "libxalan-c1_2.a">
   <!ENTITY xslt4c-hplib "libxalan-c1_2.sl">
  
  
  
  1.14      +1 -1      xml-xalan/c/xdocs/sources/xalan/extensions.xml
  
  Index: extensions.xml
  ===================================================================
  RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/extensions.xml,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- extensions.xml	2001/06/08 20:16:06	1.13
  +++ extensions.xml	2001/08/10 19:16:43	1.14
  @@ -65,7 +65,7 @@
   <li><link anchor="use">Using an extension function</link></li>
   </ul><anchor name="intro"/>
     <s2 title="Introduction">
  -<p>At times, you may want to call your own custom C functions from a stylesheet. For these situations, &xslt4c; supports the creation and use of extension functions.</p>
  +<p>At times, you may want to call your own custom C functions from a stylesheet. For these situations, &xslt4c; supports the creation and use of extension functions &xslt4c; also provides a <link idref="extensionslib">library of extension elements</link> for your use.</p>
   <p>You can think of extension functions as extending the core library of functions that XPath provides. Like the
   XPath functions, an extension function returns an XObject, which may contain a value of any of the five XSLT
   data types: node-set, result-tree-fragment, string, boolean, or number.</p> 
  
  
  
  1.2       +1 -1      xml-xalan/c/xdocs/sources/xalan/extensionslib.xml
  
  Index: extensionslib.xml
  ===================================================================
  RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/extensionslib.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- extensionslib.xml	2001/08/09 20:10:36	1.1
  +++ extensionslib.xml	2001/08/10 19:16:43	1.2
  @@ -69,7 +69,7 @@
   <li><link anchor="hassamenodes">hasSameNodes</link></li>
   </ul><anchor name="intro"/>
   <s2 title= "Introduction">
  -<p>Extension elements and functions provide a powerful mechanism
  +<p>Extension functions provide a powerful mechanism
   for extending and simplifying what you can do with an XLST processor like
   Xalan. With input and contributions from the XML open-source developer community, we are working on placing the most useful
   extensions in an extensions library distributed with &xslt4c;. If you have ideas and/or contributions you would like to make, please email us at the <human-resource-ref idref="xalandev"/>.</p>
  
  
  
  1.28      +2 -2      xml-xalan/c/xdocs/sources/xalan/readme.xml
  
  Index: readme.xml
  ===================================================================
  RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/readme.xml,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  --- readme.xml	2001/08/09 20:16:11	1.27
  +++ readme.xml	2001/08/10 19:16:43	1.28
  @@ -78,9 +78,9 @@
      </ul>
        <anchor name="done"/>
     <s3 title="Changes since &xslt4c; version 1.1">
  -     <p>TO BE ADDED</p>
  +    <p>Major updates since version 1.1 include:</p>
        <ul>
  -      <li><link idref="extensionslib">Set of extension functions</link></li>
  +      <li><link idref="extensionslib">Introduction of a library of extension functions</link></li>
         <li></li>      
         <li></li>
         <li></li>
  
  
  
  1.29      +5 -5      xml-xalan/c/xdocs/sources/xalan/samples.xml
  
  Index: samples.xml
  ===================================================================
  RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/samples.xml,v
  retrieving revision 1.28
  retrieving revision 1.29
  diff -u -r1.28 -r1.29
  --- samples.xml	2001/08/09 20:10:36	1.28
  +++ samples.xml	2001/08/10 19:16:43	1.29
  @@ -133,8 +133,8 @@
        <p>See also: <link idref="usagepatterns" anchor="params">Setting stylesheet parameters</link>.</p>     
     </s2><anchor name="xalantransformercallback"/>
     <s2 title="XalanTransformerCallback">
  -  <p>What it does: it returns transformation output in blocks to a callback function, which writes the output to a file.
  -  This sample illustrats the use of a callback function to incrementally process a transformation result, that is to begin
  +  <p>What it does: Return transformation output in blocks to a callback function, which writes the output to a file.
  +  This sample illustrates the use of a callback function to incrementally process a transformation result, that is to begin
     working with the transformation result before the transformation has beeen completed. See <link idref="usagepatterns"
     anchor="incremental">Processing output incrementally</link>.</p>
     <p>You can run it from the XalanTransformerCallback subdirectory with</p>
  @@ -189,7 +189,7 @@
     <p><code>DocumentBuilder</code></p>
     </s2><anchor name="threadsafe"/>
     <s2 title="ThreadSafe (Windows32 Only)">
  -  <p>What it does: multiple threads use a single compiled stylesheet (StylesheetRoot) and DOM source tree (XalanNode) to perform
  +  <p>What it does: Multiple threads use a single compiled stylesheet (StylesheetRoot) and DOM source tree (XalanNode) to perform
     transformations concurrently. The application tracks the progress of the threads in messages to the screen, and each thread
     writes its own output file. Imagine a server application responding to multiple clients who happen to request the same
     transformation.</p>
  @@ -214,8 +214,8 @@
       executable is XPathWrapper.</p> 
     </s2><anchor name="simplexpathapi"/>
     <s2 title="SimpleXPathAPI">
  -  <p>What it does: uses the XPathEvaluator interface to evaluate an XPath expression from the specified context node of 
  -  an XML file, and displays the nodeset returned by the expression.</p>
  +  <p>What it does: Use the XPathEvaluator interface to evaluate an XPath expression from the specified context node of 
  +  an XML file and display the nodeset returned by the expression.</p>
     <note>You can use this sample as an aid when you want to find out what a given XPath expression returns from a
     given context node in an XML file.</note>
     <p>Run this sample from the SimpleXPathAPI subdirectory with</p>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-cvs-help@xml.apache.org