You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xerces.apache.org by mr...@apache.org on 2005/06/18 20:22:59 UTC
cvs commit: xml-xerces/java/docs faq-contributing.xml faq-dom.xml readme.xml samples-xni.xml faq-grammars.xml
mrglavas 2005/06/18 11:22:59
Modified: java/docs faq-contributing.xml faq-dom.xml readme.xml
samples-xni.xml faq-grammars.xml
Log:
Minor documentation improvements.
Revision Changes Path
1.8 +1 -1 xml-xerces/java/docs/faq-contributing.xml
Index: faq-contributing.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/faq-contributing.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- faq-contributing.xml 18 Apr 2005 03:42:52 -0000 1.7
+++ faq-contributing.xml 18 Jun 2005 18:22:59 -0000 1.8
@@ -100,7 +100,7 @@
(tags for releases usually have the form Xerces-J_x_y_z
where x.y.z is the Xerces-J release number)
You should also tag the current branch of xml-commons
- containing the API's that the parser needs to conform
+ containing the APIs that the parser needs to conform
to; see step 1 above.
</li>
<li>Do a test build and regression test run;
1.18 +2 -2 xml-xerces/java/docs/faq-dom.xml
Index: faq-dom.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/faq-dom.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- faq-dom.xml 17 Jun 2005 15:23:10 -0000 1.17
+++ faq-dom.xml 18 Jun 2005 18:22:59 -0000 1.18
@@ -189,7 +189,7 @@
<faq title="Accessing the DOM Level 3 API">
<q>How do I access the DOM Level 3 functionality?</q>
<a> <anchor name="dom3"/>
- <p>The DOM Level 3 functionality is now exposed by default since Xerces-2J 2.7.0</p>
+ <p>The DOM Level 3 functionality is now exposed by default since Xerces-J 2.7.0</p>
<p>For more information, refer to the <link idref='dom3'>DOM Level 3
Implementation</link> page.
</p>
@@ -201,7 +201,7 @@
<a> <anchor name="dom3-run"/>
<p>Use the <jump href="http://java.sun.com/j2se/1.4/docs/guide/standards/">
Endorsed Standards Override Mechanism</jump> to specify xercesImpl.jar and xml-apis.jar.
- More complete description is available <jump href="http://xml.apache.org/xalan-j/faq.html#faq-N100CB">here</jump>.
+ More complete description is available <jump href="http://xml.apache.org/xalan-j/faq.html#faq-N100CC">here</jump>.
</p>
</a>
</faq>
1.54 +3 -3 xml-xerces/java/docs/readme.xml
Index: readme.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/readme.xml,v
retrieving revision 1.53
retrieving revision 1.54
diff -u -r1.53 -r1.54
--- readme.xml 17 Jun 2005 19:00:47 -0000 1.53
+++ readme.xml 18 Jun 2005 18:22:59 -0000 1.54
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='UTF-8'?>
<!--
- * Copyright 1999-2004 The Apache Software Foundation.
+ * Copyright 1999-2005 The Apache Software Foundation.
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
@@ -48,7 +48,7 @@
</p>
- <p>Xerces2 is now able to parse documents written according to the
+ <p>Xerces2 is able to parse documents written according to the
<jump href="http://www.w3.org/TR/2004/REC-xml11-20040204/">
XML 1.1 Recommendation</jump>, except that
it does not yet provide an option to enable normalization checking as described
@@ -57,7 +57,7 @@
<jump href="http://www.w3.org/TR/2004/REC-xml-names11-20040204/">
XML Namespaces 1.1 Recommendation</jump>,
and will correctly serialize XML 1.1 documents if the DOM level
- 3 load/save API's are in use.
+ 3 load/save APIs are in use.
</p>
</s2>
1.9 +2 -2 xml-xerces/java/docs/samples-xni.xml
Index: samples-xni.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/samples-xni.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- samples-xni.xml 25 Feb 2004 16:22:44 -0000 1.8
+++ samples-xni.xml 18 Jun 2005 18:22:59 -0000 1.9
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='UTF-8'?>
<!--
- * Copyright 2001-2004 The Apache Software Foundation.
+ * Copyright 2001-2005 The Apache Software Foundation.
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
@@ -468,7 +468,7 @@
<p> The third step can be quite time-consuming, especially if you
have a lot of jars on your classpath and run applications which
require the creation of lots of parsers. If you know you're
- only using applications which require "standard" API's (that
+ only using applications which require "standard" APIs (that
is, don't need some special Xerces property), or you want to
try and force applications to use only certain Xerces
configurations, then you may wish to copy this file into your
1.14 +2 -2 xml-xerces/java/docs/faq-grammars.xml
Index: faq-grammars.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/faq-grammars.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- faq-grammars.xml 9 Mar 2004 23:21:06 -0000 1.13
+++ faq-grammars.xml 18 Jun 2005 18:22:59 -0000 1.14
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='UTF-8'?>
<!--
- * Copyright 2002-2004 The Apache Software Foundation.
+ * Copyright 2002-2005 The Apache Software Foundation.
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
@@ -319,7 +319,7 @@
</p>
</a>
</faq>
- <faq title="Grammar caching with Standard API's">
+ <faq title="Grammar caching with Standard APIs">
<q>All right, I've (somehow) got a grammar pool full of
grammars. How do I use this with my application that uses
standard (SAX|DOM|JAXP) parsers?</q>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xerces.apache.org
For additional commands, e-mail: commits-help@xerces.apache.org