You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xerces.apache.org by ne...@apache.org on 2001/06/21 21:28:27 UTC
cvs commit: xml-xerces/java/docs faq-general.xml releases.xml schema.xml
neilg 01/06/21 12:28:26
Modified: java/docs faq-general.xml releases.xml schema.xml
Log:
documentation updates
Revision Changes Path
1.13 +11 -0 xml-xerces/java/docs/faq-general.xml
Index: faq-general.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/faq-general.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- faq-general.xml 2001/05/16 17:54:36 1.12
+++ faq-general.xml 2001/06/21 19:28:21 1.13
@@ -125,6 +125,13 @@
<faq title="International Encodings">
<q>What international encodings are supported by &javaparsername;?</q>
<a>
+ <p> In general, the parser supports all IANA encodings and
+ aliases (see
+ <jump href="http://www.iana.org/assignments/character-sets">
+ http://www.iana.org/assignments/character-sets</jump>) that
+ have clear mappings to Java encodings (see
+ <jump href="http://java.sun.com/j2se/1.3.0/docs/guide/intl/encoding.doc.html">here</jump>
+ for details). Some of the more common encodings are:</p>
<ul>
<li>UTF-8</li>
<li>UTF-16 Big Endian, UTF-16 Little Endian</li>
@@ -174,6 +181,10 @@
<li>EBCDIC Arabic (ebcdic-cp-ar1)</li>
</ul>
</ul>
+ <p> Please also look at the documentation for the feature
+ "http://apache.org/xml/features/allow-java-encodings"
+ which provides a mechanism for using the
+ encoding names recognized directly by Java.</p>
</a>
</faq>
1.58 +3 -0 xml-xerces/java/docs/releases.xml
Index: releases.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/releases.xml,v
retrieving revision 1.57
retrieving revision 1.58
diff -u -r1.57 -r1.58
--- releases.xml 2001/06/21 13:24:12 1.57
+++ releases.xml 2001/06/21 19:28:23 1.58
@@ -4,6 +4,9 @@
<s1 title="Releases">
<s2 title='June 22, 2001 (version 1.4.1)'>
<ul>
+ <li> Added support for all IANA encoding aliases which have a clear mapping to
+ encodings recognized by Java [Neil Graham]</li>
+ <li> Performance improvements for DTD validation [Sandy Gao, Neil Graham]</li>
<li>Bug fixes [Sandy Gao, Neil Graham, Elena Litani, Lisa Martin, Henry Zongaro] </li>
<li>Added support for setAttribute/getAttribute in JAXP [Edwin Goei]</li>
</ul>
1.23 +13 -0 xml-xerces/java/docs/schema.xml
Index: schema.xml
===================================================================
RCS file: /home/cvs/xml-xerces/java/docs/schema.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- schema.xml 2001/06/21 13:26:29 1.22
+++ schema.xml 2001/06/21 19:28:23 1.23
@@ -26,6 +26,19 @@
<li>No interface is provided for exposing the post-schema
validation infoset , beyond
that provided by DOM or SAX;</li>
+ <li> The parser permits situations in which there is
+ circular importing; that is, where there
+ is a series of schemas which contain <import>
+ information items whose effect is
+ recursive. However, the parser only permits forward
+ references--that is, references directed from the
+ direction of the schema cited in the instance
+ document to other schemas. For instance, if schema A
+ imports schema B which also imports schema A, and an
+ instance document validates against schema A, then
+ any reference in schema b to an information item from
+ schema A will produce an error. Circular
+ <include>s have similar limitations.</li>
<li> length, minLength, and maxLength facets are limited to the value
2147483647. Items larger than this limit will not be validated
correctly.</li>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-cvs-help@xml.apache.org