Sorry for not answering that -- well a) because the html cleaner/parser I've written (using HTML::PullParser) sometimes leaves them behind in unscrambling jumbled html (because it doesn't know the difference between <i>hjhk<b>hjhkj</i>hkjhk</b> and <i>kkp<b>ttyt</i></b> and reopens the b tag after the /i), and b) even if they were only there when the user/user's html generator left them in they're pointless (especially given how harshly I've cleaned the code otherwise), and take up extra space and bandwidth.

And how exactly do you mean 'bundling' it? This application isn't tied to one os much less one type of hardware -- and you need to know that to provide a binary. A list of choices is just going to confuse them. *pictures self spending life helping people who downloaded the Win32 version because that's what their desktop is.* For a module or corprate application you can assume that the person installing it isn't totally braindead, and understands a little about the server -- there are days I want to stick my more braindead adminuser user cases in a firepit, unfortunately they're realistic. :|

Thanks, and if I do, I will :) hell if I become less insolvent in general I prolly will whether or not this project makes money ;)