Use a single-font-style macro (".B", ".I") for a single argument.
The output from "nroff" and "groff" is unchanged, except that '"'
around a word is printed in regular style.
Signed-off-by: Bjarni Ingi Gislason <bjarniig@xxxxxxxxx>
---
man7/keyrings.7 | 44 ++++++++++++++++++++++----------------------
man7/libc.7 | 2 +-
man7/locale.7 | 4 ++--
3 files changed, 25 insertions(+), 25 deletions(-)
diff --git a/man7/keyrings.7 b/man7/keyrings.7
index 4270d2e91..675af51de 100644
--- a/man7/keyrings.7
+++ b/man7/keyrings.7
@@ -104,7 +104,7 @@ the key is scheduled for garbage collection.
.SS Key types
The kernel provides several basic types of key:
.TP
-.I """keyring"""
+.RI """" keyring """"
'\" Note that keyrings use different fields in struct key in order to store
'\" their data - index_key instead of type/description and name_link/keys
'\" instead of payload.
@@ -117,7 +117,7 @@ being garbage collected because nothing refers to them.
Keyrings with descriptions (names)
that begin with a period (\(aq.\(aq) are reserved to the implementation.
.TP
-.I """user"""
+.RI """" user """"
This is a general-purpose key type.
The key is kept entirely within kernel memory.
The payload may be read and updated by user-space applications.
@@ -129,34 +129,34 @@ The description may be any valid string, though it is preferred that it
start with a colon-delimited prefix representing the service
to which the key is of interest
(for instance
-.IR """afs:mykey""" ).
+.RI """" afs:mykey """)."
.TP
-.IR """logon""" " (since Linux 3.3)"
+.RI """" logon """ (since Linux 3.3)"
.\" commit 9f6ed2ca257fa8650b876377833e6f14e272848b
This key type is essentially the same as
-.IR """user""" ,
+.RI """" user ""","
but it does not provide reading (i.e., the
.BR keyctl (2)
-.BR KEYCTL_READ
+.B KEYCTL_READ
operation),
meaning that the key payload is never visible from user space.
This is suitable for storing username-password pairs
that should not be readable from user space.
.IP
The description of a
-.IR """logon"""
+.RI """" logon """"
key
.I must\
start with a non-empty colon-delimited prefix whose purpose
is to identify the service to which the key belongs.
(Note that this differs from keys of the
-.IR """user"""
+.RI """" user """"
type, where the inclusion of a prefix is recommended but is not enforced.)
.TP
-.IR """big_key""" " (since Linux 3.13)"
+.RI """" big_key """ (since Linux 3.13)"
.\" commit ab3c3587f8cda9083209a61dbe3a4407d3cada10
This key type is similar to the
-.I """user"""
+.RI """" user """"
key type, but it may hold a payload of up to 1\ MiB in size.
This key type is useful for purposes such as holding Kerberos ticket caches.
.IP
@@ -254,7 +254,7 @@ the special keyring values
.BR KEY_SPEC_SESSION_KEYRING ,
.BR KEY_SPEC_PROCESS_KEYRING ,
and
-.BR KEY_SPEC_THREAD_KEYRING
+.B KEY_SPEC_THREAD_KEYRING
can be used to refer to the caller's own instances of these keyrings.
.TP
User keyrings
@@ -271,9 +271,9 @@ in calls to
and
.BR request_key (2),
the special keyring values
-.BR KEY_SPEC_USER_KEYRING
+.B KEY_SPEC_USER_KEYRING
and
-.BR KEY_SPEC_USER_SESSION_KEYRING
+.B KEY_SPEC_USER_SESSION_KEYRING
can be used to refer to the caller's own instances of these keyrings.
.IP
A link to the user keyring is placed in a new session keyring by
@@ -308,7 +308,7 @@ An originally planned "group keyring",
for storing keys associated with each GID known to the kernel,
is not so far implemented, is unlikely to be implemented.
Nevertheless, the constant
-.BR KEY_SPEC_GROUP_KEYRING
+.B KEY_SPEC_GROUP_KEYRING
has been defined for this keyring.
.\"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
.SS Possession
@@ -673,16 +673,16 @@ field provides some further information about the key.
The information that appears here depends on the key type, as follows:
.RS
.TP 4
-.IR """user""" " and " """logon"""
+.RI """" user """ and """ logon """"
The size in bytes of the key payload (expressed in decimal).
.TP
-.IR """keyring"""
+.RI """" keyring """"
The number of keys linked to the keyring,
or the string
-.IR empty
+.I empty
if there are no keys linked to the keyring.
.TP
-.IR """big_key"""
+.RI """" big_key """"
The payload size in bytes, followed either by the string
.IR [file] ,
if the key payload exceeds the threshold that means that the
@@ -695,7 +695,7 @@ indicating that the key is small enough to reside in kernel memory.
.RE
.IP
For the
-.IR """.request_key_auth"""
+.RI """" .request_key_auth """"
key type
(authorization key; see
.BR request_key (2)),
@@ -761,7 +761,7 @@ The value in this file specifies the interval, in seconds,
after which revoked and expired keys will be garbage collected.
The purpose of having such an interval is so that there is a window
of time where user space can see an error (respectively
-.BR EKEYREVOKED
+.B EKEYREVOKED
and
.BR EKEYEXPIRED )
that indicates what happened to the key.
@@ -878,8 +878,8 @@ scripts can use them.
.BR request-key (8)
.PP
The kernel source files
-.IR Documentation/crypto/asymmetric-keys.txt
+.I Documentation/crypto/asymmetric-keys.txt
and under
-.IR Documentation/security/keys
+.I Documentation/security/keys
(or, before Linux 4.13, in the file
.IR Documentation/security/keys.txt ).
diff --git a/man7/libc.7 b/man7/libc.7
index 66b06a267..7d68fd490 100644
--- a/man7/libc.7
+++ b/man7/libc.7
@@ -89,7 +89,7 @@ no longer takes care to document Linux libc details.
Nevertheless, the history is visible in vestiges of information
about Linux libc that remain in a few manual pages,
in particular, references to
-.IR libc4
+.I libc4
and
.IR libc5 .
.SS Other C libraries
diff --git a/man7/locale.7 b/man7/locale.7
index f582fe0cd..c7bb75dfc 100644
--- a/man7/locale.7
+++ b/man7/locale.7
@@ -148,10 +148,10 @@ and
functions to ease the use of this information.
The GNU gettext family of
functions also obey the environment variable
-.BR LANGUAGE
+.B LANGUAGE
(containing a colon-separated list of locales)
if the category is set to a valid locale other than
-.BR """C""" .
+.RB """" C """."
This category also affects the behavior of
.BR catopen (3).
.TP
--
2.20.1
