You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by rd...@apache.org on 2004/08/29 20:41:25 UTC
cvs commit: jakarta-commons/digester/src/java/org/apache/commons/digester/parser package.html
rdonkin 2004/08/29 11:41:25
Modified: digester/src/java/org/apache/commons/digester/parser Tag:
RELEASE_DIGESTER_1_6_0_BRANCH package.html
Log:
Fixed typos
Revision Changes Path
No revision
No revision
1.1.6.2 +3 -3 jakarta-commons/digester/src/java/org/apache/commons/digester/parser/package.html
Index: package.html
===================================================================
RCS file: /home/cvs/jakarta-commons/digester/src/java/org/apache/commons/digester/parser/package.html,v
retrieving revision 1.1.6.1
retrieving revision 1.1.6.2
diff -u -r1.1.6.1 -r1.1.6.2
--- package.html 18 Aug 2004 19:59:28 -0000 1.1.6.1
+++ package.html 29 Aug 2004 18:41:25 -0000 1.1.6.2
@@ -23,12 +23,12 @@
<br><br>
<p>
Digester aims to support the widest range possible of parsers.
-Unfortunately, there are a few parser settings which have no been standardized.
+Unfortunately, there are a few parser settings which have not been standardized.
In most cases, the best practice is for the user to configure the parser
themselves and pass it to Digester to use.
</p>
<p>
-There are a few reasonable exceptions which Digesters makes to this general rule.
+There are a few reasonable exceptions which Digester makes to this general rule.
There are a small number of common use cases where insisting that the user
configure the parser may reduce the portability of applications using Digester.
These are outlined below.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org