dleslie 01/12/21 10:13:32
Modified: c/xdocs/sources entities.ent
c/xdocs/sources/xalan extensions.xml faq.xml getstarted.xml
overview.xml readme.xml resources.xml
usagepatterns.xml xalan-c-unixdist.gif
xalan-c-windist.gif
Log:
Updates per review by Dave Bertoni.
Revision Changes Path
1.22 +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.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- entities.ent 2001/12/20 13:57:15 1.21
+++ entities.ent 2001/12/21 18:13:31 1.22
@@ -20,7 +20,7 @@
<!ENTITY xml4c-solarislib "[This release does not include a Solaris build]">
<!ENTITY solarisbuild " [We do not have the resources to include a Solaris
build with this release.]">
<!ENTITY xslt4j "Xalan-Java">
-<!ENTITY icu-used "International Components for Unicode(ICU) 1.8.1 source
files">
+<!ENTITY icu-used "International Components for Unicode(ICU) 2.0 source
files">
<!ENTITY icu-windlls "icui18n.dll, icuuc.dll">
<!ENTITY icubridge-win "ICUBridge.dll">
<!ENTITY done SYSTEM "xalan/DONE">
1.16 +6 -6 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.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- extensions.xml 2001/08/15 17:32:40 1.15
+++ extensions.xml 2001/12/21 18:13:31 1.16
@@ -115,9 +115,9 @@
virtual XObjectPtr
execute(
XPathExecutionContext& executionContext,
- XalanNode* context,
- int /* opPos */,
- const XObjectArgVectorType& args)
+ XalanNode* /* context */,
+ const XObjectPtr arg,
+ const Locator* /* locator */) const
{
if (args.size() != 1)
{
@@ -161,11 +161,11 @@
<p><jump href="apidocs/class_xalantransformer.html">XalanTransformer</jump>
provides methods for installing and unistalling external functions:</p>
<ul>
<li>installExternalFunction() makes the function available in the current
instance of XalanTransformer. Use uninstallExternalFunction() to remove the
function.<br/><br/></li>
-<li>installExternalFunctionGlobal() makes the function available globally.
Use uninstallExternalFunctionGlobal() to remove the function. The global
functions are static; they are not thread-safe!</li>
+<li>installExternalFunctionGlobal() makes the function available globally.
Use uninstallExternalFunctionGlobal() to remove the function. The global
functions are static. The global install and unistall operations are not
thread-safe; the global functions are thread-safe..</li>
</ul>
<p>These methods include arguments for the namespace, the function name, and
the function implementation.</p>
<p>When you install an extension function, the function inhabits the
namespace you designate. For information about XML namespaces, see <jump
href="http://www.w3.org/TR/REC-xml-names/";>Namespaces in XML</jump>.</p>
-<p>The following code fragment installs locally the square root function
defined above, and binds it to the extension-function name "square-root" in the
namespace "http://ExternalFunction.xalan-c.xml.apache.org"; so it can be
accessed from stylesheets. Keep in mind that the function name does not need to
be the same as the name of the function class, and that a function name may be
used more than once provided that each function with that name is installed in
a different namespace.</p>
+<p>The following code fragment installs locally the square root function
defined above, and binds it to the extension-function name "square-root" in the
namespace "http://MyExternalFunction.mycompany.org"; so it can be accessed from
stylesheets. Keep in mind that the function name does not need to be the same
as the name of the function class, and that a function name may be used more
than once provided that each function with that name is installed in a
different namespace.</p>
<source>#include <Include/PlatformDefinitions.hpp>
#include <util/PlatformUtils.hpp>
#include <XalanTransformer/XalanTransformer.hpp>
@@ -173,7 +173,7 @@
#include <MyFunctions/FunctionSquareRoot.hpp>
// The namespace...
const XalanDOMString
- theNamespace("http://ExternalFunction.xalan-c++.xml.apache.org";);
+ theNamespace("http://MyExternalFunction.mycompany.org";);
theXalanTransformer.installExternalFunction(theNamespace,
XalanDOMString("square-root"),
1.27 +2 -2 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.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- faq.xml 2001/12/20 22:12:29 1.26
+++ faq.xml 2001/12/21 18:13:31 1.27
@@ -63,7 +63,7 @@
<tr>
<td>AIX 4.3</td>
<td>IBM C and C++ for AIX 5.02</td>
- <td>Yes</td>
+ <td>No</td>
</tr>
<tr>
<td>Solaris 2.6 &solarisbuild;</td>
@@ -87,7 +87,7 @@
<faq title="STLPort">
<q>What is STLPort and why do I need it?</q>
-<a><p>The Standard Template Library, or STL, is a C++ library of container
classes, algorithms, and iterators; it provides many of the basic computer
science algorithms and data structures. &xslt4c; implementation uses the SLT.
STLport ports SGI STL to any platform possible and provides all necessary
wrap-ups installed. If your compiler does not support the STL or its
implementation is out of date, you will need to install the STLPort.</p>
+<a><p>The Standard Template Library, or STL, is a C++ library of container
classes, algorithms, and iterators; it provides many of the basic computer
science algorithms and data structures. &xslt4c; implementation uses the STL.
STLport ports SGI STL to any platform possible and provides all necessary
wrap-ups installed. If your compiler does not support the STL or its
implementation is out of date, you will need to install the STLPort.</p>
<p>The STLPort version 4.0 for download from the site: <jump
href="http://www.stlport.org/";>http://www.stlport.org/</jump>.</p>
1.30 +2 -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.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- getstarted.xml 2001/12/20 22:12:29 1.29
+++ getstarted.xml 2001/12/21 18:13:31 1.30
@@ -11,7 +11,7 @@
</ul>
<anchor name="download"/>
<s2 title="Downloading what you need">
-<p>For &xslt4c-current;, we are distributing a Windows32 Visual C++ build
and four UNIX builds with a makefile: a Red Hat Linux GNU build, an AIX xlC_r
build, an HP-UX 11 aCC build, and a Solaris &solarisbuild; build.
+<p>For &xslt4c-current;, we are distributing a Windows32 Visual C++ build
and three UNIX builds with a makefile: a Red Hat Linux GNU build, an AIX xlC
build, and an HP-UX 11 aCC build [&solarisbuild;].
Please contact us at <human-resource-ref idref="xalandev"/> if you would
like to help provide builds for other platforms.</p>
<anchor name="xalandists"/>
<s3 title="&xslt4c; Windows Distribution">
@@ -72,7 +72,7 @@
<p>The Xalan-C++ and Xerces-C++ header files are in the src directory trees
in both distributions.</p>
<p>In the Windows32 distribution (built with Microsoft® Visual C++®
6.0), the .dlls and libraries are in the Build\Win32\V6 Debug and Release
subdirectories.</p>
<p>In the Linux distribution (built with a make file and the GNU C++
compiler on Red Hat Linux 6.1), the shared object libraries are in the lib
subdirectories.</p>
-<p>In the AIX distribution (built with the make file and xlC_r), the load
libraries are in the lib subdirectories.</p>
+<p>In the AIX distribution (built with the make file and xlC), the load
libraries are in the lib subdirectories.</p>
<p>In the HP-UX 11 distribution (built with the make file and aCC), the
shared libraries are in the lib subdirectories.</p>
<p>In the Solaris distribution &solarisbuild; (built with the make file and
CC), the shared libraries are in the lib subdirectories.</p>
<note>For your convenience, both the Xalan and Xerces libraries are placed
together in the pertinent xml-xalan directory, whereas the corresponding
xml-xerces directory only contains Xerces libraries.</note>
1.16 +1 -1 xml-xalan/c/xdocs/sources/xalan/overview.xml
Index: overview.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/overview.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- overview.xml 2001/08/14 17:41:48 1.15
+++ overview.xml 2001/12/21 18:13:31 1.16
@@ -125,7 +125,7 @@
<li>Crane Softwright's <jump
href="http://www.CraneSoftwrights.com/training/";>Free preview of Practical
Transformation Using XSLT and XPath</jump><br/><br/></li>
<li>Doug Tidwell's <jump
href="http://www.oreilly.com/catalog/xslt/";>XSLT</jump>, O'Reilly,
2001<br/><br/></li>
- <li>Bob Ducharme's <jump
href="http://www.manning.com/ducharme/index.html";>XSLT Quickly</jump>, Manning
Publications,
+ <li>Bob DuCharme's <jump
href="http://www.manning.com/ducharme/index.html";>XSLT Quickly</jump>, Manning
Publications,
2001<br/><br/></li>
<li>John Robert Gardner and Zarella Rendon's
<jump
href="http://vig.prenhall.com/catalog/academic/product/1,4096,0130404462,00.html";>XSLT
and XPath: A Guide to
1.33 +4 -4 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.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- readme.xml 2001/12/20 22:12:29 1.32
+++ readme.xml 2001/12/21 18:13:31 1.33
@@ -158,10 +158,10 @@
<li>Set the XERCESCROOT environment variable to the root of
xml-xerces.<br/><br/></li>
<li>Set the XALANCROOT environment variable to the complete path to
the root of the &xslt4c;
distribution.<br/><br/></li>
- <li>AIX and Solaris only &solarisbuild; : Download <resource-ref
idref="stlport"/> and set the STLPORTROOT environment
+ <li>Solaris only &solarisbuild; : Download <resource-ref
idref="stlport"/> and set the STLPORTROOT environment
variable to the complete path to the STLPort distribution. <br/>
- (This step is not required for Linux or HP-UX 11 because The Linux
GNU compiler and HP aCC compiler include the STL (Standard Template
- Library.)<br/><br/></li>
+ (This step is not required for Linux, AIX, or HP-UX 11 because The
Linux GNU compiler, AIX xlC compiler, and
+ HP aCC compiler include the STL (Standard Template
Library.)<br/><br/></li>
<li>(Optional) If you are including the ICUBridge, install the ICU
(see <link idref="usagepatterns"
anchor="icu">Using the ICU</link>) and use the shell to define
XALAN_USE_ICU.<br/><br/>
If you are using Bourne Shell, K Shell, or Bash:
@@ -185,7 +185,7 @@
<code>make</code><br/>
or<br/>
<code>make
<ref>targ</ref></code><br/><br/>
- where <ref>targ</ref> is ommitted or is <code>all</code> (rebuild
all), <code>lib</code> (the XSLT libary), <code>Xalan</code> (the Xalan
executable), or
+ where <ref>targ</ref> is omitted or is <code>all</code> (rebuild all),
<code>lib</code> (the XSLT library), <code>Xalan</code> (the Xalan executable),
or
<code>testXSLT</code> (the testXSLT executable). ICUBridge is included
in the build of Xalan and TestXSLT if XALAN_USE_ICU is
defined.<br/><br/></li>
</ol>
1.16 +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.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- resources.xml 2001/12/20 13:57:15 1.15
+++ resources.xml 2001/12/21 18:13:31 1.16
@@ -27,7 +27,7 @@
<resource id="xslt4c-Solaris-download" title="&solarisbuild;"
location="NONE"/>
<resource id="icu" title="International Components for Unicode (ICU)"
location="http://oss.software.ibm.com/developerworks/opensource/icu/project/index.html"/>
-<resource id="icu-download" title="International Components for Unicode
(ICU) 1.8.1 source files"
location="http://oss.software.ibm.com/developerworks/opensource/icu/project/download/index.html"/>
+<resource id="icu-download" title="International Components for Unicode
(ICU) 2.0 source files"
location="http://oss.software.ibm.com/developerworks/opensource/icu/project/download/index.html"/>
<resource id="xerces-build-icu" title="Building ICU for &xml4c;"
location="http://xml.apache.org/xerces-c/build.html#BuildICU"/>
<resource id="stlport" title="STLport" location="http://www.stlport.org/"/>
1.34 +6 -6 xml-xalan/c/xdocs/sources/xalan/usagepatterns.xml
Index: usagepatterns.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/usagepatterns.xml,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -r1.33 -r1.34
--- usagepatterns.xml 2001/12/21 15:59:26 1.33
+++ usagepatterns.xml 2001/12/21 18:13:31 1.34
@@ -147,8 +147,8 @@
<s2 title="Setting stylesheet parameters">
<p>An XSL stylesheet can include parameters that are set at run time before
a transformation takes place. When we generate the HTML documents that make up
the Xalan doc set, for example, we send the stylesheet an id parameter along
with each XML source document. The id identifies that document and enables the
stylesheet to integrate it into the overall doc set.</p>
<p>To set a stylesheet parameter, use the <jump
href="apidocs/class_xalantransformer.html">XalanTransformer</jump>
setStylesheetParam() method. The setStytlesheetParam() method takes two
arguments: the parameter name and the expression. For example:</p>
-<source>const XalanDOMString& key="param1";
-const XalanDOMString& expression="'Hello World'";
+<source>const XalanDOMString key("param1");
+const XalanDOMString expression("'Hello World'");
theXalanTransformer.setStylesheetParam(key, expression);
// foo.xsl defines a stylesheet parameter named param1.
theXalanTransformer.transform("foo.xml","foo.xsl","foo-out.xml")</source>
@@ -156,11 +156,11 @@
<p>You can include the -param flag with two arguments when you call the
<link idref="commandline">command line utility</link>. The first argument is
the parameter name or key, and the second argument is the string expression (in
single quotes). For example:</p>
<p><code>Xalan -p param1 'boo' foo.xml foo.xsl</code></p>
<p>or</p>
-<p><code>TestXSLT -in foo.xml -xsl foo.xsl -param param1 'boo'</code></p>
+<p><code>testXSLT -in foo.xml -xsl foo.xsl -param param1 'boo'</code></p>
<p>If the string expression includes spaces or other characters that the
shell intercepts, first enclose the string in single quotes so &xslt4c;
interprets it as a string expression, and then enclose the resulting string in
double quotes so the shell interprets it as a single argument. For example:</p>
<p><code>Xalan -p "'hello there'" foo.xml foo.xsl</code></p>
<p>or</p>
-<p><code>TestXSLT -in foo.xml -xsl foo.xsl -param param1 "'hello
there'"</code></p>
+<p><code>testXSLT -in foo.xml -xsl foo.xsl -param param1 "'hello
there'"</code></p>
<p>The <link idref="samples"
anchor="usestylesheetparam">UseStylesheetParam</link> sample application also
uses a command-line parameter.</p>
</s2><anchor name="incremental"/>
<s2 title="Processing output incrementally">
@@ -168,7 +168,7 @@
<source>int
transform(const XSLTInputSource& xmlIn,
const XSLTInputSource& xslIn,
- const void* theOutputHandle,
+ void* theOutputHandle,
XalanOutputHandlerType theOutputHandler
XalanFlushHanderType theFlushHandler = 0);</source>
<p>For an example, see <link idref="samples"
anchor="xalantransformercallback">XalanTransformerCallback</link>.</p>
@@ -309,7 +309,7 @@
<li><em>Encoding</em>
<br/> &xml4c; and &xslt4c; use UTF-16 encoding to work with Unicode
data.
If you integrate the ICU with &xml4c;, both &xml4c; and &xslt4c; use
ICU support for
- UTF-16 encoding.<br/><br/></li>
+ input and output transcoding.<br/><br/></li>
<li><em>format-number()</em>
<br/>This XSLT function includes two or three arguments (the third is
optional): number, format pattern, and decimal-format name. &xslt4c;
ignores the format
1.2 +8 -10 xml-xalan/c/xdocs/sources/xalan/xalan-c-unixdist.gif
<<Binary file>>
1.2 +22 -13 xml-xalan/c/xdocs/sources/xalan/xalan-c-windist.gif
<<Binary file>>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
