Ok, I looked into using HTML Tidy -- actually the JTidy implementation
of it. Here's what could be done: implement the JTidy engine as a
filter so that HTML that was output would be "cleaned."
Here are the problems:
* JTidy adheared to HTML Tidy, which was only HTML 4.0 compliant. * HTML Tidy certainly wasn't perfect. * I would assume that using such a filter would NOT be advisable in a production environment as it almost certainly would slow things down. (It's not like it's GZipping output or actually removing whitespace.)
Now, with those potential problems, would anyone be interested in this type of filter to run in a development environment? I'm not saying that I could do it (I don't have much spare time right now) , I'm simply trying to see there is any interest.
We've been using a JTidy filter for a few years... it's kinda nice when you want to show the designer how their HTML is broken, but because it's often hard to tie a given piece of broken HTML to the component that generated it, it wasn't as great as we'd hoped.
Our JTidy filter takes the HTML, tidies it with whatever settings you want, then prints <hr> and prints whatever errors/warnings the filter caught. As you say, something you only throw on in development.
-- Serge Knystautas President Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
