Bug#1092118: ps2ps.1: Some remarks and a patch with editorial changes for this man page
Package: ghostscript
Version: 10.04.0~dfsg-2+b1
Severity: minor
Tags: patch
* 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 ' $' <file>" to find 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>:27: warning: trailing space in the line
* What outcome did you expect instead?
No output (no warnings).
-.-
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.6-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 ghostscript depends on:
ii libc6 2.40-4
ii libgs10 10.04.0~dfsg-2+b1
ghostscript recommends no packages.
Versions of packages ghostscript suggests:
ii texlive-binaries 2024.20240313.70630+ds-5+b1
-- no debconf information
Input file is ps2ps.1
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
-.-
So any 'generator' should check its products with the above mentioned
'groff', 'mandoc', and additionally with 'nroff ...'.
This is just a simple quality control measure.
The 'generator' may have to be corrected to get a better man page,
the source file may, and any additional file may.
Common defects:
Input text line longer than 80 bytes.
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.
Lines should thus be shorter.
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 of '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)
-.-.
Output from "mandoc -T lint ps2ps.1": (shortened list)
1 whitespace at end of input line
-.-.
Output from "test-groff -mandoc -t -ww -z ps2ps.1": (shortened list)
1 trailing space in the line
-.-.
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
1
-.-.
Change a HYPHEN-MINUS (code 0x2D) to a minus(-dash) (\-),
if it
is in front of a name for an option,
is a symbol for standard input,
is a single character used to indicate an option,
or is in the NAME section (man-pages(7)).
N.B. - (0x2D), processed as a UTF-8 file, is changed to a hyphen
(0x2010, groff \[u2010] or \[hy]) in the output.
20:Run "\fBgs -h\fR" to find the location of Ghostscript documentation on your
-.-.
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 "\&".
14:PostScript (EPS) files. NB, despite the name, the input need not be an
27:Artifex Software, Inc. are the
-.-.
Split lines longer than 80 characters into two or more lines.
Appropriate break points are the end of a sentence and a subordinate
clause; after punctuation marks.
Line 9, length 82
\fBps2ps\fR uses \fIgs\fR(1) to convert \fBPostScript\fR(tm) or \fBPDF\fR(tm) file
-.-.
Put a subordinate sentence (after a comma) on a new line.
10:"input" to simpler, normalized and (usually) faster PostScript in
13:\fBeps2eps\fR performs the equivalent optimization, creating Encapsulated
14:PostScript (EPS) files. NB, despite the name, the input need not be an
15:EPS file, PostScript or indeed PDF files are equally acceptable.
17:Both accept any general Ghostscript command line options, and
21:system, from which you can get more details.
23:\fBps2pdf\fR(1), \fBps2ascii\fR(1), \fBps2epsi\fR(1)
27:Artifex Software, Inc. are the
-.-.
Output from "test-groff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z ":
troff:<stdin>:27: warning: trailing space in the line
--- ps2ps.1 2025-01-04 19:07:57.383716380 +0000
+++ ps2ps.1.new 2025-01-04 19:19:40.425252611 +0000
@@ -6,23 +6,32 @@ ps2ps, eps2eps \- Ghostscript PostScript
.br
\fBeps2eps\fR [ \fIoptions\fR ] \fIinput output.eps\fR
.SH DESCRIPTION
-\fBps2ps\fR uses \fIgs\fR(1) to convert \fBPostScript\fR(tm) or \fBPDF\fR(tm) file
-"input" to simpler, normalized and (usually) faster PostScript in
-"output.ps". The output is level 2 DSC 3.0 conforming PostScript.
+\fBps2ps\fR uses \fIgs\fR(1) to convert \fBPostScript\fR(tm)
+or \fBPDF\fR(tm) file "input" to simpler,
+normalized
+and (usually) faster PostScript in "output.ps".
+The output is level 2 DSC 3.0 conforming PostScript.
.PP
-\fBeps2eps\fR performs the equivalent optimization, creating Encapsulated
-PostScript (EPS) files. NB, despite the name, the input need not be an
-EPS file, PostScript or indeed PDF files are equally acceptable.
+\fBeps2eps\fR performs the equivalent optimization,
+creating Encapsulated PostScript (EPS) files.
+NB, despite the name,
+the input need not be an EPS file,
+PostScript
+or indeed PDF files are equally acceptable.
.PP
-Both accept any general Ghostscript command line options, and
-options specific to the ps2write and eps2write devices.
+Both accept any general Ghostscript command line options,
+and options specific to the ps2write
+and eps2write devices.
.SH FILES
-Run "\fBgs -h\fR" to find the location of Ghostscript documentation on your
-system, from which you can get more details.
+Run "\fBgs \-h\fR" to find the location of Ghostscript documentation on your
+system,
+from which you can get more details.
.SH SEE ALSO
-\fBps2pdf\fR(1), \fBps2ascii\fR(1), \fBps2epsi\fR(1)
+.BR ps2pdf (1),
+.BR ps2ascii (1),
+.BR ps2epsi (1)
.SH VERSION
This document was last revised for Ghostscript version 10.04.0.
.SH AUTHOR
-Artifex Software, Inc. are the
+Artifex Software, Inc.\& are the
primary maintainers of Ghostscript.
Reply to: