File: disable

package info (click to toggle)
libxmlada 25.0.0-4
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 11,212 kB
  • sloc: ada: 78,068; sh: 3,310; makefile: 394; xml: 111; python: 39
file content (163 lines) | stat: -rw-r--r-- 3,621 bytes parent folder | download | duplicates (7)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
-------------------------------------------------------------------------------
--  NI TESTS (tests relying on features that are not implemented in XML/Ada) --
-------------------------------------------------------------------------------

rmt-e2e-15h
rmt-e2e-15g
rmt-e2e-15d
rmt-e2e-15c
rmt-e2e-15b
rmt-e2e-15a
   --  These tests require support of DOCTYPE validation, which
   --  XML/Ada does not provide

attr07
rmt-e3e-06g
rmt-e3e-06h
   --  enums

ibm-invalid-P56-ibm56i10.xml
ibm-invalid-P56-ibm56i08.xml
ibm-invalid-P56-ibm56i06.xml
ibm-invalid-P56-ibm56i02.xml
id09
id08
   --  ids and idrefs

id03
   --  one ide per elemenet

id02
   --  id is unique

ibm-valid-P28-ibm28v02.xml
ibm-valid-P29-ibm29v01.xml
ibm-valid-P29-ibm29v02.xml
   --  Comparing the XML output of these tests requires partial output
   --  of the DOCTYPE, whereas other tests don't. Not sure why exactly.

el01
el03
el05
inv-dtd03
optional01
optional02
optional03
optional04
optional05
optional06
optional07
optional08
optional09
optional10
optional11
optional12
optional13
optional14
optional20
optional21
optional22
optional23
optional24
optional25
rmt-e2e-2a
rmt-e2e-34
rmt-e2e-55
   --  These tests have invalid content model

ibm-invalid-P60-ibm60i03.xml
ibm-invalid-P59-ibm59i01.xml
ibm-invalid-P51-ibm51i03.xml
ibm-invalid-P45-ibm45i01.xml
ibm-invalid-P39-ibm39i04.xml
ibm-invalid-P39-ibm39i03.xml
ibm-invalid-P39-ibm39i02.xml
ibm-invalid-P39-ibm39i01.xml
ibm-invalid-P32-ibm32i04.xml
ibm-invalid-P32-ibm32i03.xml
ibm-invalid-P32-ibm32i01.xml
inv-not-sa12
inv-not-sa11
inv-not-sa10
inv-not-sa09
inv-not-sa07
inv-not-sa06
inv-not-sa05
inv-not-sa04
inv-not-sa01
   --  standalone

empty
   --  whitespace

o-p75pass1
o-p74pass1
   --  missing element decl

attr04
attr03
   --  notations must be declared

invalid-not-sa-022
   --  conditional section

el06
el02
   --  Empty element

attr16
attr15
   --  default attribute value

inv-not-sa14
   --  CDATA as whitespace

el04
inv-dtd01
   --  duplicate element decl

rmt-ns10-045
rmt-ns10-046
   --  Requires validating parser with DTD: when an attribute is of type ID,
   --  its value must not  include ":"

invalid-bo-1
invalid-bo-2
invalid-bo-3
invalid-bo-4
invalid-bo-5
invalid-bo-6
   --  Validating tests related to Byte-Order-Mark: the byte order mark should
   --  go away in a general entity. Not clear how the test is checking that,
   --  but XML/Ada is not a DTD-validating parser in any case

------------------------------------------------------------------
-- N/A TESTS (tests that are wrong, disputed or not applicable) --
------------------------------------------------------------------

ibm-invalid-P50-ibm50i01.xml
ibm-not-wf-p28a-ibm28an01.xml
not-wf-not-sa-009
not-wf-sa-074
not-wf-sa-104
not-wf-sa-182
rmt-ns10-033
   --  These tests are apparently wrong, given the errata E14
   --  http://www.w3.org/XML/xml-V10-2e-errata

rmt-e3e-13
   --  This test is incorrect: ent2 is indeed not defined (perhaps they meant
   --  ent1), as confirmed by Xerces and xmllint

invalid-sa-140
invalid-sa-141
   --  The test (for XML 1.0 Fifth Edition) is expected to be invalid, but
   --  reported as valid by Xerces, xmllint and XML/Ada. The comment for this
   --  indicates this is "legal", so the expected output of the test seems
   --  incorrect here.

invalid-bo-9
   --  One BOM and part of another result in an invalid character, as expected.
   --  However, the testsuite says this should be a non-fatal error, when in
   --  fact an invalid character really is a fatal error. They might be
   --  expecting some special handling of multiple partial BOM here