Your message dated Sun, 22 Mar 2009 17:58:51 +0200
with message-id <20090322155851.ga...@minerva.local.invalid>
has caused the report #280148,
regarding pod2man should create bold references
to be marked as having been forwarded to the upstream software
author(s)
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
280148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=280148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
On Sun, Nov 07, 2004 at 04:57:21PM +0100, Martin Schulze wrote:
> Package: perl
> Version: 5.8.4-3
>
> man(7) contains:
>
> Any reference to another man page (or to the subject of the cur-
> rent man page) is in bold. If the manual section number is
> given, it is given in Roman (normal) font, without any spaces
> (e.g., man(7)).
>
> However, pod2man creates
>
> \&\fIdhcpd\fR\|(8), \fItcpdump\fR\|(1), \s-1RFC2132\s0
> ^ ^
> B B <--- should be
>
> from
>
> dhcpd(8), tcpdump(1), RFC2132
>
> It would be nice if pod2man and other manpages would build similar links.
This is somewhat related to
<http://rt.cpan.org/Public/Bug/Display.html?id=43700>, which requests
that L<> would be handled better.
I see the text quoted above has meanwhile been moved into man-pages(7),
which specifically discusses Linux man pages. It also recommends the
references to be written as to .BR rather than \f escapes. I'm not
familiar enough with troff to know how portable that is; Solaris 10
does have it FWIW.
Clearly, L<dhcpd(8)> can easily be recognized as a reference to another
man page, but a plain dhcpd(8) needs a heuristic approach.
Russ, would you consider converting at least L<foo(3)> to .BR (or \fB... if
that's better)?
--
Niko Tyni nt...@debian.org
--- End Message ---
