You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xerces.apache.org by tn...@apache.org on 2001/02/07 20:05:27 UTC
cvs commit: xml-xerces/c/doc/pdf xerces-c-pdf.properties
tng 01/02/07 11:05:27
Modified: c/doc build-misc.xml build-other.xml build-winunix.xml
domprint.xml faq-distrib.xml faq-other.xml
faq-parse.xml feedback.xml memparse.xml pdf-c.xml
samples.xml
c/doc/pdf xerces-c-pdf.properties
Log:
FAQ update by Khaled Noaman. Plus other documentation fixes.
Revision Changes Path
1.2 +21 -7 xml-xerces/c/doc/build-misc.xml
Index: build-misc.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/build-misc.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- build-misc.xml 2001/02/05 15:01:05 1.1
+++ build-misc.xml 2001/02/07 19:05:23 1.2
@@ -21,7 +21,7 @@
build ICU with a threaded version of the xlC compiler and
build &XercesCName; with a non-threaded one.</note>
- <p>There are two options to build Xerces-C with ICU. One is to use the
+ <p>There are two options to build &XercesCName; with ICU. One is to use the
MSDEV GUI environment, and the other is to invoke the compiler from the
command line.</p>
@@ -36,12 +36,12 @@
<li>zip.exe</li>
</ul>
- <p>Extract Xerces-C source files from the .zip archive using WinZip, say
+ <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>
<p>Extract the ICU files, using WinZip, in root directory of the disk
- where you have installed Xerces-C, sources. After extraction, there
+ where you have installed &XercesCName;, sources. After extraction, there
should be a new directory '<code>x:\icu</code>' which contains all the ICU
source files.</p>
@@ -62,7 +62,7 @@
<p>If everything is setup right and works right, then you should see a
binary drop created in the target directory specified above. This script
- will build both ICU and Xerces-C, copy the files (relevant to the binary
+ will build both ICU and &XercesCName;, copy the files (relevant to the binary
drop) to the target directory.</p>
<p>For a description of options available, you can enter:</p>
@@ -202,7 +202,7 @@
the best to follow, since that is where the main
development is done.</li>
- <li>Next, edit the file <code>XML4CDefs.hpp</code>, which is where all
+ <li>Next, edit the file <code>XercesDefs.hpp</code>, which is where all
of the fundamental stuff comes into the system. You will
see conditional sections in there where the above
per-platform and per-environment headers are brought in.
@@ -214,7 +214,7 @@
compiler. These definitions are based on known platform
and compiler defines.
<br/>
- <code>AutoSense.hpp</code> is included in <code>XML4CDefs.hpp</code> and the
+ <code>AutoSense.hpp</code> is included in <code>XercesDefs.hpp</code> and the
canonical platform and compiler settings thus defined will
make the particular platform and compiler headers to be
the included at compilation.
@@ -246,6 +246,20 @@
implementations done, you should be able to start
debugging the system using the demo programs.</li>
</ol>
+
+ <p>Other concerns are:</p>
+
+ <ul>
+ <li>Does ICU compile on your platform? If not, then you'll need to
+ create a transcoder implementation that uses your local transcoding
+ services. The Iconv transcoder should work for you, though perhaps
+ with some modifications.</li>
+ <li>What message loader will you use? To get started, you can use the
+ "in memory" one, which is very simple and easy. Then, once you get
+ going, you may want to adapt the message catalog message loader, or
+ write one of your own that uses local services.</li>
+ </ul>
+
<p>That is the work required in a nutshell!</p>
</a>
</faq>
@@ -257,7 +271,7 @@
<p>XMLCh should be defined to be a type suitable for holding a
utf-16 encoded (16 bit) value, usually an <code>unsigned short</code>. </p>
- <p>All XML data is handled within xerces-c as strings of
+ <p>All XML data is handled within &XercesCName; as strings of
XMLCh characters. Regardless of the size of the
type chosen, the data stored in variables of type XMLCh
will always be utf-16 encoded values. </p>
1.2 +4 -4 xml-xerces/c/doc/build-other.xml
Index: build-other.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/build-other.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- build-other.xml 2001/02/05 15:01:05 1.1
+++ build-other.xml 2001/02/07 19:05:23 1.2
@@ -29,7 +29,7 @@
find and edit the VAC++ configuration file <code>project_options.icc</code>.</li>
<li>Change the directory on the first line <code>'BASE_DIR = "..."'</code>
- to match the base directory of the Xerces-C sources on your system.
+ to match the base directory of the &XercesCName; sources on your system.
Note that the directory path must use double backslashes <code>"\\"</code>!</li>
<li>Save <code>project_options.icc</code></li>
@@ -123,7 +123,7 @@
<p><em>Recommendations:</em></p>
<ul>
- <li>There are a couple of options when building the XML4C parser on AS/400.
+ <li>There are a couple of options when building the &XercesCName; parser on AS/400.
For messaging support, you can use the in memory message option or the
message file support. For code page translation, you can use the AS/400
native <code>Iconv400</code> support or ICU. If you choose ICU, follow the instructions
@@ -391,8 +391,8 @@
were written. So, these instructions are not upto date.
But it will give you a jump start if you are struggling to get it
to work for the first time. We will be glad to get your changes.
- Please respond to <jump href="mailto:&XercesCEmailAddress;">
- &XercesCEmailAddress;</jump> with your comments and corrections.</note>
+ Please respond to the <jump href="mailto:&XercesCEmailAddress;">Xerces-C
+ mailing list</jump> with your comments and corrections.</note>
</s3>
</a>
1.2 +5 -5 xml-xerces/c/doc/build-winunix.xml
Index: build-winunix.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/build-winunix.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- build-winunix.xml 2001/02/05 15:01:05 1.1
+++ build-winunix.xml 2001/02/07 19:05:23 1.2
@@ -67,13 +67,13 @@
<jump href="http://oss.software.ibm.com/icu/">ICU Library</jump>
in the same directory as the &XercesCName; library. For example if
&XercesCName; is at the top level of the d drive, put the ICU
- library at the top level of d e.g. d:/xml4c, d:/icu.</li>
+ library at the top level of d e.g. d:/&XercesCInstallDir; d:/icu.</li>
</ul>
<p><em>Instructions:</em></p>
<ol>
- <li>Change the directory to d:\xml4c\Projects\Win32</li>
- <li>If a d:\xml4c\Project\Win32\VACPP40 directory does not exist, create it.</li>
+ <li>Change the directory to d:\&XercesCInstallDir;\Projects\Win32</li>
+ <li>If a d:\&XercesCInstallDir;\Project\Win32\VACPP40 directory does not exist, create it.</li>
<li>Copy the IBM VisualAge project file, <code>XML4C2X.icc</code>,
to the VACPP40 directory.</li>
<li>From the VisualAge main menu enter the project file name and path.</li>
@@ -130,7 +130,7 @@
<p>If you are not using any of these compilers, you are taking a calculated risk
by exploring new grounds. Your effort in making &XercesCName; work on this
new compiler is greatly appreciated and any problems you face can be addressed
- on the &XercesCName; <jump href="mailto:&XercesCEmailAddress;">mailing list</jump>.
+ on the <jump href="mailto:&XercesCEmailAddress;">Xerces-C mailing list</jump>.
</p>
<p><em>Differences between the UNIX platforms:</em> The description below is
@@ -293,7 +293,7 @@
configure
If the result of the above commands look OK to you, go to the directory
-XERCESCROOT and type "gmake" to make the XERCES-C system.</source>
+XERCESCROOT and type "gmake" to make the &XercesCName; system.</source>
<note>The error message concerning <code>conf.h</code>
is NOT an indication of a problem. This code has been inserted to make it
1.4 +1 -1 xml-xerces/c/doc/domprint.xml
Index: domprint.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/domprint.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- domprint.xml 2000/06/20 02:28:53 1.3
+++ domprint.xml 2001/02/07 19:05:23 1.4
@@ -37,7 +37,7 @@
<p>The following parameters may be set from the command line </p>
<source>Usage: DOMPrint [options] file
-This program invokes the Xerces-C DOM parser and builds the DOM
+This program invokes the &XercesCName; DOM parser and builds the DOM
tree. It then traverses the DOM tree and prints the contents
of the tree. Options are NOT case sensitive.
1.7 +73 -36 xml-xerces/c/doc/faq-distrib.xml
Index: faq-distrib.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/faq-distrib.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- faq-distrib.xml 2000/05/19 00:19:58 1.6
+++ faq-distrib.xml 2001/02/07 19:05:23 1.7
@@ -3,6 +3,45 @@
<faqs title="Distributing &XercesCName;">
+ <faq title="What compilers are being used on the supported platforms?">
+
+ <q>What compilers are being used on the supported platforms?</q>
+
+ <a>
+
+ <p>&XercesCProjectName; binaries has been built on the following platforms with
+ these compilers</p>
+
+ <table>
+ <tr>
+ <td><em>Operating System</em></td>
+ <td><em>Compiler</em></td>
+ </tr>
+ <tr>
+ <td>Windows NT 4.0 SP5/98</td>
+ <td>MSVC 6.0 SP3</td>
+ </tr>
+ <tr>
+ <td>Redhat Linux 6.1</td>
+ <td>egcs-2.91.66 and glibc-2.1.2-11</td>
+ </tr>
+ <tr>
+ <td>AIX 4.2.1</td>
+ <td>xlC 3.6.4</td>
+ </tr>
+ <tr>
+ <td>Solaris 2.6</td>
+ <td>CC Workshop 4.2</td>
+ </tr>
+ <tr>
+ <td>HP-UX 11.0</td>
+ <td>aCC A.03.13 with pthreads</td>
+ </tr>
+ </table>
+
+ </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>
@@ -49,7 +88,7 @@
Alphaworks Site</jump>.</p>
<p>If you are using the binaries from the <jump
- href="http://xml.apache.org/dist">Apache download
+ href="http://xml.apache.org/dist/xerces-c/">Apache download
site</jump> site, then you only need to distribute
<em>one</em> file:<br></br>
@@ -59,7 +98,7 @@
&XercesCUnixLib;.sl for HP-UX.</p>
<p>However, if you are using the XML4C binaries then in
- <em>addition</em> to the &XercesCName; library file
+ <em>addition</em> to the library file
mentioned above, you also need to ship:</p>
<ol>
@@ -126,9 +165,8 @@
them. Moreover, we have limited resources and hence cannot
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
- <jump
- href="mailto:xerces-dev@xml.apache.org">xerces-dev@xml.apache.org</jump>.
+ specific platform/environment then please send a mail to the
+ <jump href="mailto:&XercesCEmailAddress;">Xerces-C mailing list</jump>.
We can definitely use any extra help in this open source
project</p>
</a>
@@ -144,7 +182,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="http://build.html#PortingGuide">Porting
+ href="build-misc.html#faq-4">Porting
Guidelines</jump>.</p>
<p>We strongly encourage you to submit the changes that
@@ -152,8 +190,8 @@
incorporate these changes in the source code base and make
them available in the future releases.</p>
- <p>All porting changes may be sent to: <jump
- href="mailto:xerces-dev@xml.apache.org">xerces-dev@xml.apache.org</jump>
+ <p>All porting changes may be sent to the
+ <jump href="mailto:&XercesCEmailAddress;">Xerces-C mailing list</jump>
.</p>
</a>
</faq>
@@ -163,13 +201,12 @@
<q>How can I port &XercesCProjectName; to my favourite platform?</q>
<a>
<p>Some porting information is mentioned on the <jump
- href="build.html#PortingGuide">build</jump> page.</p>
+ href="build-misc.html#faq-4">build</jump> page.</p>
</a>
</faq>
-
<faq title="What application did you used to create the documentation?">
<q>What application did you used to create the documentation?</q>
<a>
@@ -180,44 +217,44 @@
It is currently available on the
<jump href="http://xml.apache.org/">Apache</jump> open source website as
<jump href="http://xml.apache.org/cocoon/index.html">Cocoon</jump>.</p>
-
- <p>The API documentation is created using
- <jump href="http://www.zib.de/Visual/software/doc++/index.html">DOC++</jump>.</p>
- </a>
- </faq>
-
- <faq title="Source code for the C++ Builder TreeViewer?">
- <q>Can I get the source code for the C++ Builder TreeViewer application?</q>
- <a>
- <p>In view of the numerous requests that we have received for
- the TreeViewer sample application (written using C++
- Builder), we have decided to make it available as an
- independent download from the IBM
- <jump href="http://www.alphaworks.ibm.com/tech/xml4c/">AlphaWorks</jump>
- portal. The archive to get from the 'Download' page is
- 'DOMSampleTreeViewer.zip'. Please note, this is provided on a
- "as-is, no support" basis. This sample works with XML4C 2.3.1
- and we have not verified if it works with XML4C 3.x releases.</p>
- <p>TreeViewer parses the XML file, using &XercesCProjectName;,
- and displays the data as a tree.</p>
+ <p>The API documentation is automatically generated using
+ <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>We welcome your additional feedback at: <
- <jump href="mailto:&XercesCEmailAddress;">&XercesCEmailAddress;</jump>></p>
</a>
-
</faq>
+
<faq title="Can I use &XercesCProjectName; in my product?">
<q>Can I use &XercesCProjectName; in my product?</q>
<a>
<p>Yes! Read the license agreement first and if you still
- have further questions, then please address them to
- <<jump
- href="mailto:&XercesCEmailAddress;">&XercesCEmailAddress;</jump>>
+ have further questions, then please address them to the
+ <jump href="mailto:&XercesCEmailAddress;">Xerces-C mailing list</jump>
.</p>
</a>
</faq>
+
+
+ <faq title="How do I uninstall &XercesCName;?">
+ <q>How do I uninstall &XercesCName;?</q>
+ <a>
+ <p>&XercesCName; only installs itself in a single directory and does not
+ set any registry entries. Thus, to uninstall, you only need to remove the
+ directory where you installed it, and all &XercesCName; related files will be
+ removed.</p>
+ </a>
+ </faq>
+ <faq title="I am getting a tar checksum error on Solaris. What's the problem?">
+ <q>I am getting a tar checksum error on Solaris. What's the problem?</q>
+ <a>
+ <p>The problem has to do with how Solaris handles long pathnames. Either use gnu
+ tar to extract the files, or try using the -i switch with Sun's native tar.
+ The -i switch is supposed to make tar ignore checksum errors.
+ </p>
+ </a>
+ </faq>
</faqs>
1.9 +27 -57 xml-xerces/c/doc/faq-other.xml
Index: faq-other.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/faq-other.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- faq-other.xml 2001/01/18 22:49:21 1.8
+++ faq-other.xml 2001/02/07 19:05:24 1.9
@@ -2,6 +2,25 @@
<!DOCTYPE faqs SYSTEM "dtd/faqs.dtd">
<faqs title="Other &XercesCName; Questions">
+ <faq title="How do I determine the version of &XercesCName; I am using?">
+ <q>How do I determine the version of &XercesCName; I am using?</q>
+ <a>
+
+ <p>The version string for &XercesCName; is in one of the header files. Look
+ inside the file <code>src/util/XercesDefs.hpp</code> or, in the binary distribution, look in <code>include/utils/XercesDefs.hpp</code>. Search for the static variable <code>gXercesFullVersionStr</code> and look at its definition. (It is usually a string like "1_4_0" or
+ something similar). This is the version of &XercesCName; you are using.</p>
+
+ <p>If you don't have the header files, you have to find the version
+ information from the shared library name. On Windows NT/95/98 right click on
+ the DLL name &XercesCWindowsLib;.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;.a (or
+ &XercesCUnixLib;.so on Solaris/Linux and &XercesCUnixLib;.sl on HP-UX). The
+ version number is coded in the name of the library.</p>
+ </a>
+ </faq>
+
<faq title="I can't use C++. Do you have a Java version?">
<q>I can't use C++. Do you have a Java version?</q>
@@ -16,20 +35,7 @@
</a>
</faq>
- <faq title="What are the differences between &XercesCName; and IBM XML4C?">
-
- <q>What are the differences between &XercesCName; and IBM XML4C?</q>
-
- <a>
-
- <p>XML4C from IBM is based on the &XercesCName; code. The only difference
- between &XercesCName; and XML4C is that XML4C is bundled with IBM's ICU classes
- for Unicode support, which allows it to support a wider range of character set
- encodings.</p>
- </a>
- </faq>
-
<faq title="Where can I find additional information on XML?">
<q>Where can I find additional information on XML?</q>
@@ -43,44 +49,10 @@
</a>
</faq>
-
- <faq title="How do I port &XercesCName; to a new platform?">
-
- <q>How do I port &XercesCName; to a new platform?</q>
-
- <a>
-
- <p>(from Dean Roddey)</p>
-
- <p>The primary work of a port involves:</p>
-
- <ol>
- <li>Creating a new compiler header for the compiler.</li>
- <li>Creating a new platform utilities file that implements the little bit
- of system access we need, and an associated header.</li>
- <li>Updating <code>XercesDefs.hpp</code> and <code>AutoSense.hpp</code> to include your new headers when compiled under your OS and
- compiler.</li>
- </ol>
-
- <p>Other concerns are:</p>
-
- <ul>
- <li>Does ICU compile on your platform? If not, then you'll need to create
- a transcoder implementation that uses your local transcoding services. The
- Iconv transcoder should work for you, though perhaps with some
- modifications.</li>
- <li>What message loader will you use? To get started, you can use the "in
- memory" one, which is very simple and easy. Then, once you get going, you may
- want to adapt the message catalog message loader, or write one of your own that
- uses local services.</li>
- </ul>
-
- </a>
- </faq>
- <faq title="Is there any kind of support available for &XercesCName;/XML4C?">
+ <faq title="Is there any kind of support available for &XercesCName;?">
- <q>Is there any kind of support available for &XercesCName;/XML4C?</q>
+ <q>Is there any kind of support available for &XercesCName;?</q>
<a>
@@ -100,9 +72,6 @@
<jump href="http://archive.covalent.net">http://archive.covalent.net</jump>
</p>
- <p>IBM also maintains a newsgroup for discussion of XML4C. The news server
- is "news.alphaworks.ibm.com" and the group is "XML-for-C++".</p>
-
</a>
</faq>
@@ -113,16 +82,16 @@
<a>
<p>Check the bug list at the
- <jump href="http://xml.apache.org/xerces-c/index.html">Apache &XercesCName; Web
+ <jump href="http://xml.apache.org/xerces-c/index.html">Apache Xerces-C Web
site</jump>. The problem may already be known, or even fixed. </p>
- <p>Otherwise, send the bugs to either the xerces-c-dev mailing list
- (preferred) or the IBM Alphaworks news group, as described above. The more
+ <p>Otherwise, send the bugs to the <jump href="mailto:&XercesCEmailAddress;">
+ Xerces-C mailing list</jump>. The more
information that you provide, the better our chance of understanding what
happened, or what the problem really is. Please include:</p>
<ul>
- <li>The version of &XercesCName; or XML4C</li>
+ <li>The version of &XercesCName;</li>
<li>What kind of machine</li>
<li>Operating system and OS version number</li>
<li>Whether you built the &XercesCName; library yourself or used the
@@ -141,7 +110,8 @@
<a>
- <p>Mail it to the xerces-c-dev mailing list at Apache. (You must be a
+ <p>Mail it to the <jump href="mailto:&XercesCEmailAddress;">Xerces-C
+ mailing list</jump> at Apache. (You must be a
subscriber to post to this list. But if you're considering changing the code
you really want to be a subscriber, in any case.) There are no set rules about
how or what must be included -- if you've fixed a problem or enhanced the code
1.20 +53 -105 xml-xerces/c/doc/faq-parse.xml
Index: faq-parse.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/faq-parse.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- faq-parse.xml 2000/12/01 02:19:35 1.19
+++ faq-parse.xml 2001/02/07 19:05:24 1.20
@@ -43,49 +43,6 @@
</a>
</faq>
- <faq title="What compilers are being used on the supported platforms?">
-
- <q>What compilers are being used on the supported platforms?</q>
-
- <a>
-
- <p>&XercesCProjectName; has been built on the following platforms with
- these compilers</p>
-
- <table>
- <tr>
- <td><em>Operating System</em></td>
- <td><em>Compiler</em></td>
- </tr>
- <tr>
- <td>Windows NT 4.0 SP5/98</td>
- <td>MSVC 6.0 SP3</td>
- </tr>
- <tr>
- <td>Redhat Linux 6.1</td>
- <td>egcs-2.91.66 and glibc-2.1.2-11</td>
- </tr>
- <tr>
- <td>AIX 4.2.1 and higher</td>
- <td>xlC 3.6.4</td>
- </tr>
- <tr>
- <td>Solaris 2.6</td>
- <td>CC Workshop 4.2</td>
- </tr>
- <tr>
- <td>HP-UX 10.2</td>
- <td>CC A.10.36</td>
- </tr>
- <tr>
- <td>HP-UX 11.0</td>
- <td>aCC A.03.13 with pthreads</td>
- </tr>
- </table>
-
- </a>
- </faq>
-
<faq title="I cannot run the sample applications. What is wrong?">
<q>I cannot run the sample applications. What is wrong?</q>
@@ -230,7 +187,7 @@
<p>For most applications, the use of <code>Terminate()</code> is optional. The system will recover all memory when the application
process shuts down. The exception to this is the use of &XercesCName; from DLLs
that will be repeatedly loaded and unloaded from within the same process. To
- avoid memory leaks with this kind of use, <code>Terminate()</code> must be called before unloading the xerces-c library</p>
+ avoid memory leaks with this kind of use, <code>Terminate()</code> must be called before unloading the &XercesCName; library</p>
</a>
</faq>
@@ -293,8 +250,8 @@
<a>
<p>On Solaris there are a few things that need to be done before you
- execute your application using &XercesCName; / XML4C. In case you're using the
- binary build of &XercesCName; / XML4C make sure that the OS and compiler are
+ execute your application using &XercesCName;. In case 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. Different OS and
compiler versions might cause unresolved linking problems or compilation
errors. If the versions are different, rebuild the &XercesCName; library on
@@ -308,42 +265,7 @@
</a>
</faq>
- <faq title="How do I determine the version of &XercesCName; I am using?">
-
- <q>How do I determine the version of &XercesCName; I am using?</q>
-
- <a>
-
- <p>The version string for &XercesCName; is in one of the header files. Look
- inside the file <code>src/util/XercesDefs.hpp</code> or, in the binary distribution, look in <code>include/utils/XercesDefs.hpp</code>. Search for the static variable <code>gXercesFullVersionStr</code> and look at its definition. (It is usually a string like "1_4_0" or
- something similar). This is the version of &XercesCName; you are using.</p>
-
- <p>If you don't have the header files, you have to find the version
- information from the shared library name. On Windows NT/95/98 right click on
- the DLL name &XercesCWindowsLib;.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;.a (or
- &XercesCUnixLib;.so on Solaris/Linux and &XercesCUnixLib;.sl on HP-UX). The
- version number is coded in the name of the library.</p>
-
- </a>
- </faq>
-
- <faq title="How do I uninstall &XercesCName;?">
- <q>How do I uninstall &XercesCName;?</q>
-
- <a>
-
- <p>&XercesCName; only installs itself in a single directory and does not
- set any registry entries. Thus, to uninstall, you only need to remove the
- directory where you installed it, and all &XercesCName; related files will be
- removed.</p>
-
- </a>
- </faq>
-
<faq title="How are entity reference nodes handled in DOM?">
<q>How are entity reference nodes handled in DOM?</q>
@@ -426,15 +348,15 @@
<p>Most commonly, the XML <code>encoding =</code> declaration is either incorrect or missing. Without a declaration, XML
defaults to the use utf-8 character encoding, which is not compatible with the
default text file encoding on most systems.</p>
-
+
<p>The XML declaration should look something like this:</p>
-
+
<p><code><?xml version="1.0" encoding="iso-8859-1"?></code></p>
-
+
<p>Make sure to specify the encoding that is actually used by file. The
encoding for "plain" text files depends both on the operating system and the
locale (country and language) in use.</p>
-
+
<p>Another common source of problems is that some characters are not
allowed in XML documents, according to the XML spec. Typical disallowed
characters are control characters, even if you escape them using the Character
@@ -445,20 +367,20 @@
</a>
</faq>
- <faq title="What encodings are supported by &XercesCName; / XML4C?">
+ <faq title="What encodings are supported by Xerces-C / XML4C?">
- <q>What encodings are supported by &XercesCName; / XML4C?</q>
+ <q>What encodings are supported by Xerces-C / XML4C?</q>
<a>
- <p>&XercesCName; has intrinsic support for ASCII, UTF-8, UTF-16 (Big/Small
+ <p>Xerces-C has intrinsic support for ASCII, UTF-8, UTF-16 (Big/Small
Endian), UCS4 (Big/Small Endian), EBCDIC code pages IBM037 and IBM1140
encodings, ISO-8859-1 (aka Latin1) and Windows-1252. This means that it can
parse input XML files in these above mentioned encodings.</p>
-
- <p>XML4C -- the version of &XercesCName; available from IBM -- extends this
+
+ <p>XML4C -- the version of Xerces-C available from IBM -- extends this
set to include the encodings listed in the table below.</p>
-
+
<table>
<tr>
<td><em>Common Name</em></td>
@@ -533,8 +455,8 @@
<td>euc-kr</td>
</tr>
</table>
-
- <p>Some implementations or ports of &XercesCName; provide support for
+
+ <p>Some implementations or ports of Xerces-C provide support for
additional encodings. The exact set will depend on the supplier of the parser
and on the character set transcoding services in use.</p>
@@ -550,7 +472,7 @@
<p>The best choice in most cases is either utf-8 or utf-16. Advantages of
these encodings include:</p>
-
+
<ul>
<li>The best portability. These encodings are more widely supported by
XML processors than any others, meaning that your documents will have the best
@@ -563,22 +485,22 @@
more efficient for encoding Asian languages. But both encodings cover all
languages without loss.</li>
</ul>
-
+
<p>The only drawback of utf-8 or utf-16 is that they are not the native
text file format for most systems, meaning that common text file editors and
viewers can not be directly used.</p>
-
+
<p>A second choice of encoding would be any of the others listed in the
table above. This works best when the xml encoding is the same as the default
system encoding on the machine where the XML document is being prepared,
because the document will then display correctly as a plain text file. For UNIX
systems in countries speaking Western European languages, the encoding will
usually be iso-8859-1.</p>
-
+
<p>The versions of Xerces distributed by IBM, both C and Java (known
respectively as XML4C and XML4J), include all of the encodings listed in the
above table, on all platforms.</p>
-
+
<p>A word of caution for Windows users: The default character set on
Windows systems is windows-1252, not iso-8859-1. While &XercesCName; does
recognize this Windows encoding, it is a poor choice for portable XML data
@@ -591,16 +513,16 @@
</faq>
<faq
- title="I find memory leaks in &XercesCName; / XML4C. How do I eliminate it?">
+ title="I find memory leaks in &XercesCName;. How do I eliminate it?">
- <q>I find memory leaks in &XercesCName; / XML4C. How do I eliminate it?</q>
+ <q>I find memory leaks in &XercesCName;. How do I eliminate it?</q>
<a>
<p>The "leaks" that are reported through a leak-detector or heap-analysis
tools aren't really leaks in most application, in that the memory usage does
not grow over time as the XML parser is used and re-used.</p>
-
+
<p>What you are seeing as leaks are actually lazily evaluated data
allocated into static variables. This data gets released when the application
ends. You can make a call to <code>XMLPlatformUtil::terminate()</code> to release all the lazily allocated variables before you exit your
@@ -619,21 +541,47 @@
data, the preferred encoding is ibm1140. Also supported is ibm037 (and its
alternate name, ebcdic-cp-us); this encoding is almost the same as ibm1140, but
it lacks the Euro symbol.</p>
-
+
<p>These two encodings, ibm1140 and ibm037, are available on both
- &XercesCName; and IBM XML4C, on all platforms.</p>
-
+ Xerces-C and IBM XML4C, on all platforms.</p>
+
<p>On IBM System 390, XML4C also supports two alternative forms,
ibm037-s390 and ibm1140-s390. These are similar to the base ibm037 and ibm1140
encodings, but with alternate mappings of the EBCDIC new-line character, which
allows them to appear as normal text files on System 390s. These encodings are
not supported on other platforms, and should not be used for portable data.</p>
-
+
<p>XML4C on System 390 and AS/400 also provides additional EBCDIC
encodings, including those for the character sets of different countries. The
exact set supported will be platform dependent, and these encodings are not
recommended for portable XML data.</p>
+ </a>
+ </faq>
+
+ <faq title="How to write out a DOM tree into an XML file?">
+ <q>How to write out a DOM tree into an XML file?</q>
+ <a>
+ <p>This feature is not yet availabe in the parser. Take a look at the DOMPrint sample
+ for an example on parsing XML file, then writing it out back to the screen. You
+ can use that code.</p>
+ </a>
+ </faq>
+
+ <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>No. XMLPlatformUtils::Initialize() can only be called once per process. Call
+ Initialize() when you start and Terminate() when you end.</p>
+ </a>
+ </faq>
+
+ <faq title="Why does deleting a transcoded string result in assertion on windows?">
+ <q>Why does deleting a transcoded string result in assertion on windows?</q>
+ <a>
+ <p>You are mixing runtimes in your process. If you build your program with debug, link
+ to the debug version of the parser. If you build your program for release, link to
+ the release version of the parser.</p>
</a>
</faq>
1.13 +3 -2 xml-xerces/c/doc/feedback.xml
Index: feedback.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/feedback.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- feedback.xml 2001/01/19 16:41:44 1.12
+++ feedback.xml 2001/02/07 19:05:24 1.13
@@ -10,8 +10,7 @@
not covered here - who may I contact?</jump>". Browsing this
documentation, may be the quickest way to get an answer. Of course, if
all else fails, as mentioned in the link above, you can post a question
- to the <jump href="mailto:xerces-c-dev@xml.apache.org">Xerces-C-dev
- mailing list</jump>.</p>
+ to the <jump href="mailto:&XercesCEmailAddress;">Xerces-C mailing list</jump>.</p>
<p>If you are reporting a defect (greatly appreciated!), please provide
the following information:</p>
@@ -75,6 +74,7 @@
<li>Andy Levine</li>
<li>Jeff Lewis</li>
<li>Sean MacRoibeaird</li>
+ <li>Jordan Naftolin</li>
<li>Tinny Ng</li>
<li>David Nickerson</li>
<li>Khaled Noaman</li>
@@ -96,6 +96,7 @@
<li>Rick J. Stevens</li>
<li>Linda M. Swan</li>
<li>Pieter Van-Dyck</li>
+ <li>Curtis Walker</li>
<li>Tom Watson</li>
<li>Roger Webster</li>
<li>Robert Weir</li>
1.5 +1 -1 xml-xerces/c/doc/memparse.xml
Index: memparse.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/memparse.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- memparse.xml 2000/06/20 02:28:53 1.4
+++ memparse.xml 2001/02/07 19:05:24 1.5
@@ -50,7 +50,7 @@
]>
<company>
- <product>&XercesCName;</product>
+ <product>XML4C</product>
<category idea='great'>XML Parsing Tools</category>
<developedAt>
IBM Center for Java Technology, Silicon Valley, Cupertino, CA
1.3 +1 -1 xml-xerces/c/doc/pdf-c.xml
Index: pdf-c.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/pdf-c.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- pdf-c.xml 2001/02/05 17:02:56 1.2
+++ pdf-c.xml 2001/02/07 19:05:24 1.3
@@ -8,6 +8,6 @@
printing and offline reference.</p>
<note>A word of caution! The tools to create the PDF documentation are still experimental.
So the resulting PDF document is not perfect. We would be glad to receive your comments on
- <jump href="mailto:xerces-c-dev@xml.apache.org">&XercesCName; mailing list</jump>.</note>
+ the <jump href="mailto:&XercesCEmailAddress;">Xerces-C mailing list</jump>.</note>
</s2>
</s1>
1.7 +1 -1 xml-xerces/c/doc/samples.xml
Index: samples.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/samples.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- samples.xml 2000/07/06 00:53:28 1.6
+++ samples.xml 2001/02/07 19:05:24 1.7
@@ -36,7 +36,7 @@
<s2 title="Building the Samples for OS2">
- <p>Building the Xerces-C samples using IBM Visual Age C++ Professional 4.0
+ <p>Building the &XercesCName; samples using IBM Visual Age C++ Professional 4.0
for OS/2 (VAC++).</p>
<ul>
1.2 +1 -1 xml-xerces/c/doc/pdf/xerces-c-pdf.properties
Index: xerces-c-pdf.properties
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/pdf/xerces-c-pdf.properties,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- xerces-c-pdf.properties 2001/02/05 15:10:21 1.1
+++ xerces-c-pdf.properties 2001/02/07 19:05:26 1.2
@@ -9,7 +9,7 @@
BOOK_SOURCE_INPUT=doc/xerces-c_book.xml
-STYLESHEET=doc/pdf/apachePdfStyle.xsl
+STYLESHEET=doc/pdf/apachePDFStyle.xsl
PDF_OUTPUT=doc/pdf/xerces-c.pdf