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...@locus.apache.org on 2000/06/28 22:10:48 UTC
cvs commit: xml-xalan/c/xdocs/sources/xalan xerces-icu.gif STATUS getstarted.xml index.xml readme.xml resources.xml
dleslie 00/06/28 13:10:47
Modified: c/xdocs/html/apiDocs footer.html
c/xdocs/sources/xalan STATUS getstarted.xml index.xml
readme.xml resources.xml
Added: c/xdocs/sources/xalan xerces-icu.gif
Log:
Updates for next (0.40.0 I think)
Revision Changes Path
1.2 +1 -1 xml-xalan/c/xdocs/html/apiDocs/footer.html
Index: footer.html
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/html/apiDocs/footer.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- footer.html 2000/05/11 19:30:38 1.1
+++ footer.html 2000/06/28 20:10:37 1.2
@@ -1,4 +1,4 @@
-<p align="center"><a class="qindex" href="diagramnotes.html">Interpreting class diagrams</a></p>
+<p align="center"><a href="diagramnotes.html">Interpreting class diagrams</a></p>
<p><FONT color="#000000" face="arial,helvetica,sanserif" size="-1">
<i><A href="http://www.stack.nl/~dimitri/doxygen/">Doxygen</A> and
<A href="http://www.research.att.com/sw/tools/graphviz/">GraphViz</A> are used to generate this API documentation from the Xalan-C header files.</I></FONT></p>
1.6 +2 -23 xml-xalan/c/xdocs/sources/xalan/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/STATUS,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- STATUS 2000/06/27 16:46:16 1.5
+++ STATUS 2000/06/28 20:10:39 1.6
@@ -1,37 +1,16 @@
-<<<<<<< STATUS
-<s3 title="Version of Xerces-C++ to use">
-<p>&xslt4c-current; has been tested with &xml4c-used;. The &xslt4c-current; Windows32 download includes xerces-c_1_1.dll. The &xslt4c-current; Linux download includes libxerces-c_1_1.so.
-
-For information about including The Xerces-C++ dynamic link or shared object library on the path, see <link idref="getstarted" anchor="path">Setting up the system path</link>.</p>
+<s3 title="Version of &xml4c; to use">
+<p>&xslt4c-current; has been tested with &xml4c-used;. The &xslt4c-current; Windows32 download includes xerces-c_1_2.dll. The &xslt4c-current; Linux download includes libxerces-c_1_2.so. For information about including The Xerces-C++ dynamic link or shared object library on the path, see <link idref="getstarted" anchor="path">Setting up the system path</link>.</p>
<p><em>Important</em> You may experience unpredictable anomalies if your Xalan and Xerces builds are not in synch. If you download an update to Xalan, check the release notes to determine which version of Xerces you should use.</p>
-
</s3><anchor name="to-do"/>
<s3 title="To-do tasks for future &xslt4c; releases">
<p>To complete our implementation of the <resource-ref idref="XSLT"/>, we must add support for</p>
-=======
-<s3 title="Version of Xerces to use">
-<p>The &xslt4c-current; has been tested with &xml4c-used;. The &xslt4c-current; Windows32 download includes xerces-c_1_1.dll. The &xslt4c-current; Linux download includes libxerces-c_1_1.so.
-
-For information about including The Xerces-C dynamic link or shared object library on the path, see <link idref="getstarted" anchor="path">Setting up the system path</link>.</p>
-<p><em>Important</em> You may experience unpredictable anomalies if your Xalan and Xerces builds are not in synch. If you download an update to Xalan, check the release notes to determine which version of Xerces you should use.</p>
-
-</s3><anchor name="to-do"/>
-<s3 title="To-do tasks for future &xslt4c; releases">
- <p>To complete our implementation of the <resource-ref idref="XSLT"/>, we must add support for</p>
->>>>>>> 1.4
<ul>
<li>The fallback element<br/><br/></li>
<li>The exclude-result-prefixes attribute<br/><br/></li>
<li>The output encoding attribute<br/><br/></li>
<li>Extension elements<br/><br/></li>
</ul>
-<<<<<<< STATUS
<p>The XSLT specification makes no such requirement, but we plan to implement a more efficient mechanism for storing and
navigating DOM trees, along the lines of the &xslt4j; Document Table Model (DTM)</p>
<p>Watch the <human-resource-ref idref="xalandev"/> for more information and for ideas about how you can get involved.</p>
-=======
- <p>The XSLT specification makes no such requirement, but we plan to implement a more efficient mechanism for storing and
- navigating DOM trees, along the lines of the Xalan-J Document Table Model (DTM)</p>
- <p>Watch the <human-resource-ref idref="xalandev"/> for more information and for ideas about how you can get involved.</p>
->>>>>>> 1.4
</s3>
1.7 +11 -12 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.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- getstarted.xml 2000/06/27 16:46:17 1.6
+++ getstarted.xml 2000/06/28 20:10:39 1.7
@@ -23,27 +23,26 @@
<p><em>Windows32</em></p>
<ul>
<li>The executable: TestXSLT.exe</li>
-<li>The Xalan-C++ dynamic link libraries: DOMSupport.dll, PlatformSupport.dll, XalanDOM.dll, XercesParserLiaison.dll,
- XercesPlatformSupport.dll, XMLSupport.dll, XPath.dll, XSLT.dll</li>
-<li>The Xerces-C++ dynamic link library: xerces-C_1_1.dll</li>
-<li>The International Components for Unicode (ICU) dynamic link libraries: icui18n.dll, icuuc.dll</li>
-<li>The ICU locale data files</li>
+<li>The Xalan-C++ dynamic link libraries: &xslt4c-windlls;</li>
+<li>The Xerces-C++ dynamic link library: &xml4c-windll;</li>
+<li>(<em>NOT FOR THIS RELEASE</em>) The International Components for Unicode (ICU) dynamic link libraries: &icu-windlls;</li>
+<li>(<em>NOT FOR THIS RELEASE</em>) The ICU locale data files</li>
</ul>
<p><em>Linux</em></p>
<ul>
<li>The utility: TestXSLT</li>
- <li>The Xalan-C++ shared library: libxalan-c_0_40_0.so</li>
- <li>The Xerces-C++ shared library: libxerces-c1_2.so</li>
- <li>The International Components for Unicode (ICU) shared library: libicu-1_4_1_2.so</li>
- <li>The ICU locale data files</li>
+ <li>The Xalan-C++ shared library: &xslt4c-linuxlib;</li>
+ <li>The Xerces-C++ shared library: &xml4c-linuxlib;</li>
+ <li>(<em>NOT FOR THIS RELEASE</em>) The International Components for Unicode (ICU) shared library: &icu-unixlib;</li>
+ <li>(<em>NOT FOR THIS RELEASE</em>) The ICU locale data files</li>
</ul>
-<p><em>Important</em> ICU requires you to set the ICU_DATA environment variable to point to the directory containing the ICU locale data files. In the Windows32 distribution, this is xml-xalan\c\Build\Win32\VC6\Release\Data. In the Linux distribution, it is xml-xalan/c/lib/data.</p>
+<p>(<em>NOT FOR THIS RELEASE</em>) <em>Important</em> ICU requires you to set the ICU_DATA environment variable to point to the directory containing the ICU locale data files. In the Windows32 distribution, this is xml-xalan\c\Build\Win32\VC6\Release\Data. In the Linux distribution, it is xml-xalan/c/lib/data.</p>
<p>For information about using the command-line utility, see <link idref="commandline">Command-Line Utility</link>.</p>
</s3>
<s3 title="What you need to build applications">
<p>To build your own applications with Xalan and Xerces, you also need need the
-Xalan-C++ and Xerces-C++ header (.hpp) files and (for Windows) the Xerces-C++ libraries (.lib files).</p>
+Xalan-C++ and Xerces-C++ header (.hpp) files and (for Windows) the &xslt4c; and &xml4c; libraries (.lib files).</p>
<p>The Xalan-C++ header files are in the src directory tree 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 - Release subdirectory.</p>
<p>In the Linux distribution (built with a make file and Red Hat Linux 6.1), the shared object library is in the lib subdirectory.</p>
@@ -61,7 +60,7 @@
and you can review the source files -- all of which are brief -- to see just how they work. In the Windows32 distribution, we have precompiled these samples for you so they are ready to run. In the Linux distribution, you need to build them first.</p>
<p>To run the samples, do the following:</p>
<ol>
-<li>(Linux only) Compile the sample sources and build an executable for each sample application.</li>
+<li>(Linux only) Compile the sample sources (you may need to make some minor changes in the header files to accommodate Linux) and build an executable for each sample application.</li>
<li>Set up your path (see above). In the Windows32 distribution, the sample executables are in
xml-xalan\c\Build\Win32\VC6\Release. For Linux, we suggest you build the executables in xml-xalan/c/bin.</li>
<li>Go to the samples subdirectory containing the sample (use the DOS shell in Windows).</li>
1.6 +5 -5 xml-xalan/c/xdocs/sources/xalan/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/index.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- index.xml 2000/06/27 16:46:17 1.5
+++ index.xml 2000/06/28 20:10:41 1.6
@@ -61,15 +61,15 @@
<s1 title="&xslt4c-current;">
<s2 title="What is it?">
- <p>Xalan is an XSL processor for transforming XML documents into HTML, text, or other XML document types. &xslt4c-current;
- represents an almost complete and a robust C++ reference implementation of the W3C Recommendations for XSL
- Transformations (XSLT) and the XML Path Language (XPath).</p>
- <p>Xalan-C uses the Xerces-C XML parser.</p>
+ <p>Xalan is an XSLT processor for transforming XML documents into HTML, text, or other XML document types.</p>
+ <p>&xslt4c-current; represents a robust and an almost complete C++ reference implementation of the W3C Recommendations
+ for XSL Transformations (XSLT) and the XML Path Language (XPath). It uses the latest release of the &xml4c; XML parser
+ (&xml4c-used;).</p>
</s2>
<s2 title="How do I get it?">
<p>Download and unzip the distribution file for your platform. In addition to the platform-specific binaries,
- documentation, and sample applications, both distributions also include the complete Xalan-C source tree.</p>
+ documentation, and sample applications, both distributions also include the complete &xslt4c; source tree.</p>
<table>
<tr>
<td><em>Platform</em></td>
1.7 +9 -10 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.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- readme.xml 2000/06/27 16:46:17 1.6
+++ readme.xml 2000/06/28 20:10:42 1.7
@@ -1,8 +1,8 @@
<?xml version="1.0" standalone="no"?>
<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd"[
-<!ENTITY done-C++ SYSTEM "DONE">
-<!ENTITY status-C++ SYSTEM "STATUS">
-<!ENTITY bugs-C++ SYSTEM "BUGS">]>
+<!ENTITY done-c SYSTEM "DONE">
+<!ENTITY status-c SYSTEM "STATUS">
+<!ENTITY bugs-c SYSTEM "BUGS">]>
<!--
* The Apache Software License, Version 1.1
@@ -90,23 +90,22 @@
<ul>
<li>The &xslt4c; source files</li>
<li>The &xml4c; header and (for Windows) .lib files</li>
- <li>The ICU header and (for Windows) .lib files</li>
+ <li>(<em>NOT FOR THIS RELEASE</em>) The ICU header and (for Windows) .lib files</li>
</ul>
<p>The &xslt4c; source files are in the distribution.</p>
- <p>The required &xml4c; files are in the &xml4c; binary distributions, with the exception of a header file that is only in the
- &xml4c; source distributions. Accordingly, you need the binary and the source distributions.</p>
- <p>To get the ICU, download and unzip the <resource-ref idref="icu-download"/> from the IBM developerWorks open source zone,
+ <p>The required &xml4c; files are in the &xml4c; binary distributions.</p>
+ <p>(<em>NOT FOR THIS RELEASE</em>) To get the ICU, download and unzip the <resource-ref idref="icu-download"/> from the IBM developerWorks open source zone,
and do a build -- see the Windows NT or Unix build instructions in the readme.html that accompanies the download.</p>
<note> If you are not rebuilding ICUBridge, you do not need the ICU header or .lib files.</note>
<p>To rebuild the Windows32 release, use the Microsoft Visual C++ 6.0 project files. To rebuild the Linux release, use the make
file in the root of the source directory. Both builds look for &xml4c; and ICU in directories parallel to the xml-xalan
directory</p>
<p><em>Important</em> We have set up the Visual C++ projects and the Linux make file to look for Xerces in a directory structure that results from downloading xml-xerces/c from the <jump href="http://xml.apache.org/websrc/cvsweb.cgi/">Apache XML CVS repository</jump> and building with the Visual C++ project files or the Linux make file. This structure parallels the &xslt4c; source tree and build structure.<br/><br/>
-If you are using a &xml4c; binary distribution, you must either modify the &xslt4c; project files or makefile, or rearrange the build directory structure, and you must also get the header files from the &xml4c; source distribution, since &xslt4c; uses a header file that is not included in the &xml4c; binary distribution.</p>
+If you are using a &xml4c; binary distribution, you must either modify the &xslt4c; project files or makefile, or rearrange the build directory structure as indicated in the following illustration.</p>
<s4 title="&xml4c; and ICU layout for &xslt4c; build">
<p><img src="xerces-icu.gif" alt="xerces-icu.gif"/></p>
</s4>
-<note>Keep in mind that at any given point in time the &xslt4c; and &xml4c; source trees in the Apache XML repository may not be consistent. When we release a version of &xml4c; we certify that it is compabible with a given release of &xslt4c;. To be safe, stick with distributions that we certify to be compatible. Reminder: &xslt4c-current; is compatible with &xml4c-used;.<br/><br/>
+<note>Keep in mind that at any given point in time the &xslt4c; and &xml4c; source trees in the Apache XML repository may not be consistent. When we release a version of &xml4c; we certify that it is compabible with a given release of &xslt4c;. To be safe, stick with distributions that we certify to be compatible. (<em>NOT FOR THIS RELEASE</em>) Reminder: &xslt4c-current; is compatible with &xml4c-used;.<br/><br/>
&xslt4c-current; was built with the &icu-used;. You can probably use newer ICU releases as they appear.</note>
</s3><anchor name="samples"/>
<s3 title="Rebuilding a sample application">
@@ -115,7 +114,7 @@
</s3>
</s2><anchor name="contact"/>
<s2 title="Getting in Touch">
- <p>Your feedback is more than welcome. Offers of help are even more so! Perhaps you would like to contribute to the ongoing development, testing, or documentation of &xslt4c;?</p>
+ <p>Your feedback is more than welcome. Offers of help are even more so! Perhaps you would like to contribute to the ongoing development, testing, or documentation of &xslt4c;.</p>
<p>Please email your comments, questions, suggestions, bug reports, and offers to help to <human-resource-ref idref="xalandev"/>.</p>
</s2>
</s1>
1.4 +3 -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.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- resources.xml 2000/06/27 16:46:18 1.3
+++ resources.xml 2000/06/28 20:10:42 1.4
@@ -1,5 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE resources [
+ <!ENTITY % externalEntity SYSTEM "sbk:/sources/entities.ent">
+ %externalEntity;
<!ENTITY apiResources SYSTEM "apiResources.xml">
<!ELEMENT resources (resource|human-resource)+>
<!ELEMENT resource EMPTY>
@@ -13,7 +15,7 @@
]>
<resources>
- <resource id="xslt4c-current" title="&xslt4c-current" location="http://xml.apache.org/xalan"/>
+ <resource id="xslt4c-current" title="&xslt4c-current;" location="http://xml.apache.org/xalan"/>
<resource id="xml4c-used" title="&xml4c-used;" location="http://xml.apache.org/xerces-c/index.html"/>
<resource id="xslt4c-distdir" title="&xslt4c; distribution directory" location="http://xml.apache.org/dist/xalan-c"/>
1.1 xml-xalan/c/xdocs/sources/xalan/xerces-icu.gif
<<Binary file>>