ldd.1, bootparam.7, feature_test_macros.7, inotify.7, man-pages.7, man.7, standards.7, zic.8: Convert inline formatting (\fX...\fP) to dot-directive formatting

Reported-by: Petr Gajdos <pgajdos@suse.cz>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

man1/ldd.1

@@ -100,7 +100,8 @@ support was added to the compiler releases.
 If you use
 .B ldd
 on one of these programs, the program will attempt to run with
-\fIargc\fP = 0 and the results will be unpredictable.
+.I argc
+= 0 and the results will be unpredictable.
 .\" .SH AUTHOR
 .\" David Engel.
 .\" Roland McGrath and Ulrich Drepper.

man7/bootparam.7

@@ -661,7 +661,7 @@ ER:None, ER:<Per-Target-Spec>), and over Host Adapter Probing
 .B "EATA/DMA configuration"
 The default list of I/O ports to be probed can be changed by
 .IP
-.BI eata= iobase,iobase,...\fP.
+.BI eata= iobase,iobase,... .
 .TP
 .B "Future Domain TMC-16x0 configuration"
 .IP
@@ -917,7 +917,9 @@ For a ThinkPad-720, add the option
 .IP
 .BI ibmmcascsi= N
 .IP
-where N is the \fIpun\fP (SCSI ID) of the subsystem.
+where N is the
+.I pun
+(SCSI ID) of the subsystem.
 .TP
 .B "The Aztech Interface"
 The syntax for this type of card is:

man7/feature_test_macros.7

@@ -72,11 +72,14 @@ Feature Test Macro Requirements for glibc (see
 _BSD_SOURCE || (_XOPEN_SOURCE && _XOPEN_SOURCE\ <\ 500)
 .RE
 .PP
-The \fB||\fP means that in order to obtain the declaration of
+The
+.B ||
+means that in order to obtain the declaration of
 .BR acct (2)
 from
 .IR <unistd.h> ,
-\fIeither\fP of the following macro
+.I either
+of the following macro
 definitions must be made before including any header files:
 .RS
 .nf
@@ -120,7 +123,9 @@ feature test macro can be used to expose the function
 declaration, and that macro is not defined by default.
 .SS Feature test macros understood by glibc
 The following paragraphs explain how feature test macros are handled
-in Linux glibc 2.\fIx\fP, \fIx\fP > 0.
+in Linux glibc 2.\fIx\fP,
+.I x
+> 0.
 .\" The details in glibc 2.0 are simpler, but combining a
 .\" a description of them with the details in later glibc versions
 .\" would make for a complicated description.
@@ -482,7 +487,9 @@ internally defines various other macros that are checked by
 other glibc header files.
 These macros have names prefixed by two underscores (e.g.,
 .BR __USE_MISC ).
-Programs should \fInever\fP define these macros directly:
+Programs should
+.I never
+define these macros directly:
 instead, the appropriate feature test macro(s) from the
 list above should be employed.
 .SH EXAMPLE

man7/inotify.7

@@ -260,7 +260,9 @@ when calling
 .PD 0
 .TP 18
 .BR IN_DONT_FOLLOW " (since Linux 2.6.15)"
-Don't dereference \fIpathname\fP if it is a symbolic link.
+Don't dereference
+.I pathname
+if it is a symbolic link.
 .TP
 .BR IN_EXCL_UNLINK " (since Linux 2.6.36)"
 .\" commit 8c1934c8d70b22ca8333b216aec6c7d09fdbd6a6
@@ -283,11 +285,15 @@ Add (OR) events to watch mask for this pathname if
 it already exists (instead of replacing mask).
 .TP
 .B IN_ONESHOT
-Monitor \fIpathname\fP for one event, then remove from
+Monitor
+.I pathname
+for one event, then remove from
 watch list.
 .TP
 .BR IN_ONLYDIR " (since Linux 2.6.15)"
-Only watch \fIpathname\fP if it is a directory.
+Only watch
+.I pathname
+if it is a directory.
 .PD
 .RE
 .PP
@@ -300,14 +306,17 @@ field returned by
 .PD 0
 .TP 18
 .B IN_IGNORED
-Watch was removed explicitly (\fBinotify_rm_watch\fP(2))
+Watch was removed explicitly
+.RB ( inotify_rm_watch (2))
 or automatically (file was deleted, or file system was unmounted).
 .TP
 .B IN_ISDIR
 Subject of this event is a directory.
 .TP
 .B IN_Q_OVERFLOW
-Event queue overflowed (\fIwd\fP is \-1 for this event).
+Event queue overflowed
+.RI ( wd
+is \-1 for this event).
 .TP
 .B IN_UNMOUNT
 File system containing watched object was unmounted.

man7/man-pages.7

@@ -104,7 +104,9 @@ New sentences should be started on new lines.
 This makes it easier to see the effect of patches,
 which often operate at the level of individual sentences.
 .SS Title line
-The first command in a man page should be a \fBTH\fP command:
+The first command in a man page should be a
+.B TH
+command:
 .RS
 .sp
 .B \&.TH
@@ -486,7 +488,8 @@ makes it easier to write tools that parse man page source files.)
 .PP
 Any reference to another man page
 should be written with the name in bold,
-\fIalways\fP followed by the section number,
+.I always
+followed by the section number,
 formatted in Roman (normal) font, without any
 separating spaces (e.g.,
 .BR intro (2)).

man7/man.7

@@ -84,7 +84,8 @@ that is, lines that start with \fB.\\"\fP) should be
 .I "title section date source manual"
 .sp
 .RE
-For details of the arguments that should be supplied to the \fBTH\fP
+For details of the arguments that should be supplied to the
+.B TH
 command, see
 .BR man-pages (7).
 .PP

man7/standards.7

@@ -43,8 +43,14 @@ This was the first Berkeley release that contained a TCP/IP
 stack and the sockets API.
 4.2BSD was released in 1983.
 
-Earlier major BSD releases included \fI3BSD\fP (1980), \fI4BSD\fP (1980),
-and \fI4.1BSD\fP (1981).
+Earlier major BSD releases included
+.IR 3BSD 
+(1980),
+.I 4BSD
+(1980),
+and
+.I 4.1BSD
+(1981).
 .TP
 .B 4.3BSD
 The successor to 4.2BSD, released in 1986.

man8/zic.8

@@ -165,7 +165,9 @@ is something else, then
 .I zic
 executes the command
 .ti +.5i
-\fByearistype\fP \fIyear\fP \fItype\fP
+.B yearistype
+.I year
+.I type
 .br
 to check the type of a year:
 an exit status of zero is taken to mean that the year is of the given type;