cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 17763] - Internal DTD comments cause invalid XML
Date Mon, 10 Mar 2003 11:54:56 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17763>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17763

Internal DTD comments cause invalid XML





------- Additional Comments From bruno@outerthought.org  2003-03-10 11:54 -------
Ah, now I understand why the old behaviour changed: before the
NamespaceNormalizingDOMStreamer, an identity XSL transform was performed in the
serializer that solved this (by ignoring those events). (so the DOMStreamer had
something to do with it after all)

Like Jeff suggested, a possible solution would be adding an extra XMLPipe in the
AbstractTextSerializer that throws away all events between startDTD and endDTD
(in the same spirit as the NamespaceAsAttributes XMLPipe).

Supporting DeclHandler probably wouldn't solve this, since it would be
impossible to distinguish between the internal and external DTD subsets. AFAIU
SAX, there's no way to keep the internal DTD subset intact.

Mime
View raw message