"Jason E. Stewart" <[EMAIL PROTECTED]> writes:
> "Jason E. Stewart" <[EMAIL PROTECTED]> writes:
>
> > "Juergen Hermann" <[EMAIL PROTECTED]> writes:
> >
> > > On Sat, 01 Sep 2001 11:24:40 +0200, Juergen Hermann wrote:
> > >
> > > >>Two tests in oasis/ fail that should have passed:
> > > >>And two tests in oasis/ pass that should have failed:
> > > >
> > > >Well, I have 272 failures with strict checking, and that seems a little high
> > > >to me. ;)
>
> Here are the lists of tests that fail using the Xerces-P perl wrapper:
>
> ibm/valid/P02/ibm02v01.xml
> ibm/not-wf/misc/432gewf.xml
> xmltest/valid/sa/049.xml
> xmltest/valid/sa/050.xml
> xmltest/valid/sa/051.xml
> xmltest/valid/not-sa/003.xml
> xmltest/valid/ext-sa/014.xml
> sun/invalid/pe01.xml
> sun/invalid/empty.xml
> sun/valid/ext01.xml
> sun/valid/ext02.xml
> japanese/weekly-little-endian.xml
> japanese/weekly-utf-16.xml
> japanese/pr-xml-utf-16.xml
> japanese/pr-xml-little-endian.xml
After looking at Juergen's example, I realized that I wasn't running
my tests properly. I needed to be parsing the xml files given for each
suite to determine how to run the tests, for example, I could just
assume the files in the 'not-wf' were all not well formed.
So I've fixed that, and I run the tests with both a validating and
non-validating DOMParser, and this is what I see:
ibm/
==========
Validating Parser Failed file: valid/P02/ibm02v01.xml
Non-Validating Parser Failed file: valid/P02/ibm02v01.xml
REASON <<I think these are unicode problems>>
japanese
==========
Validating Parser Failed file: weekly-little-endian.xml
Validating Parser Failed file: weekly-utf-16.xml
Non-Validating Parser Failed file: weekly-little-endian.xml
Non-Validating Parser Failed file: weekly-utf-16.xml
REASON <<I think these are unicode problems>>
xmltest/
===========
Validating Parser Failed file: valid/sa/049.xml
Validating Parser Failed file: valid/sa/050.xml
Validating Parser Failed file: valid/sa/051.xml
Non-Validating Parser Failed file: valid/sa/049.xml
Non-Validating Parser Failed file: valid/sa/050.xml
Non-Validating Parser Failed file: valid/sa/051.xml
Validating Parser Failed file: valid/ext-sa/014.xml
Non-Validating Parser Failed file: valid/ext-sa/014.xml
REASON <<I think these are unicode problems>>
Validating Parser Failed file: valid/not-sa/003.xml
Non-Validating Parser Failed file: valid/not-sa/003.xml
REASON <<missing entity file>>
Validating Parser Failed file: valid/sa/094.xml
Non-Validating Parser Failed file: valid/sa/094.xml
REASON <<Documented test bug:
<!-- NOTE: jclark test bug; output test ignored too. -->
>>
oasis/
========
Validating Parser Failed file: p03fail1.xml
Non-Validating Parser Failed file: p03fail1.xml
REASON: <<a true failure, nsgmls picks this one up>>
<TEST TYPE='not-wf' SECTIONS='2.3 [3]'
ID='o-p03fail1' URI='p03fail1.xml'>
Use of illegal character within XML document. </TEST>
sun/
=========
Non-Validating Parser Failed file: invalid/utf16b.xml
Non-Validating Parser Failed file: invalid/utf16l.xml
Validating Parser Failed file: valid/ext02.xml
REASON <<I think these are unicode problems>>
Validating Parser Failed file: invalid/empty.xml
REASON: <<a true failure, nsgmls picks this one up>>
<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>
Validating Parser Failed file: valid/ext01.xml
Non-Validating Parser Failed file: valid/ext01.xml
REASON <<missing entity file>>
Totals
=======
I think that only two are true Xerces failures:
* sun/invalid/empty.xml
* oasis/not-wf/p03fail1.xml
I'll install ICU, and see if the unicode problems go away.
jas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
