cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruno Dumon <br...@outerthought.org>
Subject Re: DO NOT REPLY [Bug 17763] - Internal DTD comments cause invalid XML
Date Fri, 02 May 2003 13:28:11 GMT
On Fri, 2003-05-02 at 14:59, Vadim Gritsenko wrote:
> bugzilla@apache.org wrote:
> 
> >http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17763
> >
> >Internal DTD comments cause invalid XML
> >
> >bruno@outerthought.org changed:
> >
> >           What    |Removed                     |Added
> >----------------------------------------------------------------------------
> >             Status|NEW                         |RESOLVED
> >         Resolution|                            |DUPLICATE
> >
> >
> >
> >------- Additional Comments From bruno@outerthought.org  2003-05-02 12:40 -------
> >I came to the insight that this is a Xalan-bug (and meanwhile learned that in
> >SAX, you can detect whether DTD-related events come from the external or
> >internal subset)
> >
> >I reported it over there (together with patch and all), see bug 19562, so I'm
> >closing this one.
> >
> 
> But we still should extend Excalibur XML parser to have ability to 
> ignore all this stuff, right?

Yep, I've overseen this for a moment because I was focussing too much on
the case of external DTD's. In case of external DTD's, all should be
well now, the serializer will drop them anyway, but in case of internal
DTD subsets, the comments will still be serialized (but nothing else of
the internal DTD since we do not support the DeclHandler interface), so
yes, it still makes sence to simply drop all DTD comments.

I have the modified excalibur xml parser already here, I'll post it
later on.

-- 
Bruno Dumon                             http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno@outerthought.org                          bruno@apache.org


Mime
View raw message