On Tue, Dec 31, 2024 at 01:30:59PM +0100, Hilmar Preusse wrote:
> On 31.12.24 Bjarni Ingi Gislason (bjarn...@simnet.is) wrote:
>
> Hello,
>
> > Package: texlive-extra-utils
> > Version: 2024.20241115-1
> > Severity: minor
> > Tags: patch
> >
> > * What led up to the situation?
> >
> > Checking for defects with a new version
> >
> The patch does not apply to the current upstream at [1].
>
> Please be so kind to create a new patch or (even better) do a pull
> request. If you are not familiar with github, send me the patch and
> I'll do the PR.
>
> https://raw.githubusercontent.com/pdfjam/pdfjam/refs/heads/master/pdfjam.1
>
> Thiw would be more helpful than (temporarily) patching an outdated
> version.
>
> Happa new year,
> Hilmar
>
> [1] https://github.com/pdfjam/pdfjam
Hi
I do not send e-mails to upstream if I have to acquire an account.
New patch in an attachment.
Content-Type: multipart/mixed; boundary="===============0925544496993014041=="
MIME-Version: 1.0
From: Bjarni Ingi Gislason <bjarn...@simnet.is>
To: Debian Bug Tracking System <sub...@bugs.debian.org>
Subject: pdfjam.1: Some remarks and a patch with editorial changes for this man
page
Message-ID: <173576727801.6703.14311107583703490470.report...@kassi.invalid.is>
X-Mailer: reportbug 13.0.2
Date: Wed, 01 Jan 2025 21:34:38 +0000
This is a multi-part MIME message sent by reportbug.
--===============0925544496993014041==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Package: texlive-extra-utils
Version: 2024.20241115-1
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?
an.tmac:<stdin>:1: style: .TH missing fourth argument; consider package/project
name and version (e.g., "groff 1.23.0")
an.tmac:<stdin>:1: style: .TH missing fifth argument and second argument '1'
not a recognized manual section; specify its title
* 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 texlive-extra-utils depends on:
ii libfile-homedir-perl 1.006-2
ii libunicode-linebreak-perl 0.0.20190101-1+b8
ii libyaml-tiny-perl 1.76-1
ii python3 3.12.8-1
ii tex-common 6.18
ii texlive-base 2024.20241115-1
ii texlive-binaries 2024.20240313.70630+ds-5+b1
ii texlive-latex-base 2024.20241115-1
ii texlive-luatex 2024.20241115-1
ii texlive-plain-generic 2024.20241115-1
Versions of packages texlive-extra-utils recommends:
ii ghostscript 10.04.0~dfsg-2+b1
pn liblog-log4perl-perl <none>
ii ruby 1:3.1+nmu1
ii texlive-latex-recommended 2024.20241115-1
Versions of packages texlive-extra-utils suggests:
pn chktex <none>
pn default-jre-headless <none>
pn dvidvi <none>
pn dvipng <none>
pn fragmaster <none>
pn lacheck <none>
pn latexdiff <none>
pn latexmk <none>
pn purifyeps <none>
pn xindy <none>
Versions of packages tex-common depends on:
ii ucf 3.0046
Versions of packages tex-common suggests:
pn debhelper <none>
Versions of packages texlive-extra-utils is related to:
ii tex-common 6.18
ii texlive-binaries 2024.20240313.70630+ds-5+b1
-- no debconf information
--===============0925544496993014041==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="chk_man.err.pdfjam.1"
Input file is pdfjam.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 pdfjam.1": (shortened list)
13 skipping paragraph macro
-.-.
Output from "test-groff -mandoc -t -ww -z pdfjam.1": (shortened list)
-.-.
Change two HYPHEN-MINUSES (code 0x2D) to an em-dash (\(em),
if one is intended.
" \(em " creates a too big gap in the text (in "troff").
An en-dash is usually surrounded by a space,
while an em-dash is used without spaces.
"man" (1 byte characters in input) transforms an en-dash (\(en) to one
HYPHEN-MINUS,
and an em-dash to two HYPHEN-MINUSES without considering the space
around it.
If "--" are two single "-"
(begin of an option or end of options)
then use "\-\-".
pdfjam.1:13:"pdfjam --help", and also in the web page mentioned below\&.
pdfjam.1:40:Please report bugs! --- either at GitHub or by email, see
-.-.
Change -- in x--y to \(em (em-dash), or, if an
option, to \-\-
13:"pdfjam --help", and also in the web page mentioned below\&.
-.-.
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.
13:"pdfjam --help", and also in the web page mentioned below\&.
-.-.
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 "\&".
40:Please report bugs! --- either at GitHub or by email, see
-.-.
Put a parenthetical sentence, phrase on a separate line,
if not part of a code.
See man-pages(7), item "semantic newline".
Not considered in a patch, too many lines.
pdfjam.1:11:"pdfpages" package (by Andreas Matthias) of pdflatex.
-.-.
No need for "\&" to be in front of a period (.),
if there is a character in front of it
6:pdfjam [OPTION [OPTION] \&.\&.\&.] [SRC [PAGESPEC] [SRC [PAGESPEC]] \&.\&.\&.]
-.-.
Test nr. 87:
Change "---" to an em dash
40:Please report bugs! --- either at GitHub or by email, see
-.-.
Output from "test-groff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z
":
an.tmac:<stdin>:1: style: .TH missing fourth argument; consider package/project
name and version (e.g., "groff 1.23.0")
an.tmac:<stdin>:1: style: .TH missing fifth argument and second argument '1'
not a recognized manual section; specify its title
-.-.
Additionally (general):
Abbreviations get a '\&' added after their final full stop (.) to mark them
as such and not as an end of a sentence.
There is no need to add a '\&' before a full stop (.) if it has a character
before it!
--===============0925544496993014041==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="pdfjam.1.diff"
--- pdfjam.1 2025-01-01 20:39:45.225750574 +0000
+++ pdfjam.1.new 2025-01-01 21:32:48.746767643 +0000
@@ -1,50 +1,46 @@
-.TH "pdfjam" "1" "18 November 2020" "" ""
+.TH pdfjam 1 "18 November 2020" "" ""
.SH "NAME"
pdfjam \- A shell script for manipulating PDF files
.SH "SYNOPSIS"
-.PP
-pdfjam [OPTION [OPTION] \&.\&.\&.] [SRC [PAGESPEC] [SRC [PAGESPEC]] \&.\&.\&.]
-.PP
+pdfjam [OPTION [OPTION] ...\&] [SRC [PAGESPEC] [SRC [PAGESPEC]] ...]
.SH "DESCRIPTION"
-.PP
pdfjam provides a front end to most capabilities of the
-"pdfpages" package (by Andreas Matthias) of pdflatex.
-Detailed information can be found via
-"pdfjam --help", and also in the web page mentioned below\&.
-.PP
-A working installation of pdflatex, with
-the pdfpages package, is required\&.
+"pdfpages" package
+(by Andreas Matthias)
+of pdflatex.
+Detailed information can be found via "pdfjam \-\-help",
+and also in the web page mentioned below.
+.PP
+A working installation of pdflatex,
+with the pdfpages package,
+is required.
.PP
The pdfjam script is distributed as (the main) part of the pdfjam package.
-The homepage of pdfjam is at https://github.com/pdfjam/pdfjam\&;.
-.PP
+The homepage of pdfjam is at https://github.com/pdfjam/pdfjam.
.SH "SETUP"
-.PP
See https://github.com/pdfjam/pdfjam
-.PP
.SH "CONFIGURATION FILES"
-.PP
Configuration of the PDFjam utilities involves specifying the location of
-pdflatex, the location of temporary files, specification of default page size,
-etc. This is done in a block of lines near the top of the pdfjam script;
+pdflatex,
+the location of temporary files,
+specification of default page size,
+etc.
+This is done in a block of lines near the top of the pdfjam script;
settings made there are over-ridden by any that are found at a site-wide
-configuration file (at /etc/pdfjam.conf, /usr/share/etc/pdfjam.conf,
-/usr/local/share/pdfjam.conf, or /usr/local/etc/pdfjam.conf), which in turn are
-over-ridden by any that are found in a user-defaults file at ~/.pdfjam.conf\&.
-.PP
+configuration file
+(at /etc/pdfjam.conf, /usr/share/etc/pdfjam.conf,
+/usr/local/share/pdfjam.conf, or /usr/local/etc/pdfjam.conf),
+which in turn are over-ridden by any
+that are found in a user-defaults file at ~/.pdfjam.conf.
.SH "LIMITATIONS AND BUGS"
+pdfjam does not work with encrypted PDF files,
+and does not preserve hyperlinks.
.PP
-pdfjam does not work with encrypted PDF files, and does not
-preserve hyperlinks.
-.PP
-Please report bugs! --- either at GitHub or by email, see
-https://github.com/pdfjam/pdfjam\&;.
-.PP
+Please report bugs!\& \(em either at GitHub or by email,
+see
+https://github.com/pdfjam/pdfjam.
.SH "LICENSE"
-.PP
pdfjam is distributed under the GNU public license.
-.PP
.SH "AUTHOR"
-.PP
The pdfjam package was written by David Firth and is
maintained by Reuben Thomas and Markus Kurtz.
--===============0925544496993014041==--
