cargilld 2004/09/27 20:13:57
Modified: c/doc bug-report.xml build-winunix.xml faq-build.xml
faq-other.xml feedback.xml install.xml pdf-c.xml
releases.xml schema.xml xerces-c_book.xml
c/doc/html ApacheDOMC++Binding.html
ApacheDOMC++BindingL2.html
ApacheDOMC++BindingL3.html
c/doc/html/apiDocs XercesApi.css
c/doc/style/dtd entities.ent
Log:
Documentation organization update to improve maintenance between release. Fix from
James Littlejohn.
Revision Changes Path
1.13 +1 -60 xml-xerces/c/doc/bug-report.xml
Index: bug-report.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/bug-report.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- bug-report.xml 21 Sep 2004 21:51:54 -0000 1.12
+++ bug-report.xml 28 Sep 2004 03:13:56 -0000 1.13
@@ -19,65 +19,6 @@
<s1 title="Bug Reporting">
- <s2 title="How to report bugs">
- <p> Please report bugs to <jump
href="http://nagoya.apache.org/jira";>Jira</jump>,
- the Apache bug database. Pick the product "Xerces-C++"
- using the following components:
- </p>
- <table>
- <tr><th><em>Component</em></th><th><em>Description</em></th></tr>
- <tr><td>DOM</td><td>Items specific to DOM</td></tr>
- <tr><td>SAX/SAX2</td><td>Items specific to SAX or SAX2</td></tr>
- <tr><td>Non-Validating Parser</td><td>General Parsing Problem</td></tr>
- <tr><td>Validating Parser (DTD)</td><td>DTD related parser
issue</td></tr>
- <tr><td>Validating Parser (Schema)</td><td>Schema related parser
issue</td></tr>
- <tr><td>Utilities</td><td>Items related to utilities like
MessageLoader, Transcoder, NetAccessors, Platform specific utilities</td></tr>
- <tr><td>Build</td><td>Problem with build, makefile, project
files</td></tr>
- <tr><td>Documentation</td><td>Documentation bugs such as FAQ,
Programming Guide</td></tr>
- <tr><td>Samples/Tests</td><td>Samples or test cases related
issues</td></tr>
- <tr><td>Miscellaneous</td><td>Items not covered in other
categories</td></tr>
- </table>
- <p>A copy of your bug report is sent automatically to the discussion list
- <jump href="mailto:&XercesCEmailAddress;";>&XercesCName; mailing
list</jump>.
- </p>
- </s2>
-
- <s2 title="Search first">
- <p> Check the <jump href="http://nagoya.apache.org/jira";>Jira</jump>
database
- before submitting your bug report to avoid creating a duplicate report.
- Even the bug has been reported already, you may add a comment to the
existing report
- since your contribution may lead to a quicker identification/resolution
to the bug reported.
- </p>
- <p> Here is the list of
- <jump href=
-
"http://nagoya.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=10510&statusIds=1";>
- outstanding bugs</jump> that are currently reported in Jira.
- </p>
- </s2>
+ &bug-report;
- <s2 title="Write good bug report">
- <p> Writing a useful bug report, which makes the bug reproducible, is the
first step
- towards the resolution of the bug. Specifics about the bug, like
- </p>
- <ul>
- <li>&XercesCName; version number</li>
- <li>Platform</li>
- <li>Operating system and version number</li>
- <li>Compiler and version number</li>
- <li>The XML document (or excerpt) that failed</li>
- <li>The C++ application code that failed</li>
- <li>Whether you built the &XercesCName; library yourself or used the
- binary distribution</li>
- <li>What happened</li>
- </ul>
- <p>
- are all necessary information to allow developer to reproduce,
- identify, evaluate and eventually, fix the bug, which is the very
- purpose of your reporting of the bug.
- </p>
- <p>If you are providing a patch please review the information in
- <jump href="faq-contributing.html#Submitting Patches">Submitting
Patches</jump>.
- </p>
-
- </s2>
</s1>
1.34 +3 -55 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.33
retrieving revision 1.34
diff -u -r1.33 -r1.34
--- build-winunix.xml 27 Sep 2004 13:43:44 -0000 1.33
+++ build-winunix.xml 28 Sep 2004 03:13:56 -0000 1.34
@@ -203,62 +203,10 @@
compilers we have tested &XercesCName; on. The following table lists the
relevant platforms and compilers.</p>
- <table>
- <tr>
- <th><em>Operating System</em></th>
- <th><em>Compiler</em></th>
- </tr>
- <tr>
- <th><em>32-bit binary</em></th>
- <td></td>
- </tr>
- <tr>
- <td>Redhat Linux 7.2</td>
- <td>Intel C++ Compiler v6, icc</td>
- </tr>
- <tr>
- <td>AIX 5.1</td>
- <td>xlC_r 5.0.2</td>
- </tr>
- <tr>
- <td>Solaris 2.7</td>
- <td>Forte C++ Version 6 Update 2</td>
- </tr>
- <tr>
- <td>HP-UX 11.0</td>
- <td>aCC A.03.13 with pthreads</td>
- </tr>
- <tr>
- <td>SuSE Linux 7.2 (S390)</td>
- <td>g++ 2.95</td>
- </tr>
- <tr>
- <th><em>64-bit binary</em></th>
- <td></td>
- </tr>
- <tr>
- <td>Redhat Linux 7.2, IA64</td>
- <td>Intel C++ Compiler v6, ecc</td>
- </tr>
- <tr>
- <td>AIX 5.1</td>
- <td>xlC_r 5.0.2</td>
- </tr>
- <tr>
- <td>Solaris 2.7</td>
- <td>Forte C++ Version 6 Update 2</td>
- </tr>
- <tr>
- <td>HP-UX 11.0</td>
- <td>aCC A.03.13 with pthreads</td>
- </tr>
- </table>
+ &build-winunix-supported-platforms;
- <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 <jump href="mailto:&XercesCEmailAddress;";>&XercesCName; mailing
list</jump>.
- </p>
+ <!-- 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
1.22 +2 -5 xml-xerces/c/doc/faq-build.xml
Index: faq-build.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/faq-build.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- faq-build.xml 21 Sep 2004 21:51:54 -0000 1.21
+++ faq-build.xml 28 Sep 2004 03:13:56 -0000 1.22
@@ -120,9 +120,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 (please refer to
- <jump href="faq-distrib.html#faq-1">FAQ: What platforms / compilers are
- being used to build the binary distribution kits?</jump>). Different
OS and
+ the same version as the ones used to build the binary
&faq-build-faq-distrib1;. 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
@@ -376,8 +374,7 @@
<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, (for exact name
- see <jump href="faq-distrib.html#faq-3">FAQ: Which DLL's do I need to
distribute with my application?</jump>)
+ 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.
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
1.21 +4 -43 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.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- faq-other.xml 8 Sep 2004 18:55:00 -0000 1.20
+++ faq-other.xml 28 Sep 2004 03:13:56 -0000 1.21
@@ -105,31 +105,8 @@
</a>
</faq>
- <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's up to you. Before
you
- join these lists, you should look over the resources in the Reference
Library
- section</p>
-
- <p>Instructions for subscribing are at
- <jump
-
href="http://xml.apache.org/mail.html";>http://xml.apache.org/mail.html</jump>.
- Archives of the lists are available from
- <jump href="http://marc.theaimsgroup.com/?l=xerces-c-dev";>
- http://marc.theaimsgroup.com/?l=xerces-c-dev</jump>
- </p>
-
- </a>
- </faq>
+ <!-- see entities.ent for the content for faq-other-support -->
+ &faq-other-support;
<faq title="I found a defect -- how do I report it?">
@@ -143,24 +120,8 @@
</a>
</faq>
- <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="mailto:&XercesCEmailAddress;";>&XercesCName;
- mailing list</jump>. There are no set rules about
- how or what must be included -- if you've 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
- CVS is good, along with some kind of description of what the change is.
- (Working with the current sources is important!)</p>
-
- </a>
- </faq>
+ <!-- see entities.ent for the content for faq-other-patch -->
+ &faq-other-patch;
<faq title="Where can I get predefined character entity definitions?">
1.33 +1 -9 xml-xerces/c/doc/feedback.xml
Index: feedback.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/feedback.xml,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- feedback.xml 8 Sep 2004 18:55:00 -0000 1.32
+++ feedback.xml 28 Sep 2004 03:13:56 -0000 1.33
@@ -20,16 +20,8 @@
<s1 title="Feedback Procedures">
<s2 title="Questions or Comments">
- <p>Please browse through this bundled documentation completely. Most of
- the common questions have been answered in the FAQ's. Specifically, do
- read the answer to "<jump href="faq-other.html#faq-4"> Is there any kind
- of support available for &XercesCName;?</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:&XercesCEmailAddress;";>&XercesCName; mailing
list</jump>.</p>
+ &feedback-bug-report;
- <p>See <jump href="bug-report.html">Bug Reporting</jump> if you would like
- to report a defect (greatly appreciated!).</p>
</s2>
1.13 +2 -4 xml-xerces/c/doc/install.xml
Index: install.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/install.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- install.xml 8 Sep 2004 18:55:00 -0000 1.12
+++ install.xml 28 Sep 2004 03:13:56 -0000 1.13
@@ -79,8 +79,7 @@
<p>This creates a '&XercesCSrcInstallDir;' sub-directory
containing the &XercesCName; source distribution. </p>
- <note>On Solaris, please use <code>gtar</code> instead of tar. See
- <jump href="faq-distrib.html#faq-11">FAQ</jump> for more information.</note>
+ <note>On Solaris, please use <code>gtar</code> instead of tar.
&install-faq-distrib11;</note>
<p>If you need to build the &XercesCName; source after installation,
please follow the <jump href="build.html">Build Instructions</jump>.</p>
@@ -97,8 +96,7 @@
<p>This will create an '&XercesCInstallDir;-linux' sub-directory
containing the &XercesCName; binary distribution. </p>
- <note>On Solaris, please use <code>gtar</code> instead of tar. See
- <jump href="faq-distrib.html#faq-11">FAQ</jump> for more information.</note>
+ <note>On Solaris, please use <code>gtar</code> instead of tar.
&install-faq-distrib11;</note>
<p>You will need to add the
&XercesCInstallDir;-linux/bin directory to your PATH environment
variable:</p>
1.8 +1 -2 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.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- pdf-c.xml 8 Sep 2004 18:55:00 -0000 1.7
+++ pdf-c.xml 28 Sep 2004 03:13:56 -0000 1.8
@@ -24,7 +24,6 @@
<jump
href="http://xml.apache.org/xerces-c/pdf/xerces-c.pdf.tar.gz";>xerces-c.pdf.tar.gz</jump>),
for
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
- the <jump href="mailto:&XercesCEmailAddress;";>&XercesCName; mailing
list</jump>.</note>
+ So the resulting PDF document is not perfect.</note>
</s2>
</s1>
1.100 +4 -11 xml-xerces/c/doc/releases.xml
Index: releases.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/releases.xml,v
retrieving revision 1.99
retrieving revision 1.100
diff -u -r1.99 -r1.100
--- releases.xml 8 Sep 2004 18:54:59 -0000 1.99
+++ releases.xml 28 Sep 2004 03:13:56 -0000 1.100
@@ -19,12 +19,7 @@
<s1 title="Releases">
-<s2 title="Releases Plan">
-
- <p> For future release plan about &XercesCName;,
- please refer to <jump href="releases_plan.html">Releases Plan</jump>.
- </p>
-</s2>
+&releases-releases-plan;
<s2 title="Releases Archive">
@@ -33,12 +28,10 @@
</p>
</s2>
-<s2 title="Release Information of &XercesCName; &XercesCVersion;: Feb. 16, 2004">
+<s2 title="Release Information of &XercesCName; &XercesCVersion;">
+
+&releases-fixed-bugs-para;
-<p> Here is the list of <jump href=
-"http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfield=resolution&chfieldfrom=02%2F07%2F03&chfieldto=05%2F23%2F03&chfieldvalue=fixed&product=Xerces-C%2B%2B&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&newqueryname=&order=bugs.bug_id";>
-fixed bugzilla bugs</jump> that are resolved in this release, &XercesCName;
&XercesCVersion;.
-</p>
<table>
<tr>
1.22 +3 -6 xml-xerces/c/doc/schema.xml
Index: schema.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/schema.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- schema.xml 8 Sep 2004 18:54:59 -0000 1.21
+++ schema.xml 28 Sep 2004 03:13:56 -0000 1.22
@@ -27,12 +27,9 @@
We consider this implementation complete except for the
limitations cited below.
</p>
- <p>We would very much appreciate feedback on the package via the
&XercesCName; mailing list
- <jump href="mailto:&XercesCEmailAddress;";>&XercesCEmailAddress;
</jump>, and we
- encourage the submission of bugs as described in
- <jump href="bug-report.html">Bug-Reporting</jump> page.
- Please read this document before using this package.
- </p>
+ &schema-feedback-info;
+
+
</s2>
<anchor name="limitation"/>
<s2 title="Limitations">
1.33 +12 -8 xml-xerces/c/doc/xerces-c_book.xml
Index: xerces-c_book.xml
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/xerces-c_book.xml,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- xerces-c_book.xml 21 Sep 2004 21:51:54 -0000 1.32
+++ xerces-c_book.xml 28 Sep 2004 03:13:56 -0000 1.33
@@ -17,20 +17,23 @@
<!DOCTYPE book SYSTEM "sbk:/style/dtd/book.dtd">
-<book title="&XercesCName; Documentation" copyright="2003 The Apache Software
Foundation">
- <external href="../index.html" label="Home"/>
+<book title="&XercesCName; Documentation" copyright="1999-2004 The Apache Software
Foundation">
+
+ &home;
+
<separator/>
<document id="index" label="Readme" source="readme.xml"/>
<document id="releases" label="Release Info" source="releases.xml"/>
<hidden id="releases_archive" source="releases_archive.xml"/>
- <hidden id="releases_plan" source="releases_plan.xml"/>
+ &releases_plan;
+
<separator/>
<document id="install" label="Installation" source="install.xml"/>
- <external href="http://&XercesDistDir;/"; label="Download"/>
+ <external href="http://&XercesDistDir;"; label="Download"/>
<document id="build" label="Build Instructions" source="build.xml"/>
<hidden id="build-winunix" source="build-winunix.xml"/>
<hidden id="build-other" source="build-other.xml"/>
@@ -39,11 +42,11 @@
<separator/>
<group id="faqs" label="FAQs">
- <entry id="faq-distrib" source="faq-distrib.xml"/>
+ &faq-distrib;
<entry id="faq-build" source="faq-build.xml"/>
<entry id="faq-parse" source="faq-parse.xml"/>
<entry id="faq-other" source="faq-other.xml"/>
- <entry id="faq-contributing" source="faq-contributing.xml"/>
+ &faq-contributing;
</group>
<document id="samples" label="Samples" source="samples.xml"/>
@@ -89,6 +92,7 @@
<separator/>
- <external href="http://xml.apache.org/websrc/cvsweb.cgi/xml-xerces/c/";
label="CVS Repository"/>
- <external href="http://marc.theaimsgroup.com/?l=xerces-c-dev";
label="Mail Archive"/>
+ &cvs_repository;
+ &mail_archive;
+
</book>
1.6 +4 -2 xml-xerces/c/doc/html/ApacheDOMC++Binding.html
Index: ApacheDOMC++Binding.html
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/html/ApacheDOMC++Binding.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- ApacheDOMC++Binding.html 16 Aug 2002 19:57:21 -0000 1.5
+++ ApacheDOMC++Binding.html 28 Sep 2004 03:13:57 -0000 1.6
@@ -49,8 +49,10 @@
<br>
<table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="620" >
<tr ALIGN=LEFT VALIGN=TOP>
-<td ALIGN=CENTER><i><font color="#0086B2"><font size=-1>Copyright ©
-2001 The Apache Software Foundation. All Rights Reserved.</font></font></i></td>
+<td ALIGN=CENTER><i><font color="#0086B2">
+<font size=-1>
+Copyright © 1999-2004 The Apache Software Foundation. All Rights Reserved.
+</font></font></i></td>
</tr>
</table>
</div>
1.9 +5 -2 xml-xerces/c/doc/html/ApacheDOMC++BindingL2.html
Index: ApacheDOMC++BindingL2.html
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/html/ApacheDOMC++BindingL2.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- ApacheDOMC++BindingL2.html 5 Feb 2003 22:13:02 -0000 1.8
+++ ApacheDOMC++BindingL2.html 28 Sep 2004 03:13:57 -0000 1.9
@@ -3364,8 +3364,11 @@
<table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="620" >
<tr ALIGN=LEFT VALIGN=TOP>
-<td ALIGN=CENTER><i><font color="#0086B2"><font size=-1>Copyright ©
-2001 The Apache Software Foundation. All Rights Reserved.</font></font></i></td>
+<td ALIGN=CENTER><i><font color="#0086B2">
+<font size=-1>
+Copyright © 1999-2004 The Apache Software Foundation. All Rights Reserved.
+</font>
+</font></i></td>
</tr>
</table>
</div>
1.18 +7 -2 xml-xerces/c/doc/html/ApacheDOMC++BindingL3.html
Index: ApacheDOMC++BindingL3.html
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/html/ApacheDOMC++BindingL3.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- ApacheDOMC++BindingL3.html 20 Aug 2003 11:31:22 -0000 1.17
+++ ApacheDOMC++BindingL3.html 28 Sep 2004 03:13:57 -0000 1.18
@@ -5015,8 +5015,13 @@
<table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="620" >
<tr ALIGN=LEFT VALIGN=TOP>
-<td ALIGN=CENTER><i><font color="#0086B2"><font size=-1>Copyright ©
-2001 The Apache Software Foundation. All Rights Reserved.</font></font></i></td>
+<td ALIGN=CENTER><i><font color="#0086B2">
+<font size=-1>
+Copyright © 1999-2004 The Apache Software Foundation. All Rights Reserved.
+</font>
+</font>
+</i>
+</td>
</tr>
</table>
</div>
1.3 +1 -1 xml-xerces/c/doc/html/apiDocs/XercesApi.css
Index: XercesApi.css
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/html/apiDocs/XercesApi.css,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- XercesApi.css 23 Jun 2000 21:52:00 -0000 1.2
+++ XercesApi.css 28 Sep 2004 03:13:57 -0000 1.3
@@ -8,7 +8,7 @@
DL.el { margin-left: -1cm }
DIV.fragment { width: 100%; border: none; background-color: #eeeeee }
DIV.in { margin-left: 16 }
-DIV.ah { background-color: black; margin-bottom: 3; margin-top: 3 }
+DIV.ah { background-color: #ffffff; margin-bottom: 3; margin-top: 3 }
TD.md { background-color: #f2f2ff }
DIV.groupHeader { margin-left: 16; margin-top: 12; margin-bottom: 6; font-weight:
bold }
DIV.groupText { margin-left: 16; font-style: italic; font-size: smaller }
1.12 +229 -7 xml-xerces/c/doc/style/dtd/entities.ent
Index: entities.ent
===================================================================
RCS file: /home/cvs/xml-xerces/c/doc/style/dtd/entities.ent,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- entities.ent 13 Feb 2004 17:59:37 -0000 1.11
+++ entities.ent 28 Sep 2004 03:13:57 -0000 1.12
@@ -2,17 +2,239 @@
<!ENTITY XercesCFullName "Xerces C++ Parser"> <!-- fullproductname
-->
<!ENTITY XercesCName "Xerces-C++"> <!-- productname -->
-<!ENTITY XercesCVersion "2.5.0"> <!-- versionnumber -->
+<!ENTITY XercesCVersion "2.6.0"> <!-- versionnumber -->
<!ENTITY XercesCVersion152 "1.5.2"> <!-- versionnumber -->
<!ENTITY XercesCProjectName "Xerces"> <!-- projectname -->
-<!ENTITY XercesCInstallDir "xerces-c2_5_0"> <!-- installdirname
-->
-<!ENTITY XercesCSrcInstallDir "xerces-c-src2_5_0"> <!-- sourcedirectory
-->
+<!ENTITY XercesCInstallDir "xerces-c2_6_0"> <!-- installdirname
-->
+<!ENTITY XercesCSrcInstallDir "xerces-c-src2_6_0"> <!-- sourcedirectory
-->
<!ENTITY XercesCWindowsLib "xerces-c_2"> <!-- windowslibname
-->
-<!ENTITY XercesCWindowsDLL "xerces-c_2_5_0"> <!-- windowsDLLname
-->
-<!ENTITY XercesCUnixSoName "25.0"> <!-- unixlibname -->
-<!ENTITY XercesCUnixVersion "25"> <!-- unixlibname -->
+<!ENTITY XercesCWindowsDLL "xerces-c_2_6_0"> <!-- windowsDLLname
-->
+<!ENTITY XercesCUnixSoName "26.0"> <!-- unixlibname -->
+<!ENTITY XercesCUnixVersion "26"> <!-- unixlibname -->
<!ENTITY XercesCUnixLib "libxerces-c"> <!-- unixlibname -->
<!ENTITY XercesCNamespace "xercesc"> <!-- C++ namespace
name -->
-<!ENTITY XercesCNSVersion "xercesc_2_5"> <!-- C++ namespace
name with Version -->
+<!ENTITY XercesCNSVersion "xercesc_2_6"> <!-- C++ namespace
name with Version -->
<!ENTITY XercesCEmailAddress "[EMAIL PROTECTED] "> <!-- emailaddress -->
<!ENTITY XercesDistDir "xml.apache.org/xerces-c/download.cgi"> <!-- download
directory -->
+
+<!ENTITY colon ":">
+<!ENTITY percent "%">
+
+<!-- value for home entity in xerces-c_book.xml -->
+<!ENTITY home '
+<external href="../index.html" label="Home"/>
+'>
+
+<!-- value for releases_plan entity in xerces-c_book.xml -->
+<!ENTITY releases_plan '
+<hidden id="releases_plan" source="releases_plan.xml"/>
+'>
+
+<!-- value for faq-distrib entity in xerces-c_book.xml -->
+<!ENTITY faq-distrib '
+<entry id="faq-distrib" source="faq-distrib.xml"/>
+'>
+
+<!-- value for faq-contributing entity in xerces-c_book.xml -->
+<!ENTITY faq-contributing '
+<entry id="faq-contributing" source="faq-contributing.xml"/>
+'>
+
+<!-- value for cvs_repository entity in xerces-c_book.xml -->
+<!ENTITY cvs_repository '
+<external href="http://xml.apache.org/websrc/cvsweb.cgi/xml-xerces/c/"
label="CVS Repository"/>
+'>
+
+<!-- value for mail_archive entity in xerces-c_book.xml -->
+<!ENTITY mail_archive '
+<external href="http://marc.theaimsgroup.com/?l=xerces-c-dev" label="Mail
Archive"/>
+'>
+
+<!-- Entity for bug report information used in bug-report.xml -->
+<!ENTITY bug-report '
+<s2 title="How to report bugs">
+<p> Please report bugs to <jump
href="http://nagoya.apache.org/jira">Jira</jump>,
+the Apache bug database. Pick the product "Xerces-C++"
+using the following components:
+</p>
+<table>
+<tr><th><em>Component</em></th><th><em>Description</em></th></tr>
+<tr><td>DOM</td><td>Items specific to DOM</td></tr>
+<tr><td>SAX/SAX2</td><td>Items specific to SAX or SAX2</td></tr>
+<tr><td>Non-Validating Parser</td><td>General Parsing Problem</td></tr>
+<tr><td>Validating Parser (DTD)</td><td>DTD related parser issue</td></tr>
+<tr><td>Validating Parser (Schema)</td><td>Schema related parser issue</td></tr>
+<tr><td>Utilities</td><td>Items related to utilities like MessageLoader,
Transcoder, NetAccessors, Platform specific utilities</td></tr>
+<tr><td>Build</td><td>Problem with build, makefile, project files</td></tr>
+<tr><td>Documentation</td><td>Documentation bugs such as FAQ, Programming
Guide</td></tr>
+<tr><td>Samples/Tests</td><td>Samples or test cases related issues</td></tr>
+<tr><td>Miscellaneous</td><td>Items not covered in other categories</td></tr>
+</table>
+<p>A copy of your bug report is sent automatically to the discussion list
+<jump href="mailto:&XercesCEmailAddress;">&XercesCName; mailing list</jump>.
+</p>
+</s2>
+<s2 title="Search first">
+<p> Check the <jump href="http://nagoya.apache.org/jira">Jira</jump> database
+before submitting your bug report to avoid creating a duplicate report.
+Even the bug has been reported already, you may add a comment to the existing report
+since your contribution may lead to a quicker identification/resolution to the bug
reported.
+</p>
+<p> Here is the list of
+<jump href=
+"http://nagoya.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=10510&statusIds=1">
+outstanding bugs</jump> that are currently reported in Jira.
+</p>
+</s2>
+<s2 title="Write good bug report">
+<p> Writing a useful bug report, which makes the bug reproducible, is the first step
+towards the resolution of the bug. Specifics about the bug, like
+</p>
+<ul>
+<li>&XercesCName; version number</li>
+<li>Platform</li>
+<li>Operating system and version number</li>
+<li>Compiler and version number</li>
+<li>The XML document (or excerpt) that failed</li>
+<li>The C++ application code that failed</li>
+<li>Whether you built the &XercesCName; library yourself or used the
+binary distribution</li>
+<li>What happened</li>
+</ul>
+<p>
+are all necessary information to allow developer to reproduce,
+identify, evaluate and eventually, fix the bug, which is the very
+purpose of your reporting of the bug.
+</p>
+<p>If you are providing a patch please review the information in
+<jump href="faq-contributing.html#Submitting Patches">Submitting Patches</jump>.
+</p>
+</s2>
+'>
+
+<!-- build-winunix.xml supported platforms -->
+<!ENTITY build-winunix-supported-platforms '
+<table>
+<tr><th><em>Operating System</em></th><th><em>Compiler</em></th></tr>
+<tr><th><em>32-bit binary</em></th><td></td></tr>
+<tr><td>Redhat Linux 7.2</td><td>Intel C++ Compiler v6, icc</td></tr>
+<tr><td>AIX 5.1</td><td>xlC_r 5.0.2</td></tr>
+<tr><td>Solaris 2.7</td><td>Forte C++ Version 6 Update 2</td></tr>
+<tr><td>HP-UX 11.0</td><td>aCC A.03.13 with pthreads</td></tr>
+<tr><td>SuSE Linux 7.2 (S390)</td><td>g++ 2.95</td></tr>
+<tr><th><em>64-bit binary</em></th><td></td></tr>
+<tr><td>Redhat Linux 7.2, IA64</td><td>Intel C++ Compiler v6, ecc</td></tr>
+<tr><td>AIX 5.1</td><td>xlC_r 5.0.2</td></tr>
+<tr><td>Solaris 2.7</td><td>Forte C++ Version 6 Update 2</td></tr>
+<tr><td>HP-UX 11.0</td><td>aCC A.03.13 with pthreads</td></tr>
+</table>
+'>
+
+<!-- note in build-winunix.xml about building on untested platforms -->
+<!ENTITY build-winunix-note '
+<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 <jump href="mailto:&XercesCEmailAddress;">&XercesCName; mailing
list</jump>.
+</p>
+'>
+
+<!-- support faq info for faq-other.xml -->
+<!ENTITY 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 are at
+<jump
href="http://xml.apache.org/mail.html">http://xml.apache.org/mail.html</jump>.
+Archives of the lists are available from
+<jump href="http://marc.theaimsgroup.com/?l=xerces-c-dev">
+http://marc.theaimsgroup.com/?l=xerces-c-dev</jump>
+</p>
+</a>
+</faq>
+'>
+
+<!-- patch faq info for faq-other.xml -->
+<!ENTITY 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="mailto:&XercesCEmailAddress;">&XercesCName;
+mailing list</jump>. 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
+CVS is good, along with some kind of description of what the change is.
+(Working with the current sources is important!)</p>
+</a>
+</faq>
+'>
+
+<!-- note with link to faq-distrib in faq-build.xml -->
+<!ENTITY faq-build-faq-distrib1 '
+(please refer to
+<jump href="faq-distrib.html#faq-1">FAQ: What platforms / compilers are
+being used to build the binary distribution kits?</jump>)
+'>
+
+<!ENTITY faq-build-faq-distrib3 '
+(for exact name
+see <jump href="faq-distrib.html#faq-3">FAQ: Which DLLs do I need to
distribute with my application?</jump>)
+'>
+
+<!-- note with link to faq-distrib in install.xml per solaris and gtar -->
+<!ENTITY install-faq-distrib11 '
+See
+<jump href="faq-distrib.html#faq-11">FAQ</jump> for more information.
+'>
+
+<!-- note with link to releases-plan in releases.xml -->
+<!ENTITY releases-releases-plan '
+<s2 title="Releases Plan">
+<p> For future release plan about &XercesCName;,
+please refer to <jump href="releases_plan.html">Releases Plan</jump>.
+</p>
+</s2>
+'>
+
+<!-- paragraph in releases.xml with table of bugzilla bugs fixed -->
+<!ENTITY releases-fixed-bugs-para '
+<p>Here is the list of <jump href=
+"http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfield=resolution&chfieldfrom=02&percent;2F07&percent;2F03&chfieldto=05&percent;2F23&percent;2F03&chfieldvalue=fixed&product=Xerces-C&percent;2B&percent;2B&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&newqueryname=&order=bugs.bug_id">
+fixed bugzilla bugs</jump> that are resolved in this release, &XercesCName;
&XercesCVersion;.
+</p>
+'>
+
+<!-- feedback info in schema.xml -->
+<!ENTITY schema-feedback-info '
+<p>We would very much appreciate feedback on the package via the &XercesCName;
mailing list
+<jump href="mailto:&XercesCEmailAddress;">&XercesCEmailAddress; </jump>, and
we
+encourage the submission of bugs as described on our
+<jump href="bug-report.html">Bug-Reporting</jump> page.
+Please read this document before using this package.
+</p>
+'>
+
+
+<!-- bug report / contact info in feedback.xml -->
+<!ENTITY feedback-bug-report '
+<p>Please browse through this bundled documentation completely. Most of
+the common questions have been answered in the FAQs. Specifically, do
+read the answer to "<jump href="faq-other.html#faq-4"> Is there any kind
+of support available for &XercesCName;?</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:&XercesCEmailAddress;">&XercesCName; mailing
list</jump>.</p>
+<p>See <jump href="bug-report.html">Bug Reporting</jump> if you would like
+to report a defect (greatly appreciated!).</p>
+'>
+
+
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
