Hope you won't mind me reformatting if I'm going to maintain it; I don't mind working in other people's coding style when I'm contributing, but if I'm maintaining the code, I'm used to reading it in a particular structure.
Go right ahead, the module is yours for the taking. (In fact, I think so it Pod::Simple::Jockstrap. In theory, that module could be useful for things other than Pod::Simple::Man, but in practice I think it's very unlikely, and you're better off just throwing it in the same dist as Pod::Simple::Man.)
Let me know when you dist in all to CPAN, and then I'll go make sure Pod::Perldoc uses it happily when it's installed. (Currently it just calls pod2man, which is probably a bit wasteful, what with starting up a whole new perl process when it could instead just load Pod::Simple::Man or Pod::Man and pipe the output to the *roff of choice.)
Now I'm off to cure the ills of Pod::Simple's =encoding things, whole .t's currently scream like a banshee with 5.6 and old Encode versions. Watch the skies, everyone!
-- Sean M. Burke http://search.cpan.org/~sburke/
