I wasn't aware of HTML::TagFilter. Like I say in the description, I wasn't satisfied with HTML::Sanitizer, so I wrote HTML::Scrubber.

HTML::Scrubber and HTML::TagFilter appear to attack the exact same problem with nearly the same interface.

Looking at TagFilter's TO DO, I already have tests and do the HTML::Parser level optimization he talks about (he's welcomed to borrow those bits if he can).

I don't intend to expand HTML::Scrubber beyond the interface you see now (like he does). I like my simple interface.

HTML::Scrubber is never going to do any rule based translations (like changing all font tags with size=2 to span class=bar, or whatever).

++Hero Zzyzzx, it's nice to see others play merlyn ;D

MJD says you can't just make shit up and expect the computer to know what you mean, retardo! I run a Win32 PPM repository for perl 5.6x+5.8x. I take requests. ** The Third rule of perl club is a statement of fact: pod is sexy.

Looking at TagFilter's TO DO, I already have tests and do the HTML::Parser level optimization he talks about (he's welcomed to borrow those bits if he can).

Great, instead of inventing yet another wheel, why not send him the tests and patch implementing those features?

Depending on the perspective of the viewer, perfectly round wheels can look like a warped eliptical wheels, or a flat sticks, or maybe they aren't even visible to the person.

In situations like that -- where the wheels that have allready been invented don't look quite right -- there's nothing wrong with hammering out your own, if you see fit.

I don't think so. That would require that I get too intimate with his sourcecode. I'm just not interested (my wheel is complete). Why don't you do it?

MJD says you can't just make shit up and expect the computer to know what you mean, retardo! I run a Win32 PPM repository for perl 5.6x+5.8x. I take requests. ** The Third rule of perl club is a statement of fact: pod is sexy.