On Mon, 2003-06-02 at 15:34, Geoff Howard wrote: > <quote-from-wiki> > So... what I ended up doing was extending the HTMLSerializer (or whatever > serializer you're using for your pipelines), and overriding the > startPrefixMapping and endPrefixMapping methods to do nothing, effectively > removing all namespaces from my HTML. This also had the added benefit of > having no performance penalties (and theoretically, a ever-so-slight > speedup since we no longer process namespaces in our serializer). > </quote-from-wiki> > > 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.
Pragmatically speaking, that will probably work. -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
