You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by "Jason E. Stewart" <ja...@openinformatics.com> on 2001/09/05 06:17:33 UTC
XMLConf update
Hey,
so with the updated version of xmlconf (thanks Curt, for pointing that
out), the Xerces-Perl wrapper now reports 25 failures (tested using
DOM and IDOM, but not yet sax).
Notice that there are a lot of tests such as:
Test demonstrates that characters outside of normal ascii range can be
used as element content.
Seems like Xerces-C has a problem with this. Juergen, how do my
results match up with yours?
jas.
--
------------------------------------------------------------------------------
Failed Test = valid-sa-049
File = ../xmlconf/xmltest/valid/sa/049.xml
Parser = Validating Parser
Test Section: 2.2 [2]
Test Description:
Test demonstrates that characters outside of normal ascii range can be used as element content.
Error:
FATAL ERROR
FILE: /home/jasons/work/xmlconf/xmltest/valid/sa/049.xml
LINE: 1
COLUMN: 2
MESSAGE: Invalid document structure
------------------------------------------------------------------------------
Failed Test = valid-sa-049
File = ../xmlconf/xmltest/valid/sa/049.xml
Parser = Non-Validating Parser
Test Section: 2.2 [2]
Test Description:
Test demonstrates that characters outside of normal ascii range can be used as element content.
Error:
FATAL ERROR
FILE: /home/jasons/work/xmlconf/xmltest/valid/sa/049.xml
LINE: 1
COLUMN: 2
MESSAGE: Invalid document structure
------------------------------------------------------------------------------
Failed Test = valid-sa-050
File = ../xmlconf/xmltest/valid/sa/050.xml
Parser = Validating Parser
Test Section: 2.2 [2]
Test Description:
Test demonstrates that characters outside of normal ascii range can be used as element content.
Error:
FATAL ERROR
FILE: /home/jasons/work/xmlconf/xmltest/valid/sa/050.xml
LINE: 1
COLUMN: 2
MESSAGE: Invalid document structure
------------------------------------------------------------------------------
Failed Test = valid-sa-050
File = ../xmlconf/xmltest/valid/sa/050.xml
Parser = Non-Validating Parser
Test Section: 2.2 [2]
Test Description:
Test demonstrates that characters outside of normal ascii range can be used as element content.
Error:
FATAL ERROR
FILE: /home/jasons/work/xmlconf/xmltest/valid/sa/050.xml
LINE: 1
COLUMN: 2
MESSAGE: Invalid document structure
------------------------------------------------------------------------------
Failed Test = valid-sa-051
File = ../xmlconf/xmltest/valid/sa/051.xml
Parser = Validating Parser
Test Section: 2.2 [2]
Test Description:
The document is encoded in UTF-16 and uses some name
characters well outside of the normal ASCII range.
Error:
FATAL ERROR
FILE: /home/jasons/work/xmlconf/xmltest/valid/sa/051.xml
LINE: 1
COLUMN: 2
MESSAGE: Invalid document structure
------------------------------------------------------------------------------
Failed Test = valid-sa-051
File = ../xmlconf/xmltest/valid/sa/051.xml
Parser = Non-Validating Parser
Test Section: 2.2 [2]
Test Description:
The document is encoded in UTF-16 and uses some name
characters well outside of the normal ASCII range.
Error:
FATAL ERROR
FILE: /home/jasons/work/xmlconf/xmltest/valid/sa/051.xml
LINE: 1
COLUMN: 2
MESSAGE: Invalid document structure
------------------------------------------------------------------------------
Failed Test = valid-sa-094
File = ../xmlconf/xmltest/valid/sa/094.xml
Parser = Validating Parser
Test Section: 2.8
Test Description:
This refers to an undefined parameter entity reference within
a markup declaration in the internal DTD subset, violating
the WFC.
Error:
------------------------------------------------------------------------------
Failed Test = valid-sa-094
File = ../xmlconf/xmltest/valid/sa/094.xml
Parser = Non-Validating Parser
Test Section: 2.8
Test Description:
This refers to an undefined parameter entity reference within
a markup declaration in the internal DTD subset, violating
the WFC.
Error:
------------------------------------------------------------------------------
Failed Test = valid-ext-sa-014
File = ../xmlconf/xmltest/valid/ext-sa/014.xml
Parser = Validating Parser
Test Section: 4.1 4.4.3 [68]
Test Description:
Test demonstrates use of characters outside of normal ASCII range.
Error:
FATAL ERROR
FILE: /home/jasons/work/xmlconf/xmltest/valid/ext-sa/014.ent
LINE: 1
COLUMN: 3
MESSAGE: Invalid character (Unicode: 0xFFFe)
------------------------------------------------------------------------------
Failed Test = valid-ext-sa-014
File = ../xmlconf/xmltest/valid/ext-sa/014.xml
Parser = Non-Validating Parser
Test Section: 4.1 4.4.3 [68]
Test Description:
Test demonstrates use of characters outside of normal ASCII range.
Error:
FATAL ERROR
FILE: /home/jasons/work/xmlconf/xmltest/valid/ext-sa/014.ent
LINE: 1
COLUMN: 3
MESSAGE: Invalid character (Unicode: 0xFFFe)
------------------------------------------------------------------------------
Failed Test = ext02
File = ../xmlconf/sun/valid/ext02.xml
Parser = Validating Parser
Test Section: 4.3.2 [78]
Test Description:
Tests use of external parsed entities with different
encodings than the base document.
Error:
ERROR
FILE: /home/jasons/work/xmlconf/sun/invalid/utf16b.xml
LINE: 1
COLUMN: 49
MESSAGE: No character data is allowed by content model
------------------------------------------------------------------------------
Failed Test = utf16b
File = ../xmlconf/sun/invalid/utf16b.xml
Parser = Non-Validating Parser
Test Section: 4.3.3 2.8
Test Description:
Tests reading an invalid "big endian" UTF-16 document
Error:
FATAL ERROR
FILE: /home/jasons/work/xmlconf/sun/invalid/utf16b.xml
LINE: 1
COLUMN: 1
MESSAGE: Invalid document structure
------------------------------------------------------------------------------
Failed Test = utf16l
File = ../xmlconf/sun/invalid/utf16l.xml
Parser = Non-Validating Parser
Test Section: 4.3.3 2.8
Test Description:
Tests reading an invalid "little endian" UTF-16 document
Error:
FATAL ERROR
FILE: /home/jasons/work/xmlconf/sun/invalid/utf16l.xml
LINE: 1
COLUMN: 1
MESSAGE: Invalid document structure
------------------------------------------------------------------------------
Failed Test = empty
File = ../xmlconf/sun/invalid/empty.xml
Parser = Validating Parser
Test Section: 2.4 2.7 [18] 3
Test Description:
CDATA section containing only white space does not match the nonterminal S, and cannot
appear in these positions.
Error:
------------------------------------------------------------------------------
Failed Test = pe01
File = ../xmlconf/sun/invalid/pe01.xml
Parser = Validating Parser
Test Section: 2.8
Test Description:
Parameter entities must consist of a series of complete markup
declarations of the types allowed by the nonterminal
, interespersed with whitespace or PERefs.
Error:
------------------------------------------------------------------------------
Failed Test = pe01
File = ../xmlconf/sun/invalid/pe01.xml
Parser = Non-Validating Parser
Test Section: 2.8
Test Description:
Parameter entities must consist of a series of complete markup
declarations of the types allowed by the nonterminal
, interespersed with whitespace or PERefs.
Error:
------------------------------------------------------------------------------
Failed Test = uri01
File = ../xmlconf/sun/not-wf/uri01.xml
Parser = Validating Parser
Test Section: 4.2.2 [75]
Test Description:
SYSTEM ids may not have URI fragments
Error:
------------------------------------------------------------------------------
Failed Test = uri01
File = ../xmlconf/sun/not-wf/uri01.xml
Parser = Non-Validating Parser
Test Section: 4.2.2 [75]
Test Description:
SYSTEM ids may not have URI fragments
Error:
------------------------------------------------------------------------------
Failed Test = o-p03fail1
File = ../xmlconf/oasis/p03fail1.xml
Parser = Validating Parser
Test Section: 2.3 [3]
Test Description:
Use of illegal character within XML document.
Error:
------------------------------------------------------------------------------
Failed Test = o-p03fail1
File = ../xmlconf/oasis/p03fail1.xml
Parser = Non-Validating Parser
Test Section: 2.3 [3]
Test Description:
Use of illegal character within XML document.
Error:
------------------------------------------------------------------------------
Failed Test = o-p11pass1
File = ../xmlconf/oasis/p11pass1.xml
Parser = Validating Parser
Test Section: 2.3, 4.2.2 [11]
Test Description:
system literals may not contain
URI fragments
Error:
------------------------------------------------------------------------------
Failed Test = o-p11pass1
File = ../xmlconf/oasis/p11pass1.xml
Parser = Non-Validating Parser
Test Section: 2.3, 4.2.2 [11]
Test Description:
system literals may not contain
URI fragments
Error:
------------------------------------------------------------------------------
Failed Test = ibm-not-wf-P69-ibm69n05.xml
File = ../xmlconf/ibm/not-wf/P69/ibm69n05.xml
Parser = Non-Validating Parser
Test Section: 4.1
Test Description:
Based on E29 substantial source: minutes XML-Syntax 1999-02-24 E38 in
XML 1.0 Errata, this WFC does not apply to P69, but the VC Entity declared
still apply.
Tests PEReference which is against P69 WFC: Entity Declared. The PE
with the name "paaa" is referred before declared in the DTD.
Error:
FATAL ERROR
FILE: /home/jasons/work/xmlconf/ibm/not-wf/P69/ibm69n05.xml
LINE: 6
COLUMN: 7
MESSAGE: Entity 'paaa' was not found
------------------------------------------------------------------------------
Failed Test = ibm-valid-P02-ibm02v01.xml
File = ../xmlconf/ibm/valid/P02/ibm02v01.xml
Parser = Validating Parser
Test Section: 2.2
Test Description:
Tests with 3 characters - 2 boundaries plus 1 in the middle - for
each range plus #x20 #x9 #xD #xA
Error:
FATAL ERROR
FILE: /home/jasons/work/xmlconf/ibm/valid/P02/ibm02v01.xml
LINE: 14
COLUMN: 58
MESSAGE: Invalid character (Unicode: 0xDBFF)
------------------------------------------------------------------------------
Failed Test = ibm-valid-P02-ibm02v01.xml
File = ../xmlconf/ibm/valid/P02/ibm02v01.xml
Parser = Non-Validating Parser
Test Section: 2.2
Test Description:
Tests with 3 characters - 2 boundaries plus 1 in the middle - for
each range plus #x20 #x9 #xD #xA
Error:
FATAL ERROR
FILE: /home/jasons/work/xmlconf/ibm/valid/P02/ibm02v01.xml
LINE: 14
COLUMN: 58
MESSAGE: Invalid character (Unicode: 0xDBFF)
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: XMLConf update
Posted by Juergen Hermann <jh...@web.de>.
On 05 Sep 2001 22:20:39 -0600, Jason E. Stewart wrote:
>> Makes more sense to generate XML (via a "testresults.dtd" that inherits
>> "testcases.dtd") and then run it through XSLT, if you ask me.
>
>Ah... yes, this is a better idea. That means I really need to get
>XML::Xalan working though...
Let's coordinate our efforts there. Did you start on something yet? I'll do
a DTD and post it here. I guess we should move to the xmlconf list, are you
subscribed?
Ciao, Jürgen
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: XMLConf update
Posted by "Jason E. Stewart" <ja...@openinformatics.com>.
"Juergen Hermann" <jh...@web.de> writes:
> On 05 Sep 2001 08:27:22 -0600, Jason E. Stewart wrote:
>
> >You should use the patch available at:
> >
> >http://xmlconf.sourceforge.net/xml/update.sh
>
> That made one more failed test run (xmltest/valid-not-sa-003, which
> obviously missed a file), so I'm now at 26 failures.
>
> >Also, by looking at:
> >
> >http://xmlconf.sourceforge.net/xml/?selected=java
> >
> >I can see that they have made a report generator that produces
> >HTML. I'm going to steal it and convert it to perl.
>
> Makes more sense to generate XML (via a "testresults.dtd" that inherits
> "testcases.dtd") and then run it through XSLT, if you ask me.
Ah... yes, this is a better idea. That means I really need to get
XML::Xalan working though...
> BTW, do you know of any SAX2 unit tests, before I invent my own, I
> rather steal^H^H^H^H^Hget inspired by existing ones. ;)
Haven't looked into it yet.
jas.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: XMLConf update
Posted by Juergen Hermann <jh...@web.de>.
On 05 Sep 2001 08:27:22 -0600, Jason E. Stewart wrote:
>You should use the patch available at:
>
>http://xmlconf.sourceforge.net/xml/update.sh
That made one more failed test run (xmltest/valid-not-sa-003, which
obviously missed a file), so I'm now at 26 failures.
>Also, by looking at:
>
>http://xmlconf.sourceforge.net/xml/?selected=java
>
>I can see that they have made a report generator that produces
>HTML. I'm going to steal it and convert it to perl.
Makes more sense to generate XML (via a "testresults.dtd" that inherits
"testcases.dtd") and then run it through XSLT, if you ask me.
BTW, do you know of any SAX2 unit tests, before I invent my own, I
rather steal^H^H^H^H^Hget inspired by existing ones. ;)
Ciao, Jürgen
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: XMLConf update
Posted by "Jason E. Stewart" <ja...@openinformatics.com>.
"Juergen Hermann" <jh...@web.de> writes:
> On 04 Sep 2001 22:17:33 -0600, Jason E. Stewart wrote:
>
> >Seems like Xerces-C has a problem with this. Juergen, how do my
> >results match up with yours?
>
> Using a patched xmlconf-20010315, I'm at 27 errors. The first two
> add missing files, the patches to existing files make it possible to
> _validate_ the test descriptions.
Hey Juergen,
You should use the patch available at:
http://xmlconf.sourceforge.net/xml/update.sh
instead of the one you rolled yourself. It includes many other
important fixes that were accidentally introduced into the test suite
by fumbling with WinZip...
Also, by looking at:
http://xmlconf.sourceforge.net/xml/?selected=java
I can see that they have made a report generator that produces
HTML. I'm going to steal it and convert it to perl.
jas.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: XMLConf update
Posted by Juergen Hermann <jh...@web.de>.
On 04 Sep 2001 22:17:33 -0600, Jason E. Stewart wrote:
>Seems like Xerces-C has a problem with this. Juergen, how do my
>results match up with yours?
Using a patched xmlconf-20010315, I'm at 27 errors. The first two add missing files, the patches
to existing files make it possible to _validate_ the test descriptions.
Create two missing files:
touch sun/valid/empty.xml
touch sun/valid/null.ent
Then apply the following patches:
--- xmlconf/testcases.dtd Sat Sep 1 02:30:08 2001
+++ testcases.dtd Sat Sep 1 02:30:03 2001
@@ -38,6 +38,7 @@
<!ELEMENT TESTCASES (TEST|TESTCASES)*>
<!ATTLIST TESTCASES
PROFILE CDATA #IMPLIED
+ xml:base CDATA #IMPLIED
>
<!--
--- sun/sun-invalid.xml Sat Sep 1 02:33:35 2001
+++ xmlconf/sun/sun-invalid.xml Sat Sep 1 02:35:35 2001
@@ -401,6 +401,6 @@
<TEST URI="invalid/utf16l.xml" ID="utf16l" SECTIONS="4.3.3 2.8" TYPE="invalid">
Tests reading an invalid "little endian" UTF-16 document</TEST>
-<TEST URI="invalid/empty.xml" ID="sun-empty" TYPE="invalid" SECTIONS="2.4 2.7 [18] 3">
+<TEST URI="invalid/empty.xml" ID="empty" TYPE="invalid" SECTIONS="2.4 2.7 [18] 3">
CDATA section containing only white space does not match the nonterminal S, and cannot
appear in these positions. </TEST>
=====================================================================
OASIS draft v1.0 Second Edition; with 15 March updates by Mary Brady)
=====================================================================
Running this testsuite with <pirxx._pirxx.PyXMLReader object at 00812780>
Validation mode is 'yes'
--- valid-sa-094 James Clark XMLTEST cases, 18-Nov-1998 (cf. 2.8) ------------
This refers to an undefined parameter entity reference within
a markup declaration in the internal DTD subset, violating
the PEs in Internal Subset WFC.
HI No error for non-wellformed document reported
VAL xmltest\valid\sa\094.xml
--- valid-not-sa-003 James Clark XMLTEST cases, 18-Nov-1998 (cf. 4.1 [69]) ---
Test demonstrates the expansion of an external parameter entity that declares an attribute.
HI Error for valid file
VAL xmltest\valid\not-sa\003.xml
FTL xmltest\valid\not-sa\003-1.ent:3:27: An exception occured! Type:RuntimeException,
Message:Could not open external entity 'xmltest\valid\not-sa\003-2.ent'
--- sa02 Sun Microsystems XML Tests (cf. 2.9 [32]) ---------------------------
A document may be marked 'standalone' if any
attributes that need normalization are
defined within the internal DTD subset.
HI Error for valid file
VAL sun\valid\sa02.xml
FTL sun\valid\sa02.xml:41:18: Bad standalone declaration
--- sa03 Sun Microsystems XML Tests (cf. 2.9 [32]) ---------------------------
A document may be marked 'standalone' if any
the defined entities need expanding are internal,
and no attributes need defaulting or normalization.
On output, requires notations to be correctly reported.
HI Error for valid file
VAL sun\valid\sa03.xml
FTL sun\valid\sa03.xml:21:22: Bad standalone declaration
--- inv-not-sa01 Sun Microsystems XML Tests (cf. 2.9) ------------------------
Tests the Standalone Document Declaration VC, ensuring that
optional whitespace causes a validity error.
HI No error for invalid document reported
VAL sun\invalid\not-sa01.xml
--- sun-empty Sun Microsystems XML Tests (cf. 2.4 2.7 [18] 3) ----------------
CDATA section containing only white space does not match the nonterminal S, and cannot
appear in these positions.
HI No error for invalid document reported
VAL sun\invalid\empty.xml
--- o-p03fail1 OASIS/NIST TESTS, 1-Nov-1998 (cf. 2.3 [3]) --------------------
Use of illegal character within XML document.
HI No error for non-wellformed document reported
VAL oasis\p03fail1.xml
--- ibm-invalid-P32-ibm32i01.xml IBM XML Conformance Test Suite - Production 3
This test violates VC: Standalone Document Declaration in P32.
The standalone document declaration has the value yes, BUT there is an
external markup declaration of attributes with default values, and the
associated element appears in the document with specified values for those
attributes.
HI No error for invalid document reported
VAL ibm\invalid\P32\ibm32i01.xml
--- ibm-invalid-P41-ibm41i02.xml IBM XML Conformance Test Suite - Production 4
This test violates VC: Attribute Value Type in P41. attr3 for Element b is
given a value that does not match the declaration in the DTD.
HI No error for invalid document reported
VAL ibm\invalid\P41\ibm41i02.xml
WRN ibm\invalid\P41\ibm41i02.xml:8:3: Element 'PCDATA' was referenced in a content model but
never declared
--- ibm-not-wf-P85-ibm85n121.xml IBM XML Conformance Test Suite - Production 8
Tests BaseChar with an illegal character. The character #x0E31
occurs as the first character of the PITarget in the PI in the DTD.
HI No error for non-wellformed document reported
VAL ibm\not-wf\P85\ibm85n121.xml
--- ibm-not-wf-P85-ibm85n122.xml IBM XML Conformance Test Suite - Production 8
Tests BaseChar with an illegal character. The character #x0E34
occurs as the first character of the PITarget in the PI in the DTD.
HI No error for non-wellformed document reported
VAL ibm\not-wf\P85\ibm85n122.xml
--- ibm-not-wf-P85-ibm85n123.xml IBM XML Conformance Test Suite - Production 8
Tests BaseChar with an illegal character. The character #x0E46
occurs as the first character of the PITarget in the PI in the DTD.
HI No error for non-wellformed document reported
VAL ibm\not-wf\P85\ibm85n123.xml
--- ibm-not-wf-P85-ibm85n136.xml IBM XML Conformance Test Suite - Production 8
Tests BaseChar with an illegal character. The character #x0EB1
occurs as the first character of the PITarget in the PI in the DTD.
HI No error for non-wellformed document reported
VAL ibm\not-wf\P85\ibm85n136.xml
--- ibm-not-wf-P85-ibm85n137.xml IBM XML Conformance Test Suite - Production 8
Tests BaseChar with an illegal character. The character #x0EB4
occurs as the first character of the PITarget in the PI in the DTD.
HI No error for non-wellformed document reported
VAL ibm\not-wf\P85\ibm85n137.xml
--- ibm-not-wf-P85-ibm85n19.xml IBM XML Conformance Test Suite - Production 85
Tests BaseChar with an illegal character. The character #x0387
occurs as the first character of the PITarget in the PI in the DTD.
HI No error for non-wellformed document reported
VAL ibm\not-wf\P85\ibm85n19.xml
--- ibm-not-wf-P85-ibm85n45.xml IBM XML Conformance Test Suite - Production 85
Tests BaseChar with an illegal character. The character #x064B
occurs as the first character of the PITarget in the PI in the DTD.
HI No error for non-wellformed document reported
VAL ibm\not-wf\P85\ibm85n45.xml
--- ibm-not-wf-P85-ibm85n50.xml IBM XML Conformance Test Suite - Production 85
Tests BaseChar with an illegal character. The character #x06D6
occurs as the first character of the PITarget in the PI in the DTD.
HI No error for non-wellformed document reported
VAL ibm\not-wf\P85\ibm85n50.xml
--- ibm-not-wf-P85-ibm85n51.xml IBM XML Conformance Test Suite - Production 85
Tests BaseChar with an illegal character. The character #x06E7
occurs as the first character of the PITarget in the PI in the DTD.
HI No error for non-wellformed document reported
VAL ibm\not-wf\P85\ibm85n51.xml
--- ibm-not-wf-P85-ibm85n53.xml IBM XML Conformance Test Suite - Production 85
Tests BaseChar with an illegal character. The character #x093E
occurs as the first character of the PITarget in the PI in the DTD.
HI No error for non-wellformed document reported
VAL ibm\not-wf\P85\ibm85n53.xml
--- ibm-not-wf-P85-ibm85n54.xml IBM XML Conformance Test Suite - Production 85
Tests BaseChar with an illegal character. The character #x0962
occurs as the first character of the PITarget in the PI in the DTD.
HI No error for non-wellformed document reported
VAL ibm\not-wf\P85\ibm85n54.xml
--- ibm-not-wf-P85-ibm85n63.xml IBM XML Conformance Test Suite - Production 85
Tests BaseChar with an illegal character. The character #x09E2
occurs as the first character of the PITarget in the PI in the DTD.
HI No error for non-wellformed document reported
VAL ibm\not-wf\P85\ibm85n63.xml
--- ibm-not-wf-P85-ibm85n73.xml IBM XML Conformance Test Suite - Production 85
Tests BaseChar with an illegal character. The character #x0A70
occurs as the first character of the PITarget in the PI in the DTD.
HI No error for non-wellformed document reported
VAL ibm\not-wf\P85\ibm85n73.xml
--- ibm-not-wf-P85-ibm85n76.xml IBM XML Conformance Test Suite - Production 85
Tests BaseChar with an illegal character. The character #x0ABC
occurs as the first character of the PITarget in the PI in the DTD.
HI No error for non-wellformed document reported
VAL ibm\not-wf\P85\ibm85n76.xml
--- ibm-not-wf-P85-ibm85n89.xml IBM XML Conformance Test Suite - Production 85
Tests BaseChar with an illegal character. The character #x0B3E
occurs as the first character of the PITarget in the PI in the DTD.
HI No error for non-wellformed document reported
VAL ibm\not-wf\P85\ibm85n89.xml
--- ibm-not-wf-P86-ibm86n04.xml IBM XML Conformance Test Suite - Production 86
Tests Ideographic with an illegal character. The character #x302A
occurs as the first character in the PITarget in the PI in the DTD.
HI No error for non-wellformed document reported
VAL ibm\not-wf\P86\ibm86n04.xml
--- ibm-valid-P02-ibm02v01.xml IBM XML Conformance Test Suite - Production 2 (
Tests Char with 3 characters - 2 boundaries plus 1 in the middle - for
each range plus #x20 #x9 #xD #xA
HI Error for valid file
VAL ibm\valid\P02\ibm02v01.xml
FTL ibm\valid\P02\ibm02v01.xml:14:58: Invalid character (Unicode: 0xDBFF)
--- ibm-valid-P87-ibm87v01.xml IBM XML Conformance Test Suite - Production 87
This test case covers 65 legal character ranges plus 30 single legal
characters for CombiningChar in P87 using a PI target Name
HI Error for valid file
VAL ibm\valid\P87\ibm87v01.xml
FTL ibm\valid\P87\ibm87v01.xml:6:114: Unterminated processing instruction
------------------------------------------------------------------------------
Found 27 (0 LOW / 0 MED / 27 HI) conformance violations in 1820 tests.
Needed 33,368 secs to run the tests.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org