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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
