|
 |
 |
 |
 |
|
Caveats and Limitations |
|
This is a list of the limitations in this release of XML4C. Encodings
- Encodings cannot be arbitrarily set programmatically, i.e. we only go by the encoding that is auto-sensed or found in encoding=""
- The following encodings are not currently supported: Chinese for PRC (mixed 1/2 byte) (gb2312), Japanese ISO-2022-JP (iso-2022-jp) and Cyrllic (koi8-r).
Validation
- Validation of notations/enumerations is not complete. For instance you can have a notation or enumeration type attribute that does not refer to the valid notations or enum values listed in the attribute type.
Miscellaneous
- SAXPrint does not output the <?XML ... ?> prologue line (this means that it cannot process its own output). This is because the SAX API doesn't provide a callback handler for the prologue.
- Only URL's of the form '
file://' are currently supported. Others will be supported in future versions.
- Error text is not translatable yet, its only in English
- There is no support for namespaces.
- There is no catalog support.
Known Defects
- DOM Entity reference nodes are modifiable. They should be read-only.
- Some James Clark tests do not pass.
- DOM Element names are not checked for comformance to XML spec for element names.
- DOM
getDocType() returns null, even if DTD is present.
- Parser configuration class is not documented.
|
|
|
|
|
Copyright (c) IBM Corp. 1999,
Center for Java Technology, Cupertino, USA |
|