Bug #98617 Literal .PP in man pages for mysqlpump and mysqldump
Submitted: 15 Feb 2020 16:38 Modified: 24 Feb 2020 23:08
Reporter: Daniël van Eeden (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: mysqlpump Command-line Client Severity:S3 (Non-critical)
Version:8.0.19 OS:Any
Assigned to: CPU Architecture:Any

[15 Feb 2020 16:38] Daniël van Eeden
Description:
From "man mysqlpump":
====================================================
               shell> mysqlpump [options] --result-file=dump.sql
       mysqlpump Invocation Syntax.PP By default, mysqlpump dumps all
       databases (with certain exceptions noted in mysqlpump Restrictions). To
       specify this behavior explicitly, use the --all-databases option:

           shell> mysqlpump --all-databases
====================================================

The .PP is not expected to be there. This is likely the .PP troff macro for paragraph, which should be on the start of the line, not in the middle.

Source for the above section:
====================================================
.sp
.if n \{\
.RS 4
.\}
.nf
shell> \fBmysqlpump [options] \-\-result\-file=dump\&.sql\fR
.fi
.if n \{\
.RE
.\}
.sp .5v
.RE
mysqlpump Invocation Syntax.PP
By default,
\fBmysqlpump\fR
dumps all databases (with certain exceptions noted in
mysqlpump Restrictions)\&. To specify this behavior explicitly, use the
\fB\-\-all\-databases\fR
option:
.sp
.if n \{\
.RS 4
.\}
.nf
shell> \fBmysqlpump \-\-all\-databases\fR
====================================================

How to repeat:
man mysqldump

$ rpm -q man-db groff-base mysql-community-client
man-db-2.8.4-5.fc31.x86_64
groff-base-1.22.3-20.fc31.x86_64
mysql-community-client-8.0.19-10.fc31.x86_64

Suggested fix:
Put .PP on the start of the line. Probably by changing the toolchain created to create the file.
[24 Feb 2020 23:08] Paul DuBois
Posted by developer:
 
Thanks for spotting this. Apparently a bug in the man XSLT transform. We'll compensate in our postprocessing script.