Eric Lavarde wrote: > and if you use C<> or F<> around the package names, doesn't it solve the > problem? I say this because the options (-n, --noscripts) have the > correct dashes, and it would make sense to _not_ beautify code and > filenames.
C<> fixes the dashes, but puts it in quotes: "mime-support", which is ugly. F<> makes it italic but does not fix the dashes, which is completly broken for a filename. L<> makes it bold but does not fix the dashes, which is broken for a link to another man page. It does handle urls with dashes in them correctly, FWIW. -n seems to be rendered correctly only because it's in an =item. I suppose I could use E<something (not 45)> in place of the dashes. But I prefer my pod documentation to be readable as source code too. So I cannot see any sane way to avoid man's hyphen brain-fuck using pod. Personally, I've given up and have man wrapped to use LC_CTYPE=C, but that's a different bug report I suppose. -- see shy jo
signature.asc
Description: Digital signature
