Package: perl-doc
Version: 5.8.4-8
Severity: normal

The man page looks fine:

  % man perlpacktut | grep -n "tutorial on "
  6:       perlpacktut - tutorial on "pack" and "unpack"

...but not the 'whatis':

  % whatis  perlpacktut
  perlpacktut (1)      - tutorial on *(C`pack*(C' and *(C`unpack*(C'

Its man page source code:

  % zgrep -n "tutorial on " /usr/share/man/man1/perlpacktut.1.gz
  134:perlpacktut \- tutorial on \f(CW\*(C`pack\*(C'\fR and 
\f(CW\*(C`unpack\*(C'\fR

On my system there are several perl-ish man pages with the same bad
code:

  % apropos "C\`"
  ***WARNING*** this manpage is no longer up-to-date. 
See*(C`examples/map_to_gradient*(C' for a simple raw-pixel-manipulating 
plug-in. If you bug me enough I'll rewrite this document. (3pm) [Gimp::Pixel] - 
how to operate on raw pixels.
  but can of some help for people interested in using modified Tk source 
with*(C`perlTk*(C'. (3pm) [Tk::Internals] - what is Perl Tk interface doing 
when you call Tk functions.
  c2ph (1)             - Dump C structures as generated from *(C`cc - g - S*(C' 
stabs
  charnames (3perl)    - define character names for *(C`\N{named}*(C' string 
literal escapes
  Data::Dumper (3perl) - stringified perl data structures, suitable for both 
printing and *(C`eval*(C'
  if (3perl)           - *(C`use*(C' a Perl module if a condition holds
  PDL::Reduce (3pm)    - - a *(C`reduce*(C' function for PDL
  perlpacktut (1)      - tutorial on *(C`pack*(C' and *(C`unpack*(C'
  pstruct (1)          - Dump C structures as generated from *(C`cc - g - S*(C' 
stabs
  Term::ReadLine (3perl) - Perl interface to various *(C`readline*(C' packages. 
If no real package is found, substitutes stubs instead of basic functions.
  This document is under construction. The information is believed to be 
pertinent to the version of *(C`portableTk*(C' available when it was created. 
All the details are subject to change. (3pm) [Tk::Internals] - what is Perl Tk 
interface doing when you call Tk functions.
  This information is worse than useless for *(C`perlTk*(C' users (3pm) 
[Tk::Internals] - what is Perl Tk interface doing when you call Tk functions.

Parsing that with a one-liner, the source packages of those man
pages are:

  % apropos "C\`" | sed -e 's/ (.*//'   -e 's/.* .* .*//'   -e '/^$/d' | while 
read n ; do n=`whereis $n`; dlocate ${n##* } ; done | sort
  pdl: /usr/share/man/man3/PDL::Reduce.3pm.gz
  perl-doc: /usr/share/man/man1/perlpacktut.1.gz
  perl-doc: /usr/share/man/man3/Data::Dumper.3perl.gz
  perl-doc: /usr/share/man/man3/Term::ReadLine.3perl.gz
  perl-doc: /usr/share/man/man3/charnames.3perl.gz
  perl-doc: /usr/share/man/man3/if.3perl.gz
  perl: /usr/share/man/man1/c2ph.1.gz
  perl: /usr/share/man/man1/pstruct.1.gz

Mostly it's 'perl-doc'.

I'm guessing that "*(C`" was supposed to be a double quote, or
backquote, by way of some buggy doc reformatting script.  It should be
fixed, but what's the script's name?

  % zcat /usr/share/man/man1/perlpacktut.1.gz | head -n 1
  .\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14

...it's not on my system, even though its man page is:

  %whereis Pod::Man
  Pod::Man: /usr/share/man/man3/Pod::Man.3perl.gz

Searching through some uninstalled packages, it looks as though 'Pod::Man'
is in one of these:

  po4a - tools for helping translation of documentation
  info2man - Convert GNU info files to POD or man pages


NB: for me this seemingly cosmetic bug isn't 'minor' -- reason being
that those excess '*'s make it difficult to write scripts that parse the
output of 'apropos'.  I noticed this bug while writing such a script.


Hope this helps...

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.9-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)

Versions of packages perl-doc depends on:
ii  perl                          5.8.4-8    Larry Wall's Practical Extraction 

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to