I have done exactly this before -- does this still work from a purely technical perspective? If so, why wouldn't we just define an NoNsHTMLSerializer which extends HTMLSerializer and overrides
just those two methods? Then, it's a user decision whether these namespaces belong
in real-world html.
This sounds to be an excellent solution to the problem!
Alex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
