You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xerces.apache.org by bo...@apache.org on 2008/02/25 16:46:06 UTC
svn commit: r630884 [1/3] - in /xerces/c/branches/xerces-2.8/doc: ./ html/
html/apiDocs-2/ html/apiDocs/ style/dtd/ style/graphics/ style/resources/
style/stylesheets/
Author: borisk
Date: Mon Feb 25 07:46:00 2008
New Revision: 630884
URL: http://svn.apache.org/viewvc?rev=630884&view=rev
Log:
Factor-out project-independent pages into a separate project (web). Change the documentation to allow simultaneous hosting of several releases on the website.
Added:
xerces/c/branches/xerces-2.8/doc/html/apiDocs-2/
- copied from r596087, xerces/c/branches/xerces-2.8/doc/html/apiDocs/
xerces/c/branches/xerces-2.8/doc/style/graphics/section.gif (with props)
xerces/c/branches/xerces-2.8/doc/style/resources/separator-space.gif (with props)
xerces/c/branches/xerces-2.8/doc/style/stylesheets/context2section.xsl
Removed:
xerces/c/branches/xerces-2.8/doc/applications.xml
xerces/c/branches/xerces-2.8/doc/blueb.gif
xerces/c/branches/xerces-2.8/doc/bug-report.xml
xerces/c/branches/xerces-2.8/doc/charter.xml
xerces/c/branches/xerces-2.8/doc/download.xml
xerces/c/branches/xerces-2.8/doc/feedback.xml
xerces/c/branches/xerces-2.8/doc/html/apiDocs/
xerces/c/branches/xerces-2.8/doc/html/download.cgi
xerces/c/branches/xerces-2.8/doc/index.html
xerces/c/branches/xerces-2.8/doc/mailing-lists.xml
xerces/c/branches/xerces-2.8/doc/releases.xml
xerces/c/branches/xerces-2.8/doc/releases_archive.xml
xerces/c/branches/xerces-2.8/doc/releases_plan.xml
xerces/c/branches/xerces-2.8/doc/source-repository.xml
Modified:
xerces/c/branches/xerces-2.8/doc/Doxyfile
xerces/c/branches/xerces-2.8/doc/apidocs.xml
xerces/c/branches/xerces-2.8/doc/build-misc.xml
xerces/c/branches/xerces-2.8/doc/build-other.xml
xerces/c/branches/xerces-2.8/doc/build-winunix.xml
xerces/c/branches/xerces-2.8/doc/build.xml
xerces/c/branches/xerces-2.8/doc/dom3.xml
xerces/c/branches/xerces-2.8/doc/domcount.xml
xerces/c/branches/xerces-2.8/doc/domprint.xml
xerces/c/branches/xerces-2.8/doc/enumval.xml
xerces/c/branches/xerces-2.8/doc/faq-build.xml
xerces/c/branches/xerces-2.8/doc/faq-contributing.xml
xerces/c/branches/xerces-2.8/doc/faq-distrib.xml
xerces/c/branches/xerces-2.8/doc/faq-other.xml
xerces/c/branches/xerces-2.8/doc/faq-parse.xml
xerces/c/branches/xerces-2.8/doc/install.xml
xerces/c/branches/xerces-2.8/doc/migration.xml
xerces/c/branches/xerces-2.8/doc/migration_archive.xml
xerces/c/branches/xerces-2.8/doc/pparse.xml
xerces/c/branches/xerces-2.8/doc/program-deprecateddom.xml
xerces/c/branches/xerces-2.8/doc/program-dom.xml
xerces/c/branches/xerces-2.8/doc/program-others.xml
xerces/c/branches/xerces-2.8/doc/program-sax.xml
xerces/c/branches/xerces-2.8/doc/program-sax2.xml
xerces/c/branches/xerces-2.8/doc/program.xml
xerces/c/branches/xerces-2.8/doc/psviwriter.xml
xerces/c/branches/xerces-2.8/doc/readme.xml
xerces/c/branches/xerces-2.8/doc/redirect.xml
xerces/c/branches/xerces-2.8/doc/samples.xml
xerces/c/branches/xerces-2.8/doc/sax2count.xml
xerces/c/branches/xerces-2.8/doc/sax2print.xml
xerces/c/branches/xerces-2.8/doc/saxcount.xml
xerces/c/branches/xerces-2.8/doc/saxprint.xml
xerces/c/branches/xerces-2.8/doc/schema.xml
xerces/c/branches/xerces-2.8/doc/scmprint.xml
xerces/c/branches/xerces-2.8/doc/senumval.xml
xerces/c/branches/xerces-2.8/doc/stdinparse.xml
xerces/c/branches/xerces-2.8/doc/style/dtd/book.dtd
xerces/c/branches/xerces-2.8/doc/style/dtd/entities.ent
xerces/c/branches/xerces-2.8/doc/style/stylesheets/book2project.xsl
xerces/c/branches/xerces-2.8/doc/style/stylesheets/document2html.xsl
xerces/c/branches/xerces-2.8/doc/xerces-c_book.xml
Modified: xerces/c/branches/xerces-2.8/doc/Doxyfile
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.8/doc/Doxyfile?rev=630884&r1=630883&r2=630884&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.8/doc/Doxyfile (original)
+++ xerces/c/branches/xerces-2.8/doc/Doxyfile Mon Feb 25 07:46:00 2008
@@ -585,7 +585,7 @@
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
# put in front of it. If left blank `html' will be used as the default path.
-HTML_OUTPUT = apiDocs
+HTML_OUTPUT = apiDocs-2
# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
Modified: xerces/c/branches/xerces-2.8/doc/apidocs.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.8/doc/apidocs.xml?rev=630884&r1=630883&r2=630884&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.8/doc/apidocs.xml (original)
+++ xerces/c/branches/xerces-2.8/doc/apidocs.xml Mon Feb 25 07:46:00 2008
@@ -42,13 +42,13 @@
<jump href="http://www.w3.org/TR/2002/WD-DOM-Level-3-ASLS-20020409/">
DOM Level 3.0 Abstract Schemas and Load and Save Specification</jump>
(W3C Working Draft of 09 April 2002). This implementation is experimental.
- See <jump href="dom3.html">DOM Level 3 Support</jump> for details.</li>
+ See <jump href="dom3-&XercesC2Series;.html">DOM Level 3 Support</jump> for details.</li>
</ul>
<p>For a complete understanding of how the &XercesCName; APIs work,
we recommend you to read these documents.</p>
- <p>See the <em><jump href="apiDocs/index.html">&XercesCName; API documentation</jump></em> for more details.</p>
+ <p>See the <em><jump href="apiDocs-&XercesC2Series;/index.html">&XercesCName; API documentation</jump></em> for more details.</p>
<note>The API documentation is automatically generated using
<jump href="http://www.stack.nl/~dimitri/doxygen/">Doxygen</jump> and
Modified: xerces/c/branches/xerces-2.8/doc/build-misc.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.8/doc/build-misc.xml?rev=630884&r1=630883&r2=630884&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.8/doc/build-misc.xml (original)
+++ xerces/c/branches/xerces-2.8/doc/build-misc.xml Mon Feb 25 07:46:00 2008
@@ -52,7 +52,7 @@
<p>Extract &XercesCName; source files from the .zip archive using WinZip, say
in the root directory (an arbitrary drive x:). It should create a directory like
- '<code>x:\&XercesCSrcInstallDir;</code>'.</p>
+ '<code>x:\&XercesC2SrcInstallDir;</code>'.</p>
<p>Extract the ICU files, using WinZip, in root directory of the disk
where you have installed &XercesCName;, sources. After extraction, there
@@ -66,21 +66,21 @@
'<code>VCVARS32.BAT</code>' or a similar file. Then at the prompt
enter:</p>
-<source>set XERCESCROOT=x:\&XercesCSrcInstallDir;
+<source>set XERCESCROOT=x:\&XercesC2SrcInstallDir;
set ICUROOT=x:\icu
-cd x:\&XercesCSrcInstallDir;\scripts
+cd x:\&XercesC2SrcInstallDir;\scripts
</source>
<p>To build with ICU, either specify using ICU transcoding service,</p>
<source>
-perl packageBinaries.pl -s x:\&XercesCSrcInstallDir; -o x:\temp\&XercesCInstallDir;-win32 -t icu
+perl packageBinaries.pl -s x:\&XercesC2SrcInstallDir; -o x:\temp\&XercesC2InstallDir;-win32 -t icu
</source>
<p> or specify using ICU message loader service</p>
<source>
-perl packageBinaries.pl -s x:\&XercesCSrcInstallDir; -o x:\temp\&XercesCInstallDir;-win32 -m icu
+perl packageBinaries.pl -s x:\&XercesC2SrcInstallDir; -o x:\temp\&XercesC2InstallDir;-win32 -m icu
</source>
<p>(Match the source directory to your system; the target directory can be
@@ -101,7 +101,7 @@
</s3>
<s3 title="Building on UNIX">
<p>Extract &XercesCName; source files into, say, the home directory ($HOME).
- It should create a directory like '<code>$HOME/&XercesCSrcInstallDir;</code>'.</p>
+ It should create a directory like '<code>$HOME/&XercesC2SrcInstallDir;</code>'.</p>
<p>Extract the ICU files into the same directory
where you have installed &XercesCName; sources. After extraction, there
@@ -113,7 +113,7 @@
and <code>libicudt*</code> available from your library search path.</p>
<p>Then build the &XercesCName; with ICU. This is similar to building a standalone
- &XercesCName; library as instructed in <jump href="build-winunix.html#UNIX">
+ &XercesCName; library as instructed in <jump href="build-winunix-&XercesC2Series;.html#UNIX">
"Building &XercesCName; on UNIX platforms"</jump>; except that you have to specify
the transcoder option <code>'-t icu'</code> and/or the message loader option
<code>'-m icu'</code>. For example:</p>
@@ -122,21 +122,21 @@
<p>Or instead of building the ICU and &XercesCName; manually in two steps,
you can use the bundled perl script '<code>packageBinaries.pl</code>' which
will build both of them in one step. For example:</p>
-<source>export XERCESCROOT=$HOME/&XercesCSrcInstallDir;
+<source>export XERCESCROOT=$HOME/&XercesC2SrcInstallDir;
export ICUROOT=$HOME/icu
-cd $HOME/&XercesCSrcInstallDir;/scripts
+cd $HOME/&XercesC2SrcInstallDir;/scripts
</source>
<p>To build with ICU, either specify using ICU transcoding service,</p>
<source>
-perl packageBinaries.pl -s $HOME/&XercesCSrcInstallDir; -o $HOME/temp/&XercesCInstallDir;-aix -t icu
+perl packageBinaries.pl -s $HOME/&XercesC2SrcInstallDir; -o $HOME/temp/&XercesC2InstallDir;-aix -t icu
</source>
<p> or specify using ICU message loader service</p>
<source>
-perl packageBinaries.pl -s $HOME/&XercesCSrcInstallDir; -o $HOME/temp/&XercesCInstallDir;-aix -m icu
+perl packageBinaries.pl -s $HOME/&XercesC2SrcInstallDir; -o $HOME/temp/&XercesC2InstallDir;-aix -m icu
</source>
<p>If the parser is built with icu message loader (as mentioned above), or message
@@ -152,12 +152,12 @@
<p>&XercesCName; may be built from the distributed source archive directly on Linux
using RPM. For example: </p>
<source>
-rpm -ta &XercesCSrcInstallDir;.tar.gz (rpm 4.0 and older)
+rpm -ta &XercesC2SrcInstallDir;.tar.gz (rpm 4.0 and older)
or
-rpmbuild -ta &XercesCSrcInstallDir;.tar.gz (rpm 4.1 and later; ships with RedHat 8)
+rpmbuild -ta &XercesC2SrcInstallDir;.tar.gz (rpm 4.1 and later; ships with RedHat 8)
</source>
<p>The &XercesCName; RPM specification can be found in
- <br/><code>&XercesCSrcInstallDir;/xerces-c.spec</code>.</p>
+ <br/><code>&XercesC2SrcInstallDir;/xerces-c.spec</code>.</p>
<p>Please refer to the <jump href="http://www.rpm.org/RPM-HOWTO">RPM-HOWTO</jump>,
for more RPM related information.</p>
</s2>
@@ -234,12 +234,12 @@
<ul>
<li>JDK 1.2.2 (or later).</li>
- <li>Xerces-J 1.0.1 (provided by &XercesCToolsInstallDir;)</li>
- <li>Xalan-J 0.19.2 (provided by &XercesCToolsInstallDir;)</li>
- <li>Stylebook 1.0-b2 (provided by &XercesCToolsInstallDir;)</li>
+ <li>Xerces-J 1.0.1 (provided by &XercesC2ToolsInstallDir;)</li>
+ <li>Xalan-J 0.19.2 (provided by &XercesC2ToolsInstallDir;)</li>
+ <li>Stylebook 1.0-b2 (provided by &XercesC2ToolsInstallDir;)</li>
</ul>
- <p>Before proceeding, copy the contents of the &XercesCToolsInstallDir;
+ <p>Before proceeding, copy the contents of the &XercesC2ToolsInstallDir;
distribution into your <code>$XERCESCROOT</code>. Then invoke
a terminal or a command window and setup PATH to include the
JDK 1.2.2 bin directory. Next, cd to the <code>$XERCESCROOT</code>
@@ -275,7 +275,7 @@
<s2 title="I wish to port &XercesCProjectName; to my favourite platform. Do you have any suggestions?">
<p>All platform dependent code in &XercesCProjectName; has been
isolated to a couple of files, which should ease the porting
- effort. Please refer to <jump href="program-others.html#PortingGuidelines">Porting
+ effort. Please refer to <jump href="program-others-&XercesC2Series;.html#PortingGuidelines">Porting
Guidelines</jump> for further details.</p>
</s2>
@@ -333,8 +333,8 @@
still cannot resolve your problem(s), there is more help. You
can find out if others have
solved this same problem before you, by checking the
- <jump href="mailing-lists.html">&XercesCName; mailing list archives</jump> and
- <jump href="&JiraURL;">&XercesCName; bug database</jump>.</p>
+ <jump href="&MailURI;">&XercesCName; mailing list archives</jump> and
+ <jump href="&BugURI;">&XercesCName; bug database</jump>.</p>
</s2>
</s1>
Modified: xerces/c/branches/xerces-2.8/doc/build-other.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.8/doc/build-other.xml?rev=630884&r1=630883&r2=630884&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.8/doc/build-other.xml (original)
+++ xerces/c/branches/xerces-2.8/doc/build-other.xml Mon Feb 25 07:46:00 2008
@@ -141,9 +141,9 @@
name based on the parser version (using apache xerces versioning)):</p>
<source>qsh:
cd <full path to &XercesCName;>/lib
-qar -cuv &XercesCUnixLib;&XercesCUnixSoName;.so *.o
+qar -cuv &XercesC2UnixLib;&XercesC2UnixSoName;.so *.o
will results in
-command = CRTBNDDIR BNDDIR(yourlib/libxercesc) TEXT('/yourlib/&XercesCName;/lib/&XercesCUnixLib;&XercesCUnixSoName;.so')
+command = CRTBNDDIR BNDDIR(yourlib/libxercesc) TEXT('/yourlib/&XercesCName;/lib/&XercesC2UnixLib;&XercesC2UnixSoName;.so')
command = ADDBNDDIRE BNDDIR(yourlib/libxercesc) OBJ((yourlib/LIBXERCESC *SRVPGM) )</source>
@@ -172,8 +172,8 @@
<source>
qsh:
cd <full path to &XercesCName;>/lib
-ln -s /qsys.lib/<outputdir>.lib/libxercesc.srvpgm &XercesCUnixLib;&XercesCUnixSoName;.so
-qar -cuv &XercesCUnixLib;&XercesCUnixSoName;.so *.o
+ln -s /qsys.lib/<outputdir>.lib/libxercesc.srvpgm &XercesC2UnixLib;&XercesC2UnixSoName;.so
+qar -cuv &XercesC2UnixLib;&XercesC2UnixSoName;.so *.o
</source>
<p>If you are on a v4 system using the ILE C++ PRPQ compiler (which is referred
Modified: xerces/c/branches/xerces-2.8/doc/build-winunix.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.8/doc/build-winunix.xml?rev=630884&r1=630883&r2=630884&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.8/doc/build-winunix.xml (original)
+++ xerces/c/branches/xerces-2.8/doc/build-winunix.xml Mon Feb 25 07:46:00 2008
@@ -43,7 +43,7 @@
project inside your application's solution.</p>
<p>The solutions containing the &XercesCName; project files and
all other samples are in the following sub-directories in the
- &XercesCSrcInstallDir; directory:</p>
+ &XercesC2SrcInstallDir; directory:</p>
<source>
(For VC6) Projects\Win32\VC6\xerces-all\xerces-all.dsw
@@ -65,7 +65,7 @@
</source>
<p>You must make sure that you are linking your application with
- the &XercesCWindowsLib;.lib library (or Debug/Static version of it
+ the &XercesC2WindowsLib;.lib library (or Debug/Static version of it
and also make sure that the associated DLL is somewhere in your
path.</p>
@@ -77,9 +77,7 @@
<note>If you are working on the AlphaWorks version which uses ICU,
you must have the ICU data DLL named <code>icudata.dll</code>
- available from your path setting. For finding out where you
- can get ICU from and build it, look at the
- <jump href="build-misc.html#faq-1">How to Build ICU</jump>.</note>
+ available from your path setting.</note>
<note>If the library is built with the ICU message loader,
or message catalog loader, then you need to make sure
@@ -120,15 +118,6 @@
and what risks you are taking. So read the following instructions
carefully before attempting to build it yourself.</p>
- <p>Besides having all necessary build tools, you also need to know what
- compilers we have tested &XercesCName; on. The following table lists the
- relevant platforms and compilers.</p>
-
- &build-winunix-supported-platforms;
-
- <!-- note about building on untested platforms - see entities.ent -->
- &build-winunix-note;
-
<p><em>Differences between the UNIX platforms:</em> The description below is
generic, but as every programmer is aware, there are minor differences
within the various UNIX flavors the world has been bestowed with.
@@ -141,10 +130,6 @@
discussion assumes you are working on Linux, but it is with subtle
understanding that you know how to interpret it for the other UNIX flavors.</p>
- <note>If you wish to build &XercesCName; with ICU,
- look at the <jump href="build-misc.html#faq-1">Building &XercesCName; with ICU</jump>.
- It tells you where you can get ICU and how to build &XercesCName; with it.</note>
-
<s3 title="Setting build environment variables">
<p>Before doing the build, you must first set your environment variables
to pick-up the compiler and also specify where you extracted &XercesCName;
@@ -154,7 +139,7 @@
compiler invocation command without any parameters (e.g. xlc_r, or g++, or cc)
and check if you get a proper response back.</p>
<p>Next set your &XercesCName; root path as follows:</p>
-<source>export XERCESCROOT=<full-path-to-&XercesCSrcInstallDir;></source>
+<source>export XERCESCROOT=<full-path-to-&XercesC2SrcInstallDir;></source>
<p>This should be the full path of the directory where you extracted &XercesCName;.
Note that this path should not have any spaces in it or the build process will fail. The
@@ -168,7 +153,7 @@
<p>As mentioned earlier, to build &XercesCName; from the source distribution,
you will need GNU make.</p>
- <p>If you look into the src/xercesc sub-directory in &XercesCSrcInstallDir;,
+ <p>If you look into the src/xercesc sub-directory in &XercesC2SrcInstallDir;,
you will notice the familiar configure script. It is tempting to run
this script directly as is normally the case, but wait a minute.
Even if you are
@@ -447,7 +432,7 @@
</source>
<p>The sample executable can be found in the bin sub-directory in
- &XercesCSrcInstallDir;. To delete all the generated object
+ &XercesC2SrcInstallDir;. To delete all the generated object
files and executables, run:</p>
<source>
make clean
@@ -551,7 +536,7 @@
</p>
<ul>
- <li> &XercesCSrcInstallDir;\Projects\Win32\BCB6\Xerces-all\Xerces-all.bpg </li>
+ <li> &XercesC2SrcInstallDir;\Projects\Win32\BCB6\Xerces-all\Xerces-all.bpg </li>
</ul>
<p> Each project in the group refers a directory below \Xerces-all.
@@ -559,7 +544,7 @@
</p>
<ul>
- <li> &XercesCSrcInstallDir;\Projects\Win32\BCB6\Xerces-all\XercesLib </li>
+ <li> &XercesC2SrcInstallDir;\Projects\Win32\BCB6\Xerces-all\XercesLib </li>
</ul>
<p> To build any project, open the project manager. Double click on the project
@@ -581,7 +566,7 @@
&XercesCName;.</p>
<ol>
- <li>Change directory to <code> &XercesCSrcInstallDir;\Projects\Win32\BCC.551\Xerces-all</code></li>
+ <li>Change directory to <code> &XercesC2SrcInstallDir;\Projects\Win32\BCC.551\Xerces-all</code></li>
<li>Run <code>MakeBuildDirs.bat</code>.</li>
<li>Then issue</li>
<ul>
@@ -603,18 +588,18 @@
<p>&XercesCName; source distribution provides a makefile <code>all.mak</code>
which will build everything including samples, tests and the parser library.</p>
<source>
-cd &XercesCSrcInstallDir;\Projects\Win32\VC6\xerces-all\all
+cd &XercesC2SrcInstallDir;\Projects\Win32\VC6\xerces-all\all
nmake -f all.mak "CFG=all - Win64 Release" CPP=ecl.exe
</source>
<p>If you want to just build the &XercesCName; parser library alone, then</p>
<source>
-cd &XercesCSrcInstallDir;\Projects\Win32\VC6\xerces-all\XercesLib
+cd &XercesC2SrcInstallDir;\Projects\Win32\VC6\xerces-all\XercesLib
nmake -f XercesLib.mak "CFG=XercesLib - Win64 Release" CPP=ecl.exe
</source>
<p>You must make sure that you are linking your application with
- the &XercesCWindowsLib;.lib library and also make sure that
+ the &XercesC2WindowsLib;.lib library and also make sure that
the associated DLL is somewhere in your path.</p>
</s3>
</s2>
Modified: xerces/c/branches/xerces-2.8/doc/build.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.8/doc/build.xml?rev=630884&r1=630883&r2=630884&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.8/doc/build.xml (original)
+++ xerces/c/branches/xerces-2.8/doc/build.xml Mon Feb 25 07:46:00 2008
@@ -21,39 +21,39 @@
<s1 title="Build Instructions">
<s2 title="Building on Windows and UNIX">
- <p>Read the <jump href="build-winunix.html">Building on Windows and UNIX</jump> document
+ <p>Read the <jump href="build-winunix-&XercesC2Series;.html">Building on Windows and UNIX</jump> document
or jump directly to:</p>
<ul>
- <li><jump href="build-winunix.html#WinNT">Building on Windows using Microsoft Visual C++</jump></li>
- <li><jump href="build-winunix.html#UNIX">Building on UNIX/Linux/Mac OS X platforms</jump></li>
- <li><jump href="build-winunix.html#CygWin">Building on Windows using Cygwin</jump></li>
- <li><jump href="build-winunix.html#MinGW">Building on Windows using MinGW-MSYS</jump></li>
- <li><jump href="build-winunix.html#WinBorlandCC">Building on Windows using Borland C++</jump></li>
- <li><jump href="build-winunix.html#WinBorlandBuilder">Building on Windows using Borland C++ Builder</jump></li>
- <li><jump href="build-winunix.html#WinIntel">Building 64 bit libraries on Windows using Intel C++</jump></li>
+ <li><jump href="build-winunix-&XercesC2Series;.html#WinNT">Building on Windows using Microsoft Visual C++</jump></li>
+ <li><jump href="build-winunix-&XercesC2Series;.html#UNIX">Building on UNIX/Linux/Mac OS X platforms</jump></li>
+ <li><jump href="build-winunix-&XercesC2Series;.html#CygWin">Building on Windows using Cygwin</jump></li>
+ <li><jump href="build-winunix-&XercesC2Series;.html#MinGW">Building on Windows using MinGW-MSYS</jump></li>
+ <li><jump href="build-winunix-&XercesC2Series;.html#WinBorlandCC">Building on Windows using Borland C++</jump></li>
+ <li><jump href="build-winunix-&XercesC2Series;.html#WinBorlandBuilder">Building on Windows using Borland C++ Builder</jump></li>
+ <li><jump href="build-winunix-&XercesC2Series;.html#WinIntel">Building 64 bit libraries on Windows using Intel C++</jump></li>
</ul>
</s2>
<s2 title="Building on Other Platforms">
- <p>Read the <jump href="build-other.html">Building on Other Platforms</jump> document
+ <p>Read the <jump href="build-other-&XercesC2Series;.html">Building on Other Platforms</jump> document
or jump directly to:</p>
<ul>
- <li><jump href="build-other.html#iSeries">Building &XercesCName; on iSeries (AS/400)</jump></li>
- <li><jump href="build-other.html#Mac">Building &XercesCName; on Macintosh</jump></li>
+ <li><jump href="build-other-&XercesC2Series;.html#iSeries">Building &XercesCName; on iSeries (AS/400)</jump></li>
+ <li><jump href="build-other-&XercesC2Series;.html#Mac">Building &XercesCName; on Macintosh</jump></li>
</ul>
</s2>
<s2 title="Other Build Instructions">
- <p>Read the <jump href="build-misc.html">Other Build Instructions</jump> document
+ <p>Read the <jump href="build-misc-&XercesC2Series;.html">Other Build Instructions</jump> document
or jump directly to:</p>
<ul>
- <li><jump href="build-misc.html#ICUPerl">Building &XercesCName; with ICU</jump></li>
- <li><jump href="build-misc.html#RPMLinux">Building &XercesCName; using RPM on Linux</jump></li>
- <li><jump href="build-misc.html#WinCOM">Building &XercesCName; COM Wrapper on Windows</jump></li>
- <li><jump href="build-misc.html#UserDoc">Building User Documentation</jump></li>
- <li><jump href="build-misc.html#PortInfo">I wish to port &XercesCProjectName; to my favourite platform. Do you have any suggestions?</jump></li>
- <li><jump href="build-misc.html#XMLChInfo">What should I define XMLCh to be?</jump></li>
- <li><jump href="build-misc.html#HelpInfo">Where can I look for more help?</jump></li>
+ <li><jump href="build-misc-&XercesC2Series;.html#ICUPerl">Building &XercesCName; with ICU</jump></li>
+ <li><jump href="build-misc-&XercesC2Series;.html#RPMLinux">Building &XercesCName; using RPM on Linux</jump></li>
+ <li><jump href="build-misc-&XercesC2Series;.html#WinCOM">Building &XercesCName; COM Wrapper on Windows</jump></li>
+ <li><jump href="build-misc-&XercesC2Series;.html#UserDoc">Building User Documentation</jump></li>
+ <li><jump href="build-misc-&XercesC2Series;.html#PortInfo">I wish to port &XercesCProjectName; to my favourite platform. Do you have any suggestions?</jump></li>
+ <li><jump href="build-misc-&XercesC2Series;.html#XMLChInfo">What should I define XMLCh to be?</jump></li>
+ <li><jump href="build-misc-&XercesC2Series;.html#HelpInfo">Where can I look for more help?</jump></li>
</ul>
</s2>
Modified: xerces/c/branches/xerces-2.8/doc/dom3.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.8/doc/dom3.xml?rev=630884&r1=630883&r2=630884&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.8/doc/dom3.xml (original)
+++ xerces/c/branches/xerces-2.8/doc/dom3.xml Mon Feb 25 07:46:00 2008
@@ -21,16 +21,16 @@
<s1 title="DOM Level 3 Support">
<s2 title="Disclaimer">
<p>
- The &XercesCName; &XercesCVersion; contains a partial implementation of the W3C Document Object Model
+ The &XercesCName; &XercesC2Version; contains a partial implementation of the W3C Document Object Model
Level 3. This implementation is experimental. The DOM Level 3 specification is
still in working draft stage: you should not consider this implementation complete or correct.</p>
<p>The limitations of this implementation are detailed below.
- Please, read this document before using &XercesCName; &XercesCVersion;.
+ Please, read this document before using &XercesCName; &XercesC2Version;.
</p>
</s2>
<s2 title="Introduction">
<p>
- The &XercesCName; &XercesCVersion; contains an experimental implementation of
+ The &XercesCName; &XercesC2Version; contains an experimental implementation of
a subset of the W3C DOM Level 3 as specified in </p>
<ul>
<li><jump href="http://www.w3.org/TR/DOM-Level-3-Core/">
@@ -42,7 +42,7 @@
</s2>
<s2 title='Implementation of DOM Level 3 Core'>
- <p>The following are implemented in &XercesCName; &XercesCVersion;.</p>
+ <p>The following are implemented in &XercesCName; &XercesC2Version;.</p>
<ul>
<li>
<code>DOMImplementationRegistry</code>, <code>DOMImplementationSource</code>
@@ -83,7 +83,7 @@
</s2>
<s2 title='Implementation of DOM Level 3 Load and Save'>
- <p>The following are implemented in &XercesCName; &XercesCVersion;.</p>
+ <p>The following are implemented in &XercesCName; &XercesC2Version;.</p>
<ul>
<li>
<code>DOMImplementationLS</code>
@@ -104,7 +104,7 @@
</s2>
<s2 title='Implementation of DOM Level 3 Abstract Schemas'>
- <p>The entire section has not been implemented in &XercesCName; &XercesCVersion;.</p>
+ <p>The entire section has not been implemented in &XercesCName; &XercesC2Version;.</p>
</s2>
</s1>
Modified: xerces/c/branches/xerces-2.8/doc/domcount.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.8/doc/domcount.xml?rev=630884&r1=630883&r2=630884&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.8/doc/domcount.xml (original)
+++ xerces/c/branches/xerces-2.8/doc/domcount.xml Mon Feb 25 07:46:00 2008
@@ -55,7 +55,7 @@
<em>-v=never</em> will not use any validation<br/>
<em>-v=auto</em> will validate if a DOCTYPE declaration or a schema declaration is present in the XML document</p>
<p>Here is a sample output from DOMCount</p>
-<source>cd &XercesCInstallDir;-linux/samples/data
+<source>cd &XercesC2InstallDir;-linux/samples/data
DOMCount -v=always personal.xml
personal.xml: 20 ms (37 elems)</source>
Modified: xerces/c/branches/xerces-2.8/doc/domprint.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.8/doc/domprint.xml?rev=630884&r1=630883&r2=630884&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.8/doc/domprint.xml (original)
+++ xerces/c/branches/xerces-2.8/doc/domprint.xml Mon Feb 25 07:46:00 2008
@@ -67,7 +67,7 @@
<em>-v=never</em> will not use any validation<br/>
<em>-v=auto</em> will validate if a DOCTYPE declaration or a schema declaration is present in the XML document</p>
<p>Here is a sample output from DOMPrint</p>
-<source>cd &XercesCInstallDir;-linux/samples/data
+<source>cd &XercesC2InstallDir;-linux/samples/data
DOMPrint -v=always personal.xml
<?xml version="1.0" encoding="iso-8859-1"?>
Modified: xerces/c/branches/xerces-2.8/doc/enumval.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.8/doc/enumval.xml?rev=630884&r1=630883&r2=630884&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.8/doc/enumval.xml (original)
+++ xerces/c/branches/xerces-2.8/doc/enumval.xml Mon Feb 25 07:46:00 2008
@@ -36,7 +36,7 @@
data structures.
</source>
<p>Here is a sample output from EnumVal</p>
-<source>cd &XercesCInstallDir;-linux/samples/data
+<source>cd &XercesC2InstallDir;-linux/samples/data
EnumVal personal.xml
ELEMENTS:
Modified: xerces/c/branches/xerces-2.8/doc/faq-build.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.8/doc/faq-build.xml?rev=630884&r1=630883&r2=630884&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.8/doc/faq-build.xml (original)
+++ xerces/c/branches/xerces-2.8/doc/faq-build.xml Mon Feb 25 07:46:00 2008
@@ -26,7 +26,7 @@
<a>
- <p>&XercesCName; &XercesCVersion; now supports C++ Namespace.</p>
+ <p>&XercesCName; &XercesC2Version; now supports C++ Namespace.</p>
<p>If C++ Namespace is ENABLED, users' applications must
namespace qualify all the &XercesCName; classes, data, and
@@ -36,7 +36,7 @@
properly qualified or scoped.
</p>
- <p>See the Programming Guide <jump href="program-others.html#CPPNamespace">
+ <p>See the Programming Guide <jump href="program-others-&XercesC2Series;.html#CPPNamespace">
Using C++ Namespace</jump> for details.
</p>
@@ -53,7 +53,7 @@
<p>Your application somehow has picked up the Microsoft SDK header <code>Msxml.h</code>
which has its own typedef of <code>DOMDocument</code>. This confuses
- with the &XercesCName; &XercesCVersion; <code>&XercesCNamespace;::DOMDocument</code>
+ with the &XercesCName; &XercesC2Version; <code>&XercesC2Namespace;::DOMDocument</code>
and thus lead to the compilation errors.</p>
<p> Qualifier the use of DOMDocument in your application explicitly e.g.
@@ -121,7 +121,7 @@
<p>Please check the following:</p>
<ol>
<li>If you're using the binary build of &XercesCName;, make sure that the OS and compiler are
- the same version as the ones used to build the binary &faq-build-faq-distrib1;. Different OS and
+ the same version as the ones used to build the binary. Different OS and
compiler versions might cause unresolved linking problems or compilation
errors. If the versions are different, rebuild the &XercesCName; library on
your system before building your application. If you're using ICU (which is
@@ -130,9 +130,9 @@
<li>Check that the library path is set properly and that the correct
versions of <code>gmake</code> and <code>autoconf</code> are on your system.</li>
<li>If C++ Namespace support is ENABLED (all the binary distributions of &XercesCName;
- &XercesCVersion; are built with C++ Namespace enabled), users' applications
+ &XercesC2Version; are built with C++ Namespace enabled), users' applications
must namespace qualify all the &XercesCName; classes, data and variables.
- See the Programming Guide <jump href="program-others.html#CPPNamespace">
+ See the Programming Guide <jump href="program-others-&XercesC2Series;.html#CPPNamespace">
Using C++ Namespace</jump> for details.</li>
</ol>
</a>
@@ -181,14 +181,14 @@
from Apache, you must have the &XercesCName; runtime library available from
your path settings.
</p>
- <p>On Windows this library is called <code>&XercesCWindowsDLL;.dll</code>
+ <p>On Windows this library is called <code>&XercesC2WindowsDLL;.dll</code>
which must be available from your <code>PATH</code> settings. (Note that there are
separate debug and release dlls for Windows. The release dll is named
- <code>&XercesCWindowsDLL;.dll</code>, and the debug dll
- is named <code>&XercesCWindowsDLL;d.dll)</code>.
+ <code>&XercesC2WindowsDLL;.dll</code>, and the debug dll
+ is named <code>&XercesC2WindowsDLL;d.dll)</code>.
</p>
- <p>On UNIX platforms the library is called &XercesCUnixLib;.so.&XercesCUnixSoName; (or
- &XercesCUnixLib;&XercesCUnixSoName;.so or &XercesCUnixLib;.sl.&XercesCUnixSoName;)
+ <p>On UNIX platforms the library is called &XercesC2UnixLib;.so.&XercesC2UnixSoName; (or
+ &XercesC2UnixLib;&XercesC2UnixSoName;.so or &XercesC2UnixLib;.sl.&XercesC2UnixSoName;)
which must be available from your <code>LD_LIBRARY_PATH</code>
(or <code>LIBPATH</code> or <code>SHLIB_PATH</code>) environment variable.</p>
@@ -367,7 +367,7 @@
<p>
Due to the recent directory change, you may need to either update your
project file, makefile, or your source/header file, for details,
- please refer to <jump href="migrate.html#DirChange">Directory Change. </jump></p>
+ please refer to <jump href="migrate-&XercesC2Series;.html#DirChange">Directory Change. </jump></p>
</a>
</faq>
@@ -375,8 +375,9 @@
<q>Cannot load message domain, Xerces Panic Error?</q>
<a>
<p>If the parser is built with icu message loader (like IBM XML4C binaries),
- you need to make sure that the message library &faq-build-faq-distrib3;
- is located in a directory which is on the library search path.
+ you need to make sure that the message library (for the exact name see
+ <jump href="faq-distrib-&XercesC2Series;.html#faq-2">FAQ: Which DLLs do I need to distribute
+ with my application?</jump>) is located in a directory which is on the library search path.
Or the message resource file, XercesMessages_en_US.res, is in the directory given at the call to
XMLPlatformUtils::Initialize(), or is located in the directory pointed to by the environment variable
XERCESC_NLS_HOME, or at $XERCESCROOT/msg.
@@ -419,7 +420,7 @@
<p>To use the internal XML based application that creates the
documentation, you must have a Java Virtual machine installed
on your system. The application itself, written in Java, is
- provided in the &XercesCToolsInstallDir; distribution. You
+ provided in the &XercesC2ToolsInstallDir; distribution. You
should copy its contents into your <code>$XERCESCROOT</code>
directory.</p>
Modified: xerces/c/branches/xerces-2.8/doc/faq-contributing.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.8/doc/faq-contributing.xml?rev=630884&r1=630883&r2=630884&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.8/doc/faq-contributing.xml (original)
+++ xerces/c/branches/xerces-2.8/doc/faq-contributing.xml Mon Feb 25 07:46:00 2008
@@ -31,15 +31,14 @@
</p>
<ol>
<li>Check out and build the most recent Xerces code. For
- instructions on how to do this, see <jump
- href="repository.html">Xerces-C++
+ instructions on how to do this, see <jump href="&RepURI;">Xerces-C++
Repository Information</jump>. If you do this, you can confirm that your
bug still exists and has not been fixed since the last
release.
</li>
<li>
Write up your bug report as per the instructions described in
- the <jump href="bug-report.html">Bug-Reporting</jump> page.
+ the <jump href="&BugURI;">Bug-Reporting</jump> page.
</li>
<li>
Describe why your solution works.
@@ -58,11 +57,11 @@
apply.
</li>
<li>
- Submit a bug report on <jump href="http://nagoya.apache.org/jira">Jira</jump>,
- the Apache bug database. Pick the product "Xerces-C++"
- (remembering to attach your patches and test code)
- or, if you think your patch might need some discussion,
- post it to the xerces-c-dev list.
+ Submit a bug report to the Xerces-C++ bug database as
+ described on the <jump href="&BugURI;">Bug-Reporting</jump> page.
+ Pick the product "Xerces-C++" (remembering to attach your patches
+ and test code) or, if you think your patch might need some discussion,
+ post it to the <jump href="&MailURI;">developer mailing list</jump>.
</li>
</ol>
</a>
@@ -75,15 +74,15 @@
<p>The informal release policies for &XercesCName; are (using a versioning of version.release.modification):</p>
<ul>
<li>We don't try to enforce binary compatibility between new versions and releases.</li>
- <li>New versions and releases will be delivered when a certain number of bug fixes/new features have been added
- (as decided by the committers) or when a dependent product, such as XALAN, wants to ship a new release that uses new Xerces features.</li>
+ <li>New versions and releases will be delivered when a certain number of bug fixes/new features have been added
+ (as decided by the committers) or when a dependent product, such as XALAN, wants to ship a new release that uses new Xerces features.</li>
<li>New modification levels will almost never be issued, the only exception is a showstopper bug encountered within
a release. if no commit has been made on the trunk which would result in binary incompatibility, and no commit has been made that is not thought to
be release-quality, then the modification release can be created by tagging the trunk; otherwise, a branch (new release) will need to be created and the show stopper
fixed there.</li>
<li>Any normal bug is fixed only in the HEAD branch (latest development code).</li>
</ul>
-
+
<p>The specific source and binary compatibility objectives for these release policies and the corresponding allowed source changes are:</p>
<ul>
<li>x.x.x to x.x.y: the API is the same to ensure binary compatibility.</li>
@@ -92,8 +91,8 @@
<ul>
<li>Add new non-virtual functions.</li>
<li>Add new classes.</li>
- <li>Add new STATIC data members.</li>
- </ul>
+ <li>Add new STATIC data members.</li>
+ </ul>
<li>To maintain binary compatibility you cannot:</li>
<ul>
<li>Add new virtual functions as this will change the layout of the virtual function table.</li>
@@ -108,11 +107,11 @@
</ul>
<li>x.x.x to x.y.z: the API is source code compatible but not binary compatible (a recompilation of an application that uses the public headers of &XercesCName; should work).</li>
<ul>
- <li>This means that to maintain release to release source code compatibility the signature of public methods can only be
+ <li>This means that to maintain release to release source code compatibility the signature of public methods can only be
changed by adding default parameters.</li>
<li>Signatures of private and protected methods can be changed and/or removed.</li>
<li>Methods that are deprecated should be marked with the JavaDoc tag @deprecated in the header file.</li>
- </ul>
+ </ul>
<li>x.x.x to a.b.c: the API may not be source code compatible and is not binary compatible (a recompilation of an application using &XercesCName; may fail).</li>
<ul>
<li>In this situation, a separate branch of the code will be created so that bug fixes may be applied to the last version.</li>
@@ -121,58 +120,58 @@
</ul>
</a>
</faq>
-
+
<faq title="Coding Conventions">
<q>What are the coding conventions for &XercesCName;?
</q>
- <a>
+ <a>
<p>As with any coding effort, there are always arguments over what coding conventions to use. Everyone thinks
that they have the best style which leads to the entire source tree looking different. This causes consternation
- as well as eye fatigue on subsequent developers that need to maintain the code. Therefore, we are going to
- make an attempt at defining some basic coding conventions for &XercesCName;. When committing files or providing
+ as well as eye fatigue on subsequent developers that need to maintain the code. Therefore, we are going to
+ make an attempt at defining some basic coding conventions for &XercesCName;. When committing files or providing
patches please keep them in mind:</p>
- <ol>
- <li>All classes should have a constructor, destructor, assignment operator and copy constructor to
+ <ol>
+ <li>All classes should have a constructor, destructor, assignment operator and copy constructor to
avoid compiler generated default versions of these.</li>
<ul>
<li>If a class contains only static methods, only a private constructor is required.</li>
<li>If a class contains any virtual methods, the destructor should be virtual.</li>
<li>If a class has a public or protected constructor, it should declare private assignment operator
and copy constructor which are not implemented (unless of course you need either of these).</li>
- </ul>
-
+ </ul>
+
<li>If you add a catch(...) block be sure to add the following block
- <code>
+ <code>
catch(const OutOfMemoryException&)
{
throw;
}
</code> so the OutOfMemory condition does not get absorbed.</li>
-
- <li>If you change the serialization format (by adding something to be serialized or removing something that
+
+ <li>If you change the serialization format (by adding something to be serialized or removing something that
was serialized) increment the XERCES_GRAMMAR_SERIALIZATION_LEVEL constant in XercesVersion.hpp.</li>
-
+
<li>If a class allocates memory or is instantiated with new then it should inherit from XMemory.</li>
-
+
<li>Use a tab size of 4 and insert them as spaces instead of keeping tabs.</li>
-
- <li>The code is written to be platform independent. Platform specific code should only be in the
+
+ <li>The code is written to be platform independent. Platform specific code should only be in the
util/Platforms, util/Transcoders, util/MsgLoaders, and util/NetAccessors directories.</li>
-
- <li>The header file name and the source file name should both be named corresponding to the primary
- class they contain. For example class StringPool should be in the header file StringPool.hpp and in
+
+ <li>The header file name and the source file name should both be named corresponding to the primary
+ class they contain. For example class StringPool should be in the header file StringPool.hpp and in
the source file StringPool.cpp.</li>
-
+
<li>In general, code should be documented with comments. Use JavaDoc tags to describe methods.</li>
-
+
<li>The naming convention for ENUMS should be choosen to be unique and descriptive
(i.e. INVALID or UNKNOWN) to avoid colliding with predefined macros in other
products. The current style of using ALL CAP enums should be phased out with
Mixed Case instead, except for names specified in standards (for example, TEXT_NODE
- should not be converted to mixed case for standards compliance).</li>
-
- </ol>
+ should not be converted to mixed case for standards compliance).</li>
+
+ </ol>
</a>
</faq>
-
-</faqs>
+
+</faqs>
Modified: xerces/c/branches/xerces-2.8/doc/faq-distrib.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.8/doc/faq-distrib.xml?rev=630884&r1=630883&r2=630884&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.8/doc/faq-distrib.xml (original)
+++ xerces/c/branches/xerces-2.8/doc/faq-distrib.xml Mon Feb 25 07:46:00 2008
@@ -20,20 +20,6 @@
<faqs title="Distributing &XercesCName;">
- <faq title="What platforms / compilers are being used to build the binary distribution kits?">
-
- <q>What platforms / compilers are being used to build the binary distribution kits?</q>
-
- <a>
-
- <p>&XercesCProjectName; binaries has been built on the following platforms with
- these compilers</p>
-
- &build-winunix-supported-platforms;
-
- </a>
- </faq>
-
<faq title="What are the differences between Xerces-C and XML4C?">
<q>What are the differences between Xerces-C and XML4C?</q>
<a>
@@ -61,12 +47,12 @@
<p>You only need to distribute <em>one</em> file:<br></br>
- &XercesCWindowsDLL;.dll for Windows, or<br/>
- &XercesCUnixLib;&XercesCUnixSoName;.a for AIX, or<br/>
- &XercesCUnixLib;.so.&XercesCUnixSoName; for Solaris/Linux, or<br/>
- &XercesCUnixLib;.sl.&XercesCUnixSoName; for HP-UX on PA-RISC, or<br/>
- &XercesCUnixLib;.so.&XercesCUnixSoName; for HP-UX on IA64, or<br/>
- &XercesCUnixLib;.&XercesCUnixSoName;.dylib for Mac OS X.
+ &XercesC2WindowsDLL;.dll for Windows, or<br/>
+ &XercesC2UnixLib;&XercesC2UnixSoName;.a for AIX, or<br/>
+ &XercesC2UnixLib;.so.&XercesC2UnixSoName; for Solaris/Linux, or<br/>
+ &XercesC2UnixLib;.sl.&XercesC2UnixSoName; for HP-UX on PA-RISC, or<br/>
+ &XercesC2UnixLib;.so.&XercesC2UnixSoName; for HP-UX on IA64, or<br/>
+ &XercesC2UnixLib;.&XercesC2UnixSoName;.dylib for Mac OS X.
</p>
<p>However, if you are using the ICU transcoder then in
@@ -129,8 +115,8 @@
-t <transcoder> can be 'icu' or 'native'
-r <thread option> can be 'pthread' or 'dce' (only used on HP-11)
-h to get help on these commands
-Example: perl packageBinaries.pl -s$HOME/&XercesCSrcInstallDir;
- -o$HOME/&XercesCInstallDir;
+Example: perl packageBinaries.pl -s$HOME/&XercesC2SrcInstallDir;
+ -o$HOME/&XercesC2InstallDir;
-cgcc -xg++ -minmem
-nfileonly -tnative</source>
@@ -150,7 +136,7 @@
publish binaries for every platform. If you wish to
contribute your time and effort in building binaries for a
specific platform/environment then please send a mail to the
- <jump href="mailing-lists.html">&XercesCName; development mailing list</jump>.
+ <jump href="&MailURI;">&XercesCName; developer mailing list</jump>.
We can definitely use any extra help in this open source
project</p>
</a>
@@ -166,7 +152,7 @@
many platforms as there are. Again, due to limited resources
we cannot do all the ports. We will help you make this port
happen. Here are some <jump
- href="program-others.html#PortingGuidelines">Porting
+ href="program-others-&XercesC2Series;.html#PortingGuidelines">Porting
Guidelines</jump>.</p>
<p>We strongly encourage you to submit the changes that
@@ -175,7 +161,7 @@
them available in the future releases.</p>
<p>All porting changes may be sent to the
- <jump href="mailing-lists.html">&XercesCName; development mailing list</jump>
+ <jump href="&MailURI;">&XercesCName; developer mailing list</jump>
.</p>
</a>
</faq>
@@ -185,7 +171,7 @@
<q>How can I port &XercesCProjectName; to my favourite platform?</q>
<a>
<p>Here are some <jump
- href="program-others.html#PortingGuidelines">Porting
+ href="program-others-&XercesC2Series;.html#PortingGuidelines">Porting
Guidelines</jump>.</p>
</a>
</faq>
@@ -207,7 +193,7 @@
<jump href="http://www.stack.nl/~dimitri/doxygen/">Doxygen</jump> and
<jump href="http://www.research.att.com/sw/tools/graphviz/">GraphViz</jump>.</p>
- <p>See <jump href="faq-build.html#faq-18">
+ <p>See <jump href="faq-build-&XercesC2Series;.html#faq-18">
FAQ: Regenerating (API) documentation?</jump></p>
</a>
@@ -219,8 +205,7 @@
<a>
<p>Yes! Read the license agreement first and if you still
have further questions, then please address them to the
- <jump href="mailing-lists.html">&XercesCName; user mailing list</jump>
- .</p>
+ <jump href="&MailURI;">&XercesCName; user mailing list</jump>.</p>
</a>
</faq>
Modified: xerces/c/branches/xerces-2.8/doc/faq-other.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.8/doc/faq-other.xml?rev=630884&r1=630883&r2=630884&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.8/doc/faq-other.xml (original)
+++ xerces/c/branches/xerces-2.8/doc/faq-other.xml Mon Feb 25 07:46:00 2008
@@ -32,7 +32,7 @@
integers which contain the number of seconds since 1st January 1970,
so the magic boundary to worry about is the year 2038 and not 2000.
But modern operating systems shouldn't cause any trouble at all.</p>
-
+
<p>The Apache Xerces project is an open-source software product
of the Apache Software Foundation. The project and the Foundation
cannot and does not offer legal assurances regarding any suitability
@@ -67,12 +67,12 @@
<p>If you don't have the header files, you have to find the version
information from the shared library name. On Windows right click on
- the DLL name &XercesCWindowsDLL;.dll in the bin directory and look up
+ the DLL name &XercesC2WindowsDLL;.dll in the bin directory and look up
properties. The version information may be found on the Version tab.</p>
- <p>On AIX, just look for the library name &XercesCUnixLib;&XercesCUnixSoName;.a (or
- &XercesCUnixLib;.so.&XercesCUnixSoName; on Solaris/Linux/IA64 HP-UX
- and &XercesCUnixLib;.sl.&XercesCUnixSoName; on PA-RISC HP-UX). The
+ <p>On AIX, just look for the library name &XercesC2UnixLib;&XercesC2UnixSoName;.a (or
+ &XercesC2UnixLib;.so.&XercesC2UnixSoName; on Solaris/Linux/IA64 HP-UX
+ and &XercesC2UnixLib;.sl.&XercesC2UnixSoName; on PA-RISC HP-UX). The
version number is indicated in the name of the library.</p>
</a>
</faq>
@@ -106,23 +106,50 @@
</a>
</faq>
- <!-- see entities.ent for the content for faq-other-support -->
- &faq-other-support;
+ <faq title="Is there any kind of support available for &XercesCName;?">
+ <q>Is there any kind of support available for &XercesCName;?</q>
+ <a>
+ <p>&XercesCName; comes with <em>no</em> formal support.</p>
+
+ <p>Every volunteer project obtains its strength from the people involved in
+ it. Mailing lists provide a simple and effective communication mechanism. You
+ are welcome to join any of these mailing lists (or all of them if you wish).
+ You can choose to lurk, or to actively participate. It is up to you. Before you
+ join these lists, you should look over the resources in the Reference Library
+ section</p>
+
+ <p>Instructions for subscribing as well as archives are available at the
+ <jump href="&MailURI;">&XercesCName; mailing lists</jump> page.</p>
+ </a>
+ </faq>
+
<faq title="I found a defect -- how do I report it?">
<q>I found a defect -- how do I report it?</q>
<a>
-
- <p>See <jump href="bug-report.html">Bug Reporting</jump>.
+ <p>See <jump href="&BugURI;">Bug Reporting</jump>.
</p>
-
</a>
</faq>
- <!-- see entities.ent for the content for faq-other-patch -->
- &faq-other-patch;
+ <faq title="I have a patch to the &XercesCName; source code. How do I submit it?">
+ <q>I have a patch to the &XercesCName; source code. How do I submit it?</q>
+ <a>
+ <p>Mail it to the <jump href="&MailURI;">&XercesCName;
+ development mailing list</jump>. Its also a good idea to add a report to
+ <jump href="&BugURI;">&XercesCName; bug database</jump> to track the issue.
+ There are no set rules about
+ how or what must be included -- if you have fixed a problem or enhanced the code
+ in some way, we really would like to get your changes, and will take them in
+ any reasonable form.</p>
+
+ <p>Generally a diff of the changed files against the current sources from the
+ <jump href="&RepURI;">&XercesCName; repository</jump> is good, along with some kind of
+ description of what the change is. (Working with the current sources is important!)</p>
+ </a>
+ </faq>
<faq title="Where can I get predefined character entity definitions?">
@@ -142,7 +169,7 @@
<a>
- <p>No. The &XercesCName; &XercesCVersion; only has partial XPath implementation
+ <p>No. The &XercesCName; &XercesC2Version; only has partial XPath implementation
for the purposes of handling Schema identity constraints. For full XPath
support, you can refer
<jump href="http://xml.apache.org/xalan-c/overview.html">Apache Xalan C++</jump> or
Modified: xerces/c/branches/xerces-2.8/doc/faq-parse.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.8/doc/faq-parse.xml?rev=630884&r1=630883&r2=630884&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.8/doc/faq-parse.xml (original)
+++ xerces/c/branches/xerces-2.8/doc/faq-parse.xml Mon Feb 25 07:46:00 2008
@@ -26,14 +26,14 @@
<a>
- <p>Yes. The &XercesCName; &XercesCVersion; contains an implementation
+ <p>Yes. The &XercesCName; &XercesC2Version; contains an implementation
of the W3C XML Schema Language, a recommendation of the Worldwide Web Consortium
available in three parts:
<jump href="http://www.w3.org/TR/xmlschema-0/">XML Schema: Primer</jump> and
<jump href="http://www.w3.org/TR/xmlschema-1/">XML Schema: Structures</jump> and
<jump href="http://www.w3.org/TR/xmlschema-2/">XML Schema: Datatypes</jump>.
We consider this implementation complete. See
- <jump href="schema.html#limitation">the Schema page</jump> for limitations.</p>
+ <jump href="schema-&XercesC2Series;.html#limitation">the Schema page</jump> for limitations.</p>
</a>
</faq>
@@ -44,19 +44,19 @@
<a>
- <p>The &XercesCName; &XercesCVersion; contains an implementation
+ <p>The &XercesCName; &XercesC2Version; contains an implementation
of the W3C XML Schema Language, a recommendation of the Worldwide Web Consortium
available in three parts:
<jump href="http://www.w3.org/TR/xmlschema-0/">XML Schema: Primer</jump> and
<jump href="http://www.w3.org/TR/xmlschema-1/">XML Schema: Structures</jump> and
<jump href="http://www.w3.org/TR/xmlschema-2/">XML Schema: Datatypes</jump>.
We consider this implementation complete. See
- <jump href="schema.html#limitation">the Schema page</jump> for limitations.</p>
+ <jump href="schema-&XercesC2Series;.html#limitation">the Schema page</jump> for limitations.</p>
<p>If you find any Schema feature which is specified in the W3C XML Schema Language
- Recommendation does not work with &XercesCName; &XercesCVersion;, we encourage
+ Recommendation does not work with &XercesCName; &XercesC2Version;, we encourage
the submission of bugs as described in
- <jump href="bug-report.html">Bug Reporting</jump> page.
+ <jump href="&BugURI;">Bug-Reporting</jump> page.
</p>
</a>
@@ -90,7 +90,7 @@
<faq title="Is it OK to call the XMLPlatformUtils::Initialize/Terminate pair of routines multiple times in one program?">
<q>Is it OK to call the XMLPlatformUtils::Initialize/Terminate pair of routines multiple times in one program?</q>
<a>
- <p>Yes. Since &XercesCName; &XercesCVersion152;, the code has been enhanced so that
+ <p>Yes. Since &XercesCName; 1.5.2, the code has been enhanced so that
calling XMLPlatformUtils::Initialize/Terminate pair of routines
multiple times in one process is now allowed.
</p>
@@ -176,7 +176,7 @@
<a>
- <p>Please make sure you are using the &XercesCName; &XercesCVersion152; or up.
+ <p>Please make sure you are using the &XercesCName; 1.5.2 or up.
</p>
<p>Earlier version of &XercesCName; does not allow XMLPlatformUtils::Initialize()/Terminate()
@@ -431,7 +431,7 @@
<faq title="How to write out a DOM tree into a string or an XML file?">
<q>How to write out a DOM tree into a string or an XML file?</q>
<a>
- <p>Please make sure you are using &XercesCName; &XercesCVersion; or up.</p>
+ <p>Please make sure you are using &XercesCName; &XercesC2Version; or up.</p>
<p>You can use
the DOMWriter::writeToString, or DOMWriter::writeNode to serialize a DOM tree.
@@ -772,8 +772,8 @@
<p>The function <code>SAX2XMLReader::setProperty(const XMLCh* const name, void* value)</code>
and <code>DOMBuilder::setProperty(const XMLCh* const name, void* value)</code>
takes a void pointer for the property value. Application is required to initialize this void pointer
- to a correct type. See <jump href="program-sax2.html#SAX2Properties">SAX2 Programming Guide</jump>
- and <jump href="program-dom.html#DOMBuilderProperties">DOM Programming Guide</jump>
+ to a correct type. See <jump href="program-sax2-&XercesC2Series;.html#SAX2Properties">SAX2 Programming Guide</jump>
+ and <jump href="program-dom-&XercesC2Series;.html#DOMBuilderProperties">DOM Programming Guide</jump>
to learn exactly what type of property value that each property expects for processing.
Passing a void pointer that was initialized with a wrong type will lead to unexpected result.
</p>
@@ -790,7 +790,7 @@
<p>The function <code>void* SAX2XMLReader::getProperty(const XMLCh* const name)</code>
and <code>void* DOMBuilder::getProperty(const XMLCh* const name)</code>
returns a void pointer for the property value. See
- <jump href="program-sax2.html#SAX2Properties">SAX2 Programming Guide</jump> and
+ <jump href="program-sax2-&XercesC2Series;.html#SAX2Properties">SAX2 Programming Guide</jump> and
exactly what type of object each property returns.
</p>
<p>The parser owns the returned pointer. The memory allocated for
@@ -799,8 +799,8 @@
is deleted, callers need to copy and store the returned information
somewhere else; otherwise you may get unexpected result. Since the returned
pointer is a generic void pointer, see
- <jump href="program-sax2.html#SAX2Properties">SAX2 Programming Guide</jump> and
- <jump href="program-dom.html#DOMBuilderProperties">DOM Programming Guide</jump> to learn
+ <jump href="program-sax2-&XercesC2Series;.html#SAX2Properties">SAX2 Programming Guide</jump> and
+ <jump href="program-dom-&XercesC2Series;.html#DOMBuilderProperties">DOM Programming Guide</jump> to learn
exactly what type of property value each property returns for replication.
</p>
@@ -822,7 +822,7 @@
validation is turned off.
</p>
- <p>To ignore the DTD, with &XercesCName; &XercesCVersion; or up, you can call
+ <p>To ignore the DTD, with &XercesCName; &XercesC2Version; or up, you can call
<code>setLoadExternalDTD(false)</code> (or
<code>setFeature(XMLUni::fgXercesLoadExternalDTD, false)</code>
to disable the loading of external DTD. The parser will then ignore
@@ -872,7 +872,7 @@
back to the parser, it will not print the DOMNode node value as is. The DOMWriter
may do some "touch up" to the output data for it to be parsable.</p>
- <p>See <jump href="program-dom.html#DOMWriterEntityRef">How does DOMWriter handle built-in entity
+ <p>See <jump href="program-dom-&XercesC2Series;.html#DOMWriterEntityRef">How does DOMWriter handle built-in entity
Reference in node value?</jump> to understand further how DOMWriter touches up the entity reference.
</p>
</a>
Modified: xerces/c/branches/xerces-2.8/doc/install.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.8/doc/install.xml?rev=630884&r1=630883&r2=630884&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.8/doc/install.xml (original)
+++ xerces/c/branches/xerces-2.8/doc/install.xml Mon Feb 25 07:46:00 2008
@@ -34,47 +34,47 @@
<s3 title="Source distribution">
<p>The &XercesCName; source is available in the source distribution:
- &XercesCSrcInstallDir;.zip.</p>
+ &XercesC2SrcInstallDir;.zip.</p>
<p>Install the &XercesCName; source distribution by using <code>unzip</code>
- on the &XercesCSrcInstallDir;.zip archive in the Windows environment. You can
+ on the &XercesC2SrcInstallDir;.zip archive in the Windows environment. You can
use WinZip, or any other UnZip utility:</p>
<source>
-unzip &XercesCSrcInstallDir;.zip
+unzip &XercesC2SrcInstallDir;.zip
</source>
- <p>This creates the '&XercesCSrcInstallDir;' sub-directory
+ <p>This creates the '&XercesC2SrcInstallDir;' sub-directory
containing the &XercesCName; source distribution. </p>
<p>If you need to build the &XercesCName; source after installation,
- please follow the <jump href="build.html">Build Instructions</jump>.</p>
+ please follow the <jump href="build-&XercesC2Series;.html">Build Instructions</jump>.</p>
</s3>
<s3 title="Binary distribution">
<p>Install the &XercesCName; binary distribution by using <code>unzip</code>
- on the &XercesCInstallDir;-{arch}-windows-{compiler}.zip archive in
+ on the &XercesC2InstallDir;-{arch}-windows-{compiler}.zip archive in
the Windows environment. Here {arch} denotes the CPU architecture
and {compiler} denotes the C++ compiler of your choice. You can use
WinZip, or any other UnZip utility. For example:</p>
<source>
-unzip &XercesCInstallDir;-x86-windows-vc_8_0.zip
+unzip &XercesC2InstallDir;-x86-windows-vc_8_0.zip
</source>
- <p>This creates a '&XercesCInstallDir;-x86-windows-vc_8_0'
+ <p>This creates a '&XercesC2InstallDir;-x86-windows-vc_8_0'
sub-directory containing the &XercesCName; binary distribution.</p>
- <p>You need to add the '&XercesCInstallDir;-{arch}-windows-{compiler}\bin'
+ <p>You need to add the '&XercesC2InstallDir;-{arch}-windows-{compiler}\bin'
directory to your path.
To do this go to the start menu, click the settings menu and
select control panel. When the control panel opens, double
click on System and select the 'Environment' tab.
Locate the PATH variable under system variables and add
- <full-path-to-&XercesCInstallDir;-{arch}-windows-{compiler}>\bin
+ <full-path-to-&XercesC2InstallDir;-{arch}-windows-{compiler}>\bin
to the PATH variable.</p>
<p>The binary distribution contains the pre-built parser libraries
and sample executables. Please refer to the
- <jump href="samples.html">Samples</jump> for how to run the
+ <jump href="samples-&XercesC2Series;.html">Samples</jump> for how to run the
samples.</p>
</s3>
@@ -88,46 +88,46 @@
<s3 title="Source distribution">
<p>The &XercesCName; source is available in the source distribution:
- &XercesCSrcInstallDir;.tar.gz.</p>
+ &XercesC2SrcInstallDir;.tar.gz.</p>
<p>Install the &XercesCName; source distribution
- &XercesCSrcInstallDir;.tar.gz by extracting the files
+ &XercesC2SrcInstallDir;.tar.gz by extracting the files
from the compressed archive:</p>
<source>
-gzip -d &XercesCSrcInstallDir;.tar.gz
-tar -xf &XercesCSrcInstallDir;.tar
+gzip -d &XercesC2SrcInstallDir;.tar.gz
+tar -xf &XercesC2SrcInstallDir;.tar
</source>
- <p>This creates the '&XercesCSrcInstallDir;' sub-directory
+ <p>This creates the '&XercesC2SrcInstallDir;' sub-directory
containing the &XercesCName; source distribution. </p>
<p>If you need to build the &XercesCName; source after installation,
- please follow the <jump href="build.html">Build Instructions</jump>.</p>
+ please follow the <jump href="build-&XercesC2Series;.html">Build Instructions</jump>.</p>
</s3>
<s3 title="Binary distribution">
- <p>Install the binary distribution &XercesCInstallDir;-{arch}-{os}-{compiler}.tar.gz
+ <p>Install the binary distribution &XercesC2InstallDir;-{arch}-{os}-{compiler}.tar.gz
by extracting the files from the compressed archive. Here {arch}
denotes the CPU architecture, {os} denotes the operating system,
and {compiler} denotes the C++ compiler of your choice.
For example:</p>
<source>
-gzip -d &XercesCInstallDir;-x86-linux-gcc_3_4.tar.gz
-tar -xf &XercesCInstallDir;-x86-linux-gcc_3_4.tar
+gzip -d &XercesC2InstallDir;-x86-linux-gcc_3_4.tar.gz
+tar -xf &XercesC2InstallDir;-x86-linux-gcc_3_4.tar
</source>
- <p>This will create an '&XercesCInstallDir;-x86-linux-gcc_3_4'
+ <p>This will create an '&XercesC2InstallDir;-x86-linux-gcc_3_4'
sub-directory containing the &XercesCName; binary distribution.</p>
<p>You will need to add the
- &XercesCInstallDir;-{arch}-{os}-{compiler}/bin directory to your
+ &XercesC2InstallDir;-{arch}-{os}-{compiler}/bin directory to your
PATH environment variable:</p>
<p>For Bourne Shell, K Shell or Bash, type: </p>
<source>
-export PATH="$PATH:<full-path-to-&XercesCInstallDir;-{arch}-{os}-{compiler}>/bin"
+export PATH="$PATH:<full-path-to-&XercesC2InstallDir;-{arch}-{os}-{compiler}>/bin"
</source>
<p>For C Shell, type:</p>
<source>
-setenv PATH "$PATH:<full-path-to-&XercesCInstallDir;-{arch}-{os}-{compiler}>/bin"
+setenv PATH "$PATH:<full-path-to-&XercesC2InstallDir;-{arch}-{os}-{compiler}>/bin"
</source>
<p>If you wish to make this setting permanent, you need to change
@@ -140,7 +140,7 @@
<p>In the following shell commands, the <xerces-path>
denotes the full path to the
- &XercesCInstallDir;-{arch}-{os}-{compiler} directory. For
+ &XercesC2InstallDir;-{arch}-{os}-{compiler} directory. For
Bourne Shell, K Shell or Bash, type:</p>
<source>
export LIBPATH=<xerces-path>/lib:$LIBPATH (AIX)
@@ -159,7 +159,7 @@
<p>The binary distribution contains the pre-built parser libraries
and sample executables. Please refer to the
- <jump href="samples.html">Samples</jump> for how to run the
+ <jump href="samples-&XercesC2Series;.html">Samples</jump> for how to run the
samples.</p>
</s3>
</s2>
@@ -172,19 +172,19 @@
<s3 title="Source distribution">
<p>The &XercesCName; source is available in the source distribution:
- &XercesCSrcInstallDir;.tar.gz.</p>
+ &XercesC2SrcInstallDir;.tar.gz.</p>
<p>Install the &XercesCName; source distribution
- &XercesCSrcInstallDir;.tar.gz by extracting the files
+ &XercesC2SrcInstallDir;.tar.gz by extracting the files
from the compressed archive:</p>
<source>
-tar -xfz &XercesCSrcInstallDir;.tar.gz
+tar -xfz &XercesC2SrcInstallDir;.tar.gz
</source>
- <p>This creates the '&XercesCSrcInstallDir;' sub-directory
+ <p>This creates the '&XercesC2SrcInstallDir;' sub-directory
containing the &XercesCName; source distribution. </p>
<p>If you need to build the &XercesCName; source after installation,
- please follow the <jump href="build.html">Build Instructions</jump>.
+ please follow the <jump href="build-&XercesC2Series;.html">Build Instructions</jump>.
</p>
</s3>
@@ -194,7 +194,7 @@
<jump href="http://www.cygwin.com">Cygwin</jump> setup.exe.
When you reach the "Packages" step of the Cygwin Setup wizard,
expand the "Devel" category, then click in the "New" column next
- to "xerces-c-devel" until it reads "&XercesCVersion;-X".</p>
+ to "xerces-c-devel" until it reads "&XercesC2Version;-X".</p>
<p>This will install the necessary libraries and include files
for the &XercesCName; binary distribution.</p>
@@ -211,7 +211,7 @@
Sample executables may be available in a future release on the
Cygwin platform. In the meantime, they may be built from the
source distribution by following the
- <jump href="build.html">Build Instructions</jump> for
+ <jump href="build-&XercesC2Series;.html">Build Instructions</jump> for
"Building samples".</p>
</s3>
</s2>
Modified: xerces/c/branches/xerces-2.8/doc/migration.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.8/doc/migration.xml?rev=630884&r1=630883&r2=630884&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.8/doc/migration.xml (original)
+++ xerces/c/branches/xerces-2.8/doc/migration.xml Mon Feb 25 07:46:00 2008
@@ -22,17 +22,17 @@
<s2 title="Migration Archive">
<p>For migration information to &XercesCName; 2.7.0 or earlier,
- please refer to <jump href="migrate_archive.html">Migration Archive. </jump></p>
+ please refer to <jump href="migrate_archive-&XercesC2Series;.html">Migration Archive. </jump></p>
</s2>
- <s2 title="Migrating from &XercesCName; 2.7.0 to &XercesCName; &XercesCVersion;">
+ <s2 title="Migrating from &XercesCName; 2.7.0 to &XercesCName; &XercesC2Version;">
<p>The following section is a discussion of the technical differences between
- &XercesCName; 2.7.0 code base and the &XercesCName; &XercesCVersion;.</p>
+ &XercesCName; 2.7.0 code base and the &XercesCName; &XercesC2Version;.</p>
<p>Topics discussed are:</p>
<ul>
- <li><link anchor="NewFeatures280">New features in &XercesCName; &XercesCVersion;</link></li>
+ <li><link anchor="NewFeatures280">New features in &XercesCName; &XercesC2Version;</link></li>
<li><link anchor="API280">Public API Changes</link></li>
<ul>
<li><link anchor="NewAPI280">New Public API</link></li>
@@ -42,7 +42,7 @@
</ul>
<anchor name="NewFeatures280"/>
- <s3 title="New features in &XercesCName; &XercesCVersion;">
+ <s3 title="New features in &XercesCName; &XercesC2Version;">
<ul>
<li>Exponential growth of memory block (from 16KB to 128KB) that are allocated by the DOM heap.</li>
<li>The NODE_CLONED notification is now sent to each node's user data handler when cloning the entire DOMDocument.</li>
@@ -58,7 +58,7 @@
<s3 title="Public API Changes">
<p>The following lists the public API changes between the &XercesCName;
- 2.7.0; and the &XercesCName; &XercesCVersion; releases
+ 2.7.0; and the &XercesCName; &XercesC2Version; releases
of the parser. </p>
<anchor name="NewAPI280"/>
Modified: xerces/c/branches/xerces-2.8/doc/migration_archive.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.8/doc/migration_archive.xml?rev=630884&r1=630883&r2=630884&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.8/doc/migration_archive.xml (original)
+++ xerces/c/branches/xerces-2.8/doc/migration_archive.xml Mon Feb 25 07:46:00 2008
@@ -432,7 +432,7 @@
<li>DOM Message: make use of the non-standard extension DOMImplementation::loadDOMExceptionMsg
to load the default error text message for the correspond Exception Code.</li>
<li>New feature XMLPlatformUtils::Initialize(const char* const locale) to set
- the locale for message loader. See <jump href="program-others.html#SpecifylocaleforMessageLoader">
+ the locale for message loader. See <jump href="program-others-&XercesC2Series;.html#SpecifylocaleforMessageLoader">
Specify locale for Message Loader</jump> for details</li>
<li>Support Build with ICU Message Loader, or Message Catalog Message Loader</li>
<li>RPM for Linux</li>
@@ -442,7 +442,7 @@
<li>Performance: Break Scanner for different functionalities and many other performance improvement</li>
<li>New feature, "http://apache.org/xml/features/dom/byte-order-mark", allows user to enable
DOMWriter to write Byte-Order-Mark in the output XML stream,
- See <jump href="program-dom.html#Byte-Order-Mark">
+ See <jump href="program-dom-&XercesC2Series;.html#Byte-Order-Mark">
Xercesc Feature: Byte Order Mark</jump> for details</li>
</ul>
</s3>
@@ -450,14 +450,14 @@
<anchor name="CPPNamespace220"/>
<s3 title="Using C++ Namespace">
<p>&XercesCName; 2.2.0 now supports C++ Namespace. All &XercesCName;
- classes, data and variables are defined in the &XercesCNamespace; namespace
+ classes, data and variables are defined in the &XercesC2Namespace; namespace
if C++ Namespace support is ENABLED.</p>
<p>All the binary distributions of &XercesCName; 2.2.0 are now built with
C++ Namespace enabled. Therefore users' applications that links with the distributed
binary packages must namespace qualify all the &XercesCName; classes, data and variables.</p>
- <p>See the Programming Guide <jump href="program-others.html#CPPNamespace">Using C++ Namespace</jump>
+ <p>See the Programming Guide <jump href="program-others-&XercesC2Series;.html#CPPNamespace">Using C++ Namespace</jump>
for details.</p>
</s3>
@@ -646,21 +646,21 @@
<ul>
<li>AIX</li>
<ul>
- <li>&XercesCUnixLib;&XercesCUnixSoName;.so</li>
- <li>symbolic link: &XercesCUnixLib;.so ----> &XercesCUnixLib;&XercesCUnixVersion;.so</li>
- <li>symbolic link: &XercesCUnixLib;&XercesCUnixVersion;.so ----> &XercesCUnixLib;&XercesCUnixSoName;.so</li>
+ <li>&XercesC2UnixLib;&XercesC2UnixSoName;.so</li>
+ <li>symbolic link: &XercesC2UnixLib;.so ----> &XercesC2UnixLib;&XercesC2UnixVersion;.so</li>
+ <li>symbolic link: &XercesC2UnixLib;&XercesC2UnixVersion;.so ----> &XercesC2UnixLib;&XercesC2UnixSoName;.so</li>
</ul>
<li>Solaris / Linux</li>
<ul>
- <li>&XercesCUnixLib;.so.&XercesCUnixSoName;</li>
- <li>symbolic link: &XercesCUnixLib;.so ----> &XercesCUnixLib;.so.&XercesCUnixVersion;</li>
- <li>symbolic link: &XercesCUnixLib;.so.&XercesCUnixVersion; ----> &XercesCUnixLib;.so.&XercesCUnixSoName;</li>
+ <li>&XercesC2UnixLib;.so.&XercesC2UnixSoName;</li>
+ <li>symbolic link: &XercesC2UnixLib;.so ----> &XercesC2UnixLib;.so.&XercesC2UnixVersion;</li>
+ <li>symbolic link: &XercesC2UnixLib;.so.&XercesC2UnixVersion; ----> &XercesC2UnixLib;.so.&XercesC2UnixSoName;</li>
</ul>
<li>HP-UX</li>
<ul>
- <li>&XercesCUnixLib;.sl.&XercesCUnixSoName;</li>
- <li>symbolic link: &XercesCUnixLib;.sl ----> &XercesCUnixLib;.sl.&XercesCUnixVersion;</li>
- <li>symbolic link: &XercesCUnixLib;.sl.&XercesCUnixVersion; ----> &XercesCUnixLib;.sl.&XercesCUnixSoName;</li>
+ <li>&XercesC2UnixLib;.sl.&XercesC2UnixSoName;</li>
+ <li>symbolic link: &XercesC2UnixLib;.sl ----> &XercesC2UnixLib;.sl.&XercesC2UnixVersion;</li>
+ <li>symbolic link: &XercesC2UnixLib;.sl.&XercesC2UnixVersion; ----> &XercesC2UnixLib;.sl.&XercesC2UnixSoName;</li>
</ul>
</ul>
</s3>
@@ -711,7 +711,7 @@
file is renamed as well</li>
<li>the rest is the same, see
<jump href="ApacheDOMC++Binding.html">Apache Recommended DOM C++ binding</jump>
- and <jump href="program-dom.html">DOM Programming Guide</jump> for more programming
+ and <jump href="program-dom-&XercesC2Series;.html">DOM Programming Guide</jump> for more programming
information</li>
</ul>
<p>Users of IDOM are required to change all their #include lines and do a global rename of
@@ -806,7 +806,7 @@
by targetNamespace (for Schema) or system id (for DTD).</li>
<li>Plus "Grammar Caching" has much more functionalities other than above
(like "Pre-parsing Grammar"). Please refer to
- <jump href="program-others.html#GrammarCache">Preparsing Grammar and Grammar Caching
+ <jump href="program-others-&XercesC2Series;.html#GrammarCache">Preparsing Grammar and Grammar Caching
</jump> for more programming details.</li>
</ol>
</s3>
@@ -822,7 +822,7 @@
<s4 title="New Public API">
<ul>
<li>To support DOM Level 3, the following are added (see
- <jump href="api.html">the API documentation page</jump> for details).</li>
+ <jump href="api-&XercesC2Series;.html">the API documentation page</jump> for details).</li>
<ul>
<li>DOMNode functions set/getUserData, isSameNode isEqualNode.</li>
<li>DOMDocument functions renameNode, get/setActualEncoding, get/setEncoding, get/setVersion, get/setStandalone, get/setDocumentURI.</li>
@@ -909,7 +909,7 @@
<li>The old Java-like DOM is now deprecated as described in
<link anchor="DirChange200">DOM Reorganization</link></li>
<li>SAX2XMLReader::setValidationConstraint. For consistency, SAX2XMLReader users should
- set the feature http://apache.org/xml/features/validation-error-as-fatal" instead.</li>
+ set the feature "http://apache.org/xml/features/validation-error-as-fatal" instead.</li>
<li>SAX2XMLReader::setExitOnFirstFatalError. For consistency, SAX2XMLReader users should
set the feature "http://apache.org/xml/features/continue-after-fatal-error" instead.</li>
<li>With the new Grammar Caching introduced, the following features will not be
@@ -977,7 +977,7 @@
<s4 title="New Public API">
<ul>
<li>Added SAX2-ext's DeclHandler class.
- See <jump href="api.html">the API documentation page</jump> for details.</li>
+ See <jump href="api-&XercesC2Series;.html">the API documentation page</jump> for details.</li>
<li>To support SAX2-ext's DeclHandler, the following new methods are added
in classes DefaultHandler and SAX2XMLReader:</li>
<ul>
@@ -1050,7 +1050,7 @@
<s3 title="New features in &XercesCName; 1.6.0">
<ul>
<li>Full Schema support is available in this release.
- See <jump href="schema.html">the Schema page</jump> for details.</li>
+ See <jump href="schema-&XercesC2Series;.html">the Schema page</jump> for details.</li>
<li>New sample SEnumVal to show how to enumerate the markup decls in a Schema Grammar is added.</li>
</ul>
</s3>
@@ -1138,16 +1138,13 @@
<li>New command line option "-s" for samples.</li>
</ul>
<p>
- See <jump href="schema.html">the Schema page</jump> for details.
+ See <jump href="schema-&XercesC2Series;.html">the Schema page</jump> for details.
</p>
</s4>
<s4 title="Experimental IDOM">
- <p>The experimental IDOM API is a new design of the C++ DOM API. If you would like
- to migrate from DOM to the experimental IDOM, please refer to
- <jump href="program-idom.html">
- IDOM programming guide.</jump> Please note that this experimental IDOM API is only
- a prototype and is subject to change.
+ <p>The experimental IDOM API is a new design of the C++ DOM API. Please note that
+ this experimental IDOM API is only a prototype and is subject to change.
</p>
</s4>
Modified: xerces/c/branches/xerces-2.8/doc/pparse.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.8/doc/pparse.xml?rev=630884&r1=630883&r2=630884&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.8/doc/pparse.xml (original)
+++ xerces/c/branches/xerces-2.8/doc/pparse.xml Mon Feb 25 07:46:00 2008
@@ -60,7 +60,7 @@
<em>-v=never</em> will not use any validation<br/>
<em>-v=auto</em> will validate if a DOCTYPE declaration or a schema declaration is present in the XML document</p>
<p>Here is a sample output from PParse</p>
-<source>cd &XercesCInstallDir;-linux/samples/data
+<source>cd &XercesC2InstallDir;-linux/samples/data
PParse -v=always personal.xml
personal.xml: 60 ms (37 elems, 12 attrs, 134 spaces, 134 chars)</source>
<p>Running PParse with the validating parser gives a different result because
Modified: xerces/c/branches/xerces-2.8/doc/program-deprecateddom.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.8/doc/program-deprecateddom.xml?rev=630884&r1=630883&r2=630884&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.8/doc/program-deprecateddom.xml (original)
+++ xerces/c/branches/xerces-2.8/doc/program-deprecateddom.xml Mon Feb 25 07:46:00 2008
@@ -354,7 +354,7 @@
of the features below are set using the "setter" methods (e.g. <code>setDoNamespaces</code>),
and are queried using the corresponding "getter" methods (e.g. <code>getDoNamespaces</code>).
The following only gives you a quick summary of supported features. Please
- refer to <jump href="api.html">API Documentation</jump> for complete detail.
+ refer to <jump href="api-&XercesC2Series;.html">API Documentation</jump> for complete detail.
</p>
<p>None of these features can be modified in the middle of a parse, or an exception will be thrown.</p>
@@ -637,7 +637,7 @@
fgSGXMLScanner, or fgIGXMLScanner) or a string that matches the value of
one of those constants.</td></tr>
<tr><th><em>Value Type</em></th><td> XMLCh* </td></tr>
- <tr><th><em>note: </em></th><td> See <jump href="program-others.html#UseSpecificScanner">Use Specific Scanner</jump>
+ <tr><th><em>note: </em></th><td> See <jump href="program-others-&XercesC2Series;.html#UseSpecificScanner">Use Specific Scanner</jump>
for more programming details. </td></tr>
</table>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xerces.apache.org
For additional commands, e-mail: commits-help@xerces.apache.org