kc3-lang/libxml2/result/valid/cond_sect2.xml.err.rdr
Branch
-
Show log
Commit
-
Hash : 2f3655c9
Author :
Date : 2025-05-20T19:40:06
parser: Pop PEs that start markup declarations explicitly We currently only handle "Validity constraint: Proper Declaration/PE Nesting", but we must detect "Well-formedness constraint: PE Between Declarations" separately: > The replacement text of a parameter entity reference in a DeclSep must > match the production extSubsetDecl. PEs in DeclSeps are PEs that start with a full markup declaration (or another PE). These are handled in xmParse{Internal|External}Subset. We set a flag on these PEs and don't close them implicitly in xmlSkipBlankCharsPE. This will make unterminated declarations in such PEs cause a parser error. The PEs are closed explicitly in xmParse{Internal|External}Subset, the only location where they are allowed to end.
-
result/valid/cond_sect2.xml.err.rdr
-
test/valid/dtds/cond_sect2.dtd:15: parser error : Parameter entity must match extSubsetDecl %ent; ^ Entity: line 1: ]]> ^ test/valid/dtds/cond_sect2.dtd:15: parser error : Content error in the external subset %ent; ^ Entity: line 1: ]]> ^ ./test/valid/cond_sect2.xml : failed to parse