Re: XMLC, setEnableXTHMLCompatibilty

Hi David,

At 03:43 PM 10/6/2003 -0400, you wrote:
> About a year ago, I submitted a patch which was "converted" to become the
> enableXHTMLCompatibilty of OutputOptions.  Aside from the name change, the
> functionality of the patch (always use "close tags" , rather than an implied
> close) was limited to only the SCRIPT tag.

Yes, since it is the only case that I know of where HTML allows for an 
empty or close tag *and* where IE has troubles dealing with the empty 
version.  Since either is valid XHTML, we choose the version that IE deals 
with when using enableXHTMLCompatibility(true).

> Based on my recent experiences, this is wrong.  ALL tags need to be closed
> with an explicit close tag to work in both Mozilla and IE.

Hmm....  examples please?  I hope you don't mean <br></br> and the 
like.  That is just plain invalid.  And I'm guessing you mean it won't work 
with IE but Mozilla works just fine in almost every case.  Please provide 
markup (in an html document attached in a zip file so it isn't inlined in 
the email) which doesn't work for you and explain what exactly about it 
doesn't work.

>   This may, in
> fact, be exacerbated by the fact that we're sending "Content-type:
> text/html", but that's being done because there doesn't seem to be an agreed
> upon solution for xhtml (last time I looked).

For application/xhtml+xml, use....
-domfactory org.enhydra.xml.xhtml.XHTMLDomFactory

For text/html, use....
-domfactory org.enhydra.xml.xhtml.HTMLDomFactory

Does that help?

Jake