Bug#1050886: [pkg-gnupg-maint] Bug#1050886: Issues that need to be fixed in "yat2m" for transforming manuals to a man-page format

2023-08-30 Thread NIIBE Yutaka
Bjarni Ingi Gislason  wrote:

> Package: gpgrt-tools
> Version: 1.47-2
> Severity: normal
>
> Dear Maintainer,
>
>   The following are issues that yat2m needs to correct when producing
> man-page formatted manuals.
>
>   The example is from "gpg(1)".

Thank you for your bug report and good descriptions.

Last week, in upstream, I created a ticket for the problem of U+2010
vs. U+002D.

https://dev.gnupg.org/T6674

Since it's for yat2m, other problems should be handled in this ticket
too.
-- 



Bug#1050886: Issues that need to be fixed in "yat2m" for transforming manuals to a man-page format

2023-08-30 Thread Bjarni Ingi Gislason
Package: gpgrt-tools
Version: 1.47-2
Severity: normal

Dear Maintainer,

  The following are issues that yat2m needs to correct when producing
man-page formatted manuals.

  The example is from "gpg(1)".

-.-

Output from "mandoc -T lint gpg.1":

mandoc: gpg.1:152:1: WARNING: skipping paragraph macro: sp after PP
mandoc: gpg.1:646:1: WARNING: skipping paragraph macro: sp after PP
mandoc: gpg.1:1174:1: WARNING: skipping paragraph macro: sp after PP
mandoc: gpg.1:2210:1: WARNING: skipping paragraph macro: sp after PP
mandoc: gpg.1:2350:1: WARNING: skipping paragraph macro: sp after PP
mandoc: gpg.1:2747:1: WARNING: skipping paragraph macro: sp after PP
mandoc: gpg.1:2866:1: WARNING: skipping paragraph macro: sp after PP
mandoc: gpg.1:2965:1: WARNING: skipping paragraph macro: sp after PP
mandoc: gpg.1:3689:1: WARNING: skipping paragraph macro: sp after PP
mandoc: gpg.1:3737:1: WARNING: skipping paragraph macro: sp after PP
mandoc: gpg.1:3781:1: WARNING: skipping paragraph macro: sp after PP
mandoc: gpg.1:4076:1: WARNING: skipping paragraph macro: sp after PP
mandoc: gpg.1:4092:1: WARNING: skipping paragraph macro: sp after PP
mandoc: gpg.1:4183:2: WARNING: skipping paragraph macro: PP empty
mandoc: gpg.1:4184:1: WARNING: skipping paragraph macro: sp after PP
mandoc: gpg.1:4201:1: WARNING: skipping paragraph macro: sp after PP
mandoc: gpg.1:4304:1: WARNING: skipping paragraph macro: sp after PP
mandoc: gpg.1:4355:1: WARNING: skipping paragraph macro: sp after PP

-.-.

Input file is gpg.1

Change '-' (\-) to '\(en' (en-dash) for a numeric range.

gpg.1:338:the numbers 1-3 for certificate check level (see
gpg.1:345:numbers 1-9 or "T" for 10 and above to indicate trust signature levels
gpg.1:2859:that not all values in the 1024-65011712 range are legal and if an

-.-.

Change three HYPHEN-MINUSES (code 0x055, 2D) to an em-dash (\(em),
if one is intended.  An en-dash is usually surrounded by a space,
while an em-dash is used without spaces.

gpg.1:2287:--- you cannot make an group that points to another group. When used

-.-.

Mark a full stop (.) and the exclamation mark (!) with "\&",
if it does not mean an end of a sentence.
This is a preventive action,
the paragraph could be reshaped, e.g., after changes.

When typing, one does not always notice when the line wraps after the
period.
There are too many examples of input lines in manual pages,
that end with an abbreviation point.

This marking is robust, and independent of the position on the line.

It corresponds to "\ " in TeX, and to "@:" in Texinfo.


331:checking the signature (e.g. a non supported algorithm).  Signatures
589:ownertrust values (e.g. in the file \(oq\fIotrust.txt\fR\(cq), you may 
re-create
867:once it has been send to the public (i.e. to a keyserver).  In that case
901:(i.e. to a keyserver).  In that case you better use \fBrevuid\fR.
1000:a subkey, once it has been send to the public (i.e. to a keyserver).  In
1043:that is no longer usable (e.g. revoked, or expired). Then, remove any
1446:(e.g. "jpg"), "%T" for the MIME type of the image (e.g. "image/jpeg"),
1448:viewed (e.g. "f"), "%V" for the calculated validity as a string (e.g.
2184:(i.e. run, but give a warning).
2396:known (e.g. keyserver, web key directory) and set.  For a standard
2562:e.g. "2016-08-17". (drop-subkey)
2604:e.g. "2016-08-17". (drop-sig)
2704:(i.e. \fB--with-colons\fR).  Note that the legacy format does not
2822:(e.g. \fB--clear-sign\fR or \fB--sign\fR).
2833:to consider (e.g. \fB--symmetric\fR).
3027:in C syntax (e.g. 0x0042) or as a comma separated list of flag names.
3045:(e.g. "20070924T154812").
3367:(cf. \fB--s2k-mode\fR).
3878:(i.e. inside the angle brackets).

-.-.

Change -- in x--y to \(em (em-dash), or, if an
option, to \-\-

71:options \fB--with-colons\fR and \fB--status-fd\fR.  For certain
72:operations the option \fB--command-fd\fR may come handy too.  See
86:forcing their use via the \fB--cipher-algo\fR,
87:\fB--digest-algo\fR, \fB--cert-digest-algo\fR, or
88:\fB--compress-algo\fR options in GnuPG, it is possible to create a
104:the \fB--pgp6\fR, \fB--pgp7\fR, or \fB--pgp8\fR options. These
120:If you run into any problems, please add the option \fB--verbose\fR
131:.B  --version
136:.B  --help
144:.B  --warranty
148:.B  --dump-options
161:.B  --sign
164:Sign a message. This command may be combined with \fB--encrypt\fR
165:(to sign and encrypt a message), \fB--symmetric\fR (to sign and
166:symmetrically encrypt a message), or both \fB--encrypt\fR and
167:\fB--symmetric\fR (to sign and encrypt a message that can be
170:\fB--local-user\fR and \fB--default-key\fR options.
173:.B  --clear-sign
175:.B  --clearsign
181:explicitly using the \fB--local-user\fR and \fB--default-key\fR
186:.B  --detach-sign
192:.B  --encrypt
196:with \fB--sign\fR (to sign and encrypt a message),
197:\fB--symmetric\fR (to encrypt a message that can be decrypted using a
198:secret key or a passphrase), or \fB--sign\fR and
199:\fB--symmetric\fR together (for a signed message that