dbertoni    2003/04/18 16:16:05

  Modified:    c/xdocs/sources/xalan faq.xml getstarted.xml readme.xml
                        resources.xml
  Log:
  Updates for 1.5.
  
  Revision  Changes    Path
  1.40      +12 -11    xml-xalan/c/xdocs/sources/xalan/faq.xml
  
  Index: faq.xml
  ===================================================================
  RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/faq.xml,v
  retrieving revision 1.39
  retrieving revision 1.40
  diff -u -r1.39 -r1.40
  --- faq.xml   18 Apr 2003 06:41:42 -0000      1.39
  +++ faq.xml   18 Apr 2003 23:16:05 -0000      1.40
  @@ -105,11 +105,11 @@
         </tr>
          <tr>
            <td>HP/UX 11.0</td>
  -         <td>aCC A.03.33</td>
  +         <td>aCC A.03.37</td>
         </tr>
          <tr>
  -         <td>Red Hat Linux 7.2</td>
  -         <td>Intel C++ Compiler, version 6</td>
  +         <td>RedHat Linux 7.2</td>
  +         <td>Intel C++ Compiler, version 6.0.1</td>
         </tr>
       </table>
    <p>For more details see: <link idref="readme" anchor="unix">Steps for doing 
a UNIX build</link>.</p>
  @@ -126,7 +126,7 @@
   
   <a><p>The International Components for Unicode(ICU) is a C and C++ library 
that provides robust and full-featured Unicode support on a wide variety of 
platforms. &xslt4c; uses the ICU to extend support for encoding, number 
formatting, and sorting.</p> 
   <p>The ICU is available for download from <jump 
href="http://oss.software.ibm.com/icu/index.html";>http://oss.software.ibm.com/icu/index.html</jump>.</p>
  -<p>This release of Xalan was tested with ICU 2.2.</p>
  +<p>This release of Xalan was tested with ICU 2.4.</p>
   <p>For more details see: <link idref="usagepatterns" anchor="icu">Using the 
International Components for Unicode (ICU)</link>.</p><!--icuNote--><anchor 
name="gnutar"/><p/></a>
   </faq>
   
  @@ -236,17 +236,18 @@
   <faq title="Transformation Output Methods">
        <q>How do I output a transformation to [a DOM, a file, an in-memory 
string, as input to another transformation]?</q>
        <a>
  +             <p>The output parameter of XalanTransformer::transform() is an 
XSLTResultTarget which has many constructors.</p>
                <p>Output to a file:</p>
                <ul>
  -                     <li> See this <jump 
href="http://marc.theaimsgroup.com/?l=xalan-c-users&amp;m=104791991207944&amp;w=2";>mailing
 list post</jump>. The short answer: use LocalFileFormatTarget or a DOMWriter 
(gotten from DOMImplementation). Note that these are actually &xml4c; classes, 
so you will find more extensive API documentation at the <jump 
href="http://xml.apache.org/xerces-c/index.html";>&xml4c; website</jump>.</li>
  +                     <li>The easiest way is to use a null-terminated string 
containing the file name to create an XSLTResultTarget.  Or, use an instance of 
std::ofstream or std::ostringstream to create an XSLTResultTarget.</li>
                </ul>
  -             <p>Output to an in-memory string:</p>
  +             <p>Output to an in-memory buffer:</p>
                <ul>
  -                     <li>Same as to a file, only you use 
MemBufFormatTarget.</li>
  +                     <li>Use an instance of std::ostrstream or 
std::ostringstream to create an XSLTResultTarget.  See the StreamTransform 
sample for more information.</li>
                </ul>
                <p>Input to another tranformation:</p>
                <ul>
  -                     <li>The output parameter of XalanTransformer::transform 
is an XSLTResultTarget which can be constructed with: a string, a file name, an 
output stream, or a FormatterListener. Any of these could be used as the input 
to another transformation, but the FormatterToSourceTree is probably the best 
for efficiency reasons.</li>
  +                     <li>Any of the previous output targets could be used as 
the input to another transformation, but the FormatterToSourceTree is probably 
the best for efficiency reasons.  See the source code for the TestXSLT command 
line program for more information.</li>
                </ul>
        </a>
   </faq>
  @@ -271,7 +272,7 @@
   <faq title="Changing Where Error Output is Sent">
        <q>XalanTransformer outputs errors to the console. How do I, for 
example, output error to a file?</q>
        <a>
  -             <p>By default, XalanTransformer creates a 
XalanTransformerProblemListener (subclass of ProblemListener) that outputs 
erros to std::cerr. To change this you can:</p>
  +             <p>By default, XalanTransformer creates a 
XalanTransformerProblemListener (a subclass of ProblemListener) that writes 
output to std::cerr. To change this you can:</p>
                <ul>
                        <li>Redirect cerr somewhere else</li>
                        <li>Call XalanTranformer::setWarningStream with a 
different std::ostream before calling XalanTransformer::transform.</li>
  @@ -305,7 +306,7 @@
   </faq>
   
   <faq title="Extension Functions">
  -     <q>The xalan extension functions (xalan:execute, etc.) don't work for 
me. Help!</q>
  +     <q>The Xalan extension functions (xalan:node-set, etc.) don't work for 
me. Help!</q>
        <a>
                <p>Did you declare the namespace on the xsl:stylesheet or 
xsl:transform element? It should look like this: </p>
                <p>&lt;xsl:stylesheet version="1.0" 
xmlns:xalan="http://xml.apache.org/xalan"&gt; ...rest of stylesheet</p>
  @@ -322,7 +323,7 @@
   </faq>
   
   <faq title="format-number and ICU">
  -     <q>Why does Xalan emit an error message when using the XPath function 
format-number with more than one parameter?</q>
  +     <q>Why does Xalan emit a warning when using the XSLT function 
format-number()?</q>
        <a>
                <p>Did you build with ICU support? See <link 
idref="usagepatterns" anchor="icu">Using the International Components for 
Unicode (ICU)</link>.</p>
        </a>
  
  
  
  1.39      +1 -2      xml-xalan/c/xdocs/sources/xalan/getstarted.xml
  
  Index: getstarted.xml
  ===================================================================
  RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/getstarted.xml,v
  retrieving revision 1.38
  retrieving revision 1.39
  diff -u -r1.38 -r1.39
  --- getstarted.xml    18 Apr 2003 06:41:42 -0000      1.38
  +++ getstarted.xml    18 Apr 2003 23:16:05 -0000      1.39
  @@ -62,10 +62,9 @@
                <td>HP-UX 11.0 (64 bit)</td>
       </tr>    
     </table>
  -  <p>The Windows32 distribution was built with MSVC 6.0 SP3 and <jump 
href="http://www.dinkumware.com/vc_fixes.html";>Dinkumware C++ library 
fixes</jump>. The Red Hat Linux 7.2 32-bit distribution was built with Intel 
C++ Compiler version 6.0.1. The AIX 5.1 32-bit distribution was built with IBM 
C and C++ for AIX 5.02. The Solaris 2.6 32-bit and 64-bit distributions were 
built with Sun Workshop 6 update 2. 
  +  <p>The Windows32 distribution was built with MSVC 6.0 SP3 and <jump 
href="http://www.dinkumware.com/vc_fixes.html";>Dinkumware C++ library 
fixes</jump>. The Red Hat Linux 7.2 32-bit distribution was built with Intel 
C++ Compiler version 6.0.1. The AIX 5.1 32-bit distribution was built with IBM 
C and C++ for AIX 5.02. The Solaris 2.8 32-bit and 64-bit distributions were 
built with Sun Workshop 6 update 2. 
   The HP-UX 11 32-bit and 64-bit distributions were built with aCC A.03.37.</p>
   <note>Use GNU tar to untar the Solaris distribution file; see <link 
idref="faq" anchor="gnutar">A tar checksum error on Solaris </link>.</note>
  -<p>This release also includes alpha support for building 64-bit Solaris and 
AIX binaries. See <link idref="readme" anchor="64bit">building 64-bit 
binaries</link>.</p>
   <anchor name="xalandists"/>
   
   <p>If you want to take advantage of the support for number formatting, 
sorting, and encoding the ICU provides, you should also download and install 
the <resource-ref idref="icu"/>; see <link idref="usagepatterns" 
anchor="icu">Using the ICU</link>,</p>
  
  
  
  1.43      +1 -0      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.42
  retrieving revision 1.43
  diff -u -r1.42 -r1.43
  --- readme.xml        18 Apr 2003 06:41:43 -0000      1.42
  +++ readme.xml        18 Apr 2003 23:16:05 -0000      1.43
  @@ -81,6 +81,7 @@
        <p>Major updates since version 1.4 include:</p>
        <ul>
                <li><resource-ref idref="bugsfixedforthisrelease"/>.</li>
  +             <li>For Windows, Xalan-C++ is now packaged as a single DLL.  
The project files to build separate DLLs are now deprecated and will not be 
maintained.</li>
                <li>Support for &xml4c; DOMNode classes.</li>
                <li>New sample <em>TransformToXercesDOM</em> that illustrates 
how
                  to perform a transform resulting in a &xml4c; DOMDocument</li>
  
  
  
  1.23      +1 -1      xml-xalan/c/xdocs/sources/xalan/resources.xml
  
  Index: resources.xml
  ===================================================================
  RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/resources.xml,v
  retrieving revision 1.22
  retrieving revision 1.23
  diff -u -r1.22 -r1.23
  --- resources.xml     18 Dec 2002 21:30:11 -0000      1.22
  +++ resources.xml     18 Apr 2003 23:16:05 -0000      1.23
  @@ -58,6 +58,6 @@
   
     <resource id="bugsfixedforthisrelease"
               title="XalanC bugs fixed for this release"
  -            
location="http://nagoya.apache.org/bugzilla/buglist.cgi?resolution=FIXED&amp;bugidtype=include&amp;bug_id=&amp;changedin=&amp;chfield=resolution&amp;chfieldfrom=01%2F10%2F2002&amp;chfieldto=09%2F20%2F2002&amp;chfieldvalue=FIXED&amp;product=XalanC&amp;short_desc=&amp;short_desc_type=allwordssubstr"/>
  +            
location="http://nagoya.apache.org/bugzilla/buglist.cgi?resolution=FIXED&amp;bugidtype=include&amp;bug_id=&amp;changedin=&amp;chfield=resolution&amp;chfieldfrom=09%2F20%2F2002&amp;chfieldto=04%2F15%2F2003&amp;chfieldvalue=FIXED&amp;product=XalanC&amp;short_desc=&amp;short_desc_type=allwordssubstr"/>
   
   </resources>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to