Bug#1095043: lwptut.3pm: Some remarks about this man page

Sun Feb 2 23:44:47 GMT 2025

Package: libwww-perl
Version: 6.77-1
Severity: minor
Tags: upstream

   * What led up to the situation?

     Checking for defects with a new version

test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z < "man page"

  [Use "groff -e ' $' -e '\\~$' <file>" to find obvious trailing spaces.]

  ["test-groff" is a script in the repository for "groff"; is not shipped]
(local copy and "troff" slightly changed by me).

  [The fate of "test-nroff" was decided in groff bug #55941.]

   * What was the outcome of this action?

troff:<stdin>:84: warning: font name 'CW' is deprecated
troff:<stdin>:150: warning: trailing space in the line
troff:<stdin>:155: warning: trailing space in the line
troff:<stdin>:157: warning: trailing space in the line
troff:<stdin>:160: warning: trailing space in the line
troff:<stdin>:170: warning: trailing space in the line
troff:<stdin>:195: warning: trailing space in the line
troff:<stdin>:229: warning: trailing space in the line
troff:<stdin>:258: warning: trailing space in the line
troff:<stdin>:280: warning: trailing space in the line
troff:<stdin>:281: warning: trailing space in the line
troff:<stdin>:292: warning: trailing space in the line
troff:<stdin>:293: warning: trailing space in the line
troff:<stdin>:296: warning: trailing space in the line
troff:<stdin>:297: warning: trailing space in the line
troff:<stdin>:387: warning: trailing space in the line
troff:<stdin>:392: warning: trailing space in the line
troff:<stdin>:560: warning: trailing space in the line
troff:<stdin>:591: warning: trailing space in the line
troff:<stdin>:770: warning: trailing space in the line

   * What outcome did you expect instead?

     No output (no warnings).

N.B.

  The man page contains an 8-bit character, so the mailer uses base64
encoding for that attachment.

-.-

  General remarks and further material, if a diff-file exist, are in the
attachments.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.11-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libwww-perl depends on:
ii  ca-certificates             20241223
ii  libencode-locale-perl       1.05-3
ii  libfile-listing-perl        6.16-1
ii  libhtml-parser-perl         3.83-1+b2
ii  libhtml-tagset-perl         3.24-1
ii  libhtml-tree-perl           5.07-3
ii  libhttp-cookies-perl        6.11-1
ii  libhttp-date-perl           6.06-1
ii  libhttp-message-perl        7.00-2
ii  libhttp-negotiate-perl      6.01-2
ii  liblwp-mediatypes-perl      6.04-2
ii  liblwp-protocol-https-perl  6.14-1
ii  libnet-http-perl            6.23-1
ii  libtry-tiny-perl            0.32-1
ii  liburi-perl                 5.30-1
ii  libwww-robotrules-perl      6.02-1
ii  netbase                     6.4
ii  perl                        5.40.0-8

Versions of packages libwww-perl recommends:
pn  libdata-dump-perl    <none>
ii  libhtml-form-perl    6.12-1
ii  libhtml-format-perl  2.16-2
pn  libhttp-daemon-perl  <none>
ii  libmailtools-perl    2.22-1

Versions of packages libwww-perl suggests:
pn  libauthen-ntlm-perl  <none>

-- no debconf information
-------------- next part --------------
 Input file is lwptut.3pm

Output from "mandoc -T lint  lwptut.3pm": (shortened list)

      1 input text line longer than 80 bytes: So if we add the fol...
      1 input text line longer than 80 bytes: The actual content o...
      1 input text line longer than 80 bytes: The basic idiom is \...
      1 input text line longer than 80 bytes: The handiest variant...
      1 input text line longer than 80 bytes: To give a browser an...
      1 input text line longer than 80 bytes: When you use this \f...
      1 input text line longer than 80 bytes: a problem with the n...
      1 input text line longer than 80 bytes: and password (at \f(...
      1 input text line longer than 80 bytes: are the \f(CW\*(C`qu...
      1 input text line longer than 80 bytes: by default one minut...
      1 input text line longer than 80 bytes: can use the URI modu...
      1 input text line longer than 80 bytes: documentation, speci...
      1 input text line longer than 80 bytes: environment variable...
      1 input text line longer than 80 bytes: is to use the \f(CW\...
      1 input text line longer than 80 bytes: is with \f(CW\*(C`$u...
      1 input text line longer than 80 bytes: it's a GIF, then \f(...
      1 input text line longer than 80 bytes: its \f(CW\*(C`cookie...
      1 input text line longer than 80 bytes: the \f(CW$browser\fR...
      1 input text line longer than 80 bytes: the \f(CW\*(C`Client...
      1 input text line longer than 80 bytes: versions of LWP, so ...
      1 input text line longer than 80 bytes: won't actually reque...
      1 input text line longer than 80 bytes: you usually call the...
      4 whitespace at end of input line

-.-.

Output from "test-groff -mandoc -t -ww -z lwptut.3pm": (shortened list)

      1 font name 'CW' is deprecated
     19 trailing space in the line

-.-.

Show if Pod::Man generated this.

Who is actually creating this man page?  Debian or upstream?

Is the generating software out of date?

2:.\" Automatically generated by Pod::Man 5.01 (Pod::Simple 3.43)

-.-.

Remove space characters (whitespace) at the end of lines.
Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".

Number of lines affected is

19

-.-.

Wrong distance between sentences in the input file.

  Separate the sentences and subordinate clauses; each begins on a new
line.  See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").

  The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.

Remember coding: Only one command ("sentence") on each (logical) line.

E-mail: Easier to quote exactly the relevant lines.

Generally: Easier to edit the sentence.

Patches: Less unaffected text.

Search for two adjacent words is easier, when they belong to the same line,
and the same phrase.

  The amount of space between sentences in the output can then be
controlled with the ".ss" request.

Mark a final abbreviation point as such by suffixing it with "\&".

N.B.

  The number of lines affected can be too large to be in a patch.

68:Perl modules for accessing data on the Web. Like most Perl
70:documentation that is a complete reference to its interface. However,
76:that just happens to exist, called \fIPerl & LWP\fR. But this article
121:\&     | grep "/by\-module/Acme" | mail \-s "New Acme modules! Joy!" $USER
127:saving/mirroring a URL to a local file. See the LWP::Simple
136:error). To get at all those features, you'll have to use the full LWP
140:understand are LWP::UserAgent and HTTP::Response. LWP::UserAgent
181:class HTTP::Response. You really need only one browser object per
214:\&  $response = $browser\->get( $url, $key1, $value1, $key2, $value2, ... );
254:support turned off. There are various ways of turning it on, by setting
255:its \f(CW\*(C`cookie_jar\*(C'\fR attribute. A "cookie jar" is an object representing
257:the HTTP cookies that a browser knows about. It can correspond to a
324:\&  if( $response\->decoded_content =~ m{([0\-9,]+)(?:<.*?>)? results for} ) {
457:and gopher. If it tries accessing any other kind of URL (like an "ftp:"
531:avoid making too many requests too often. How long it will pause for, is
548:accessing certain sites and/or using certain protocols. This is most
571:Authentication". This isn't just any form of "enter your password"
681:\&   Aborting at paypal.pl line 7.   [or whatever program and line]
695:memory will have to hold the whole document \-\- \fIin memory\fR. If the
764:(like turning "C. & E. Bront??" to and from "C. & E. Brontë")
770:The book \fIPerl & LWP\fR by Sean M. Burke.  O'Reilly & Associates, 
776:Copyright 2002, Sean M. Burke.  You can redistribute this document and/or
780:Sean M. Burke \f(CW\*(C`sburke at cpan.org\*(C'\fR

-.-.

Do not use more than two space characters between sentences or (better)
only a new line character.

681:\&   Aborting at paypal.pl line 7.   [or whatever program and line]

-.-.

Add a zero (0) in front of a decimal fraction that begins with a period
(.)

7:.if t .sp .5v

-.-.

Remove quotes when there is a printable
but no space character between them
and the quotes are not for emphasis (markup),
for example as an argument to a macro.

66:.IX Header "DESCRIPTION"
775:.IX Header "COPYRIGHT"
779:.IX Header "AUTHOR"

-.-.

Use ".na" (no adjustment) instead of ".ad l" and then ".ad" to begin the
same adjustment again as before

61:.if n .ad l

-.-.

Add lines to use the CR font for groff instead of CW.

.ie \n(.g .ft CR
.el .ft CW

11:.ft CW

-.-.

Output from "test-groff  -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z ":

troff:<stdin>:84: warning: font name 'CW' is deprecated
troff:<stdin>:150: warning: trailing space in the line
troff:<stdin>:155: warning: trailing space in the line
troff:<stdin>:157: warning: trailing space in the line
troff:<stdin>:160: warning: trailing space in the line
troff:<stdin>:170: warning: trailing space in the line
troff:<stdin>:195: warning: trailing space in the line
troff:<stdin>:229: warning: trailing space in the line
troff:<stdin>:258: warning: trailing space in the line
troff:<stdin>:280: warning: trailing space in the line
troff:<stdin>:281: warning: trailing space in the line
troff:<stdin>:292: warning: trailing space in the line
troff:<stdin>:293: warning: trailing space in the line
troff:<stdin>:296: warning: trailing space in the line
troff:<stdin>:297: warning: trailing space in the line
troff:<stdin>:387: warning: trailing space in the line
troff:<stdin>:392: warning: trailing space in the line
troff:<stdin>:560: warning: trailing space in the line
troff:<stdin>:591: warning: trailing space in the line
troff:<stdin>:770: warning: trailing space in the line
-------------- next part --------------
  Any program (person), that produces man pages, should check the output
for defects by using (both groff and nroff)

[gn]roff -mandoc -t -ww -b -z -K utf8  <man page>

  The same goes for man pages that are used as an input.

  For a style guide use

  mandoc -T lint

-.-

  Any "autogenerator" should check its products with the above mentioned
'groff', 'mandoc', and additionally with 'nroff ...'.

  It should also check its input files for too long (> 80) lines.

  This is just a simple quality control measure.

  The "autogenerator" may have to be corrected to get a better man page,
the source file may, and any additional file may.

  Common defects:

  Not removing trailing spaces (in in- and output).
  The reason for these trailing spaces should be found and eliminated.

  Not beginning each input sentence on a new line.
Line length should thus be reduced.

  The script "reportbug" uses 'quoted-printable' encoding when a line is
longer than 1024 characters in an 'ascii' file.

  See man-pages(7), item "semantic newline".

-.-

The difference between the formatted output of the original and patched file
can be seen with:

  nroff -mandoc <file1> > <out1>
  nroff -mandoc <file2> > <out2>
  diff -u <out1> <out2>

and for groff, using

\"printf '%s\n%s\n' '.kern 0' '.ss 12 0' | groff -mandoc -Z - \"

instead of 'nroff -mandoc'

  Add the option '-t', if the file contains a table.

  Read the output from 'diff -u ...' with 'less -R' or similar.

-.-.

  If 'man' (man-db) is used to check the manual for warnings,
the following must be set:

  The option \"-warnings=w\"

  The environmental variable:

export MAN_KEEP_STDERR=yes (or any non-empty value)

  or

  (produce only warnings):

export MANROFFOPT=\"-ww -b -z\"

export MAN_KEEP_STDERR=yes (or any non-empty value)

-.-