Re: [xmlc] <br clear="none"></br>

Jacob Kjome wrote:
> Comparisons of lower-case tags to the upper-case special handling 
> categories never match, which is why <br> is not recognized as a tag 
> with an empty content model.  "br" is being matched against "BR" (in a 
> Map or a Set, so no opportunity for equalsIgnoreCase() unless code is 
> modified), which clearly doesn't match.

> I'm not 100% sure this is worth it?  If one has chosen to use the XHTML 
> DOM and taken care to write valid XHTML documents, why would they want 
> to output it as HTML?  One answer might be "so that developers can write 
> markup that validates in their editors, but be able to output basic HTML 
> to less capable user-agents that only understand HTML and foul up on 
> XHTML".  This is certainly a legitimate use-case.  I'm still not sure 
> whether it's worth the effort, especially when I put so much effort into 
> allowing HTML to be formatted as XHTML in the XMLFormatter.
>
> Comments?

I can imagine that someone created all the pages of their project in 
nice clean XHTML and then realized that the user-agent used by majority 
of their users still unfortunately doesn't handle xhtml correctly. It 
actually happened to me some years ago. Internet Exploder is now better 
by two-three major versions but the xhtml is still a bit questionable. 
How about W3C starting work on HTML5?

The power of xmlc allows us to output in HTML by turning one simple 
switch so if only the IgnoreCase is missing for correct <br> and <hr> 
then I'd be for adding it there.

Obviously my comment is worthless if I don't attach a patch implementing 
it so feel free to ignore it/me :-)

Petr



--
You receive this message as a subscriber of the xmlc@xxxxxxxxxxxxx mailing list.
To unsubscribe: mailto:xmlc-unsubscribe@xxxxxxxxxxxxx
For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws