man: Use various groff escape sequences for quoting characters

debian/changelog

@@ -121,6 +121,7 @@ dpkg (1.18.0) UNRELEASED; urgency=low
     - Mark some words and commands as non-hyphenable in man pages.
     - Separate multi-line hanging tag paragraphs with .TQ in man pages.
     - Mark field names in bold in man pages.
+    - Use various groff escape sequences for quoting characters.
   * Output message fixes and improvements:
     - Remove trailing newline from string literal in warning calls.
     - Say “execute” instead of “exec” in Dpkg::Changelog::Parse error message.

man/deb-control.5

@@ -27,9 +27,9 @@ deb\-control \- Debian packages' master control file format
 control
 .
 .SH DESCRIPTION
-Each Debian package contains the master `control' file, which contains
-a number of fields, or comments when the line starts with \fB'#'\fP. Each
-field begins with a tag, such as
+Each Debian package contains the master \fIcontrol\fP file, which contains
+a number of fields, or comments when the line starts with \(oq\fB#\fP\(cq.
+Each field begins with a tag, such as
 .B Package
 or
 .B Version
@@ -55,7 +55,7 @@ are described in
 .BR deb\-version (5).
 .TP
 .BI Maintainer: " fullname-email"
-Should be in the format `Joe Bloggs <jbloggs@foo.com>', and is typically
+Should be in the format \(lqJoe Bloggs <jbloggs@foo.com>\(rq, and is typically
 the person who created the package, as opposed to the author of the
 software that was packaged.
 .TP
@@ -67,18 +67,20 @@ The format for the package description is a short brief summary on the
 first line (after the \fBDescription\fP field). The following lines should be
 used as a longer, more detailed description. Each line of the long description
 must be preceded by a space, and blank lines in the long description must
-contain a single '.' following the preceding space.
+contain a single \(oq\fB.\fP\(cq following the preceding space.
 .
 .SH OPTIONAL FIELDS
 .TP
 .BI Section: " section"
 This is a general field that gives the package a category based on the
-software that it installs. Some common sections are `utils', `net',
-`mail', `text', `x11' etc.
+software that it installs.
+Some common sections are \fButils\fP, \fBnet\fP, \fBmail\fP, \fBtext\fP,
+\fBx11\fP, etc.
 .TP
 .BI Priority: " priority"
 Sets the importance of this package in relation to the system as a whole.
-Common priorities are `required', `standard', `optional', `extra' etc.
+Common priorities are \fBrequired\fP, \fBstandard\fP, \fBoptional\fP,
+\fBextra\fP, etc.
 .LP
 In Debian, the
 .B Section
@@ -98,8 +100,10 @@ package to be removed (at least not without using one of the force options).
 .TP
 .BR Architecture: " \fIarch\fP|\fBall\fP"
 The architecture specifies which type of hardware this package was compiled
-for. Common architectures are `i386', `m68k', `sparc', `alpha', `powerpc'
-etc. Note that the
+for.
+Common architectures are \fBamd64\fP, \fBarmel\fP, \fBi386\fP, \fBpowerpc\fP,
+etc.
+Note that the
 .B all
 option is meant for packages that are architecture independent. Some examples
 of this are shell and Perl scripts, and documentation.
@@ -185,11 +189,14 @@ The syntax of
 and
 .B Suggests
 fields is a list of groups of alternative packages. Each group is a list
-of packages separated by vertical bar (or `pipe') symbols, `|'. The
-groups are separated by commas. Commas are to be read as `AND', and pipes
-as `OR', with pipes binding more tightly. Each package name is
-optionally followed by an architecture qualifier appended after a colon ":",
-optionally followed by a version number specification in parentheses.
+of packages separated by vertical bar (or \(lqpipe\(rq) symbols,
+\(oq\fB|\fP\(cq.
+The groups are separated by commas.
+Commas are to be read as \(lqAND\(rq, and pipes as \(lqOR\(rq, with pipes
+binding more tightly.
+Each package name is optionally followed by an architecture qualifier
+appended after a colon \(oq\fB:\fP\(cq, optionally followed by a version
+number specification in parentheses.
 .LP
 An architecture qualifier name can be a real Debian architecture name
 (since dpkg 1.16.5) or \fBany\fP (since dpkg 1.16.2).
@@ -198,11 +205,13 @@ A real Debian architecture name will match exactly that architecture for
 that package name, \fBany\fP will match any architecture for that package
 name if the package has been marked as \fBMulti\-Arch: allowed\fP.
 .LP
-A version number may start with a `>>', in which case any later version
-will match, and may specify or omit the Debian packaging revision (separated
-by a hyphen). Accepted version relationships are ">>" for greater than,
-"<<" for less than, ">=" for greater than or equal to, "<=" for less than
-or equal to, and "=" for equal to.
+A version number may start with a \(oq\fB>>\fP\(cq, in which case any later
+version will match, and may specify or omit the Debian packaging revision
+(separated by a hyphen).
+Accepted version relationships are \(oq\fB>>\fP\(cq for greater than,
+\(oq\fB<<\fP\(cq for less than, \(oq\fB>=\fP\(cq for greater than or
+equal to, \(oq\fB<=\fP\(cq for less than or equal to, and \(oq\fB=\fP\(cq
+for equal to.
 .TP
 .BI Breaks: " package-list"
 Lists packages that this one breaks, for example by exposing bugs
@@ -232,11 +241,12 @@ same files as the conflicted package.
 This is a list of virtual packages that this one provides. Usually this is
 used in the case of several packages all providing the same service.
 For example, sendmail and exim can serve as a mail server, so they
-provide a common package (`mail\-transport\-agent') on which other packages
-can depend. This will allow sendmail or exim to serve as a valid option
+provide a common package (\(lqmail\-transport\-agent\(rq) on which other
+packages can depend.
+This will allow sendmail or exim to serve as a valid option
 to satisfy the dependency. This prevents the packages that depend on a mail
 server from having to know the package names for all of them, and using
-`|' to separate the list.
+\(oq\fB|\fP\(cq to separate the list.
 .LP
 The syntax of
 .BR Breaks ,
@@ -249,7 +259,7 @@ In the
 .B Breaks
 and
 .B Conflicts
-fields, the comma should be read as `OR'.
+fields, the comma should be read as \(lqOR\(rq.
 An optional architecture qualifier can also be appended to the package name
 with the same syntax as above, but the default is \fBany\fP instead of the
 binary package architecture.
@@ -266,7 +276,8 @@ same syntax as above for the \fBProvides\fP field (since dpkg 1.17.11).
 This field lists extra source packages that were used during the build of this
 binary package.  This is an indication to the archive maintenance software that
 these extra source packages must be kept whilst this binary package is
-maintained.  This field must be a list of source package names with strict (=)
+maintained.
+This field must be a list of source package names with strict \(oq\fB=\fP\(cq
 version relationships.  Note that the archive maintenance software is likely to
 refuse to accept an upload which declares a
 .B Built\-Using

man/deb-old.5

@@ -60,7 +60,7 @@ subdirectory. In that case, the
 subdirectory will be in the control tarfile too, and the control
 tarfile will have only files in that directory. Optionally the
 control tarfile may contain an entry for
-.RB ` . ',
+.RB \(oq . \(cq,
 that is, the current directory.
 .PP
 The second gzipped tarfile is the filesystem archive, containing

man/deb-origin.5

@@ -24,7 +24,7 @@ deb\-origin \- Vendor-specific information files
 .SH DESCRIPTION
 The files in \fB/etc/dpkg/origins\fP can provide information about
 various vendors who are providing Debian packages. They contain a
-number of fields, or comments when the line starts with \fB'#'\fP.
+number of fields, or comments when the line starts with \(oq\fB#\fP\(cq.
 Each field begins with a tag, such as \fBVendor\fP or \fBParent\fP,
 followed by a colon and the body of the field. Fields are delimited
 only by field tags. In other words, field text may be multiple lines

man/deb-src-control.5

@@ -25,8 +25,9 @@ deb\-src\-control \- Debian source packages' master control file format
 control
 .
 .SH DESCRIPTION
-Each Debian source package contains the master "control" file, which contains
-at least 2 paragraphs, separated by a blank line. The first paragraph lists
+Each Debian source package contains the master \(Focontrol\(Fc file,
+which contains at least 2 paragraphs, separated by a blank line.
+The first paragraph lists
 all information about the source package in general, while each following
 paragraph describes exactly one binary package. Each paragraph consists of at
 least one field. A field starts with a fieldname, such as
@@ -40,8 +41,8 @@ fields is generally joined to a single line by the tools (except in the case of
 the
 .B Description
 field, see below). To insert empty lines into a multi-line
-field, insert a dot after the space. Lines starting with a \fB'#'\fP are
-treated as comments.
+field, insert a dot after the space.
+Lines starting with a \(oq\fB#\fP\(cq are treated as comments.
 .
 .SH SOURCE FIELDS
 .TP
@@ -54,7 +55,7 @@ long and must start with an alphanumeric character.
 
 .TP
 .BR Maintainer: " \fIfullname-email\fP (required)"
-Should be in the format "Joe Bloggs <jbloggs@foo.com>", and references the
+Should be in the format \(FoJoe Bloggs <jbloggs@foo.com>\(Fc, and references the
 person who currently maintains the package, as opposed to the author of the
 software or the original packager.
 
@@ -116,13 +117,15 @@ usually not needed.
 .TP
 .BI Section: " section"
 This is a general field that gives the package a category based on the
-software that it installs. Some common sections are "utils", "net",
-"mail", "text", "x11", etc.
+software that it installs.
+Some common sections are \fButils\fP, \fBnet\fP, \fBmail\fP, \fBtext\fP,
+\fBx11\fP, etc.
 
 .TP
 .BI Priority: " priority"
 Sets the importance of this package in relation to the system as a whole.
-Common priorities are "required", "standard", "optional", "extra", etc.
+Common priorities are \fBrequired\fP, \fBstandard\fP, \fBoptional\fP,
+\fBextra\fP, etc.
 
 In Debian, the
 .B Section
@@ -182,11 +185,14 @@ The syntax of the
 .B Build\-Depends\-Arch
 and
 .B Build\-Depends\-Indep
-fields is a list of groups of alternative packages. Each group is a list
-of packages separated by vertical bar (or "pipe") symbols, "|". The
-groups are separated by commas. Commas are to be read as "AND", and pipes
-as "OR", with pipes binding more tightly. Each package name is
-optionally followed by an architecture qualifier appended after a colon ":",
+fields is a list of groups of alternative packages.
+Each group is a list of packages separated by vertical bar (or \(lqpipe\(rq)
+symbols, \(oq\fB|\fP\(cq.
+The groups are separated by commas.
+Commas are to be read as \(lqAND\(rq, and pipes as \(lqOR\(rq, with pipes
+binding more tightly.
+Each package name is optionally followed by an architecture qualifier
+appended after a colon \(oq\fB:\fP\(cq,
 optionally followed by a version number specification in parentheses, an
 architecture specification in square brackets, and a restriction formula
 consisting of one or more lists of profile names in angle brackets.
@@ -197,7 +203,8 @@ The syntax of the
 and
 .B Build\-Conflicts\-Indep
 fields is a list of comma-separated package names, where the comma is read
-as an "AND". Specifying alternative packages using a "pipe" is not supported.
+as an \(lqAND\(rq.
+Specifying alternative packages using a \(lqpipe\(rq is not supported.
 Each package name is optionally followed by a version number specification in
 parentheses, an architecture specification in square brackets, and a
 restriction formula consisting of one or more lists of profile names in
@@ -214,21 +221,23 @@ name if the package is marked with \fBMulti\-Arch: allowed\fP, and
 \fBnative\fP will match the current build architecture if the package
 is not marked with \fBMulti\-Arch: foreign\fP.
 
-A version number may start with a ">>", in which case any later version
-will match, and may specify or omit the Debian packaging revision (separated
-by a hyphen). Accepted version relationships are ">>" for greater than,
-"<<" for less than, ">=" for greater than or equal to, "<=" for less than
-or equal to, and "=" for equal to.
+A version number may start with a \(oq\fB>>\fP\(cq, in which case any
+later version will match, and may specify or omit the Debian packaging
+revision (separated by a hyphen).
+Accepted version relationships are \(oq\fB>>\fP\(cq for greater than,
+\(oq\fB<<\fP\(cq for less than, \(oq\fB>=\fP\(cq for greater than or
+equal to, \(oq\fB<=\fP\(cq for less than or equal to, and \(oq\fB=\fP\(cq
+for equal to.
 
 An architecture specification consists of one or more architecture names,
 separated by whitespace. Exclamation marks may be prepended to each of the
-names, meaning "NOT".
+names, meaning \(lqNOT\(rq.
 
 A restriction formula consists of one or more restriction lists, separated
 by whitespace. Each restriction list is enclosed in angle brackets. Items
 in the restriction list are build profile names, separated by whitespace
-and can be prefixed with an exclamation mark, meaning "NOT". A restriction
-formula represents a disjunctive normal form expression.
+and can be prefixed with an exclamation mark, meaning \(lqNOT\(rq.
+A restriction formula represents a disjunctive normal form expression.
 
 Note that dependencies on packages in the
 .B build\-essential
@@ -267,9 +276,10 @@ for more information about them).
 
 .TP
 .BR Package\-Type: " \fBdeb\fP|\fBudeb\fP"
-This field defines the type of the package. "udeb" is for size-constrained
-packages used by the debian installer. "deb" is the default value, it's
-assumed if the field is absent. More types might be added in the future.
+This field defines the type of the package.
+\fBudeb\fP is for size-constrained packages used by the debian installer.
+\fBdeb\fP is the default value, it is assumed if the field is absent.
+More types might be added in the future.
 
 .TP
 .BI Subarchitecture: " value"

man/deb-symbols.5

@@ -40,11 +40,11 @@ in these files is:
 The \fIlibrary-soname\fR is exactly the value of the SONAME field
 as exported by \fBobjdump\fR(1). A \fIdependency-template\fR is a
 dependency where \fI#MINVER#\fR is dynamically replaced either by
-a version check like "(>= \fIminimal-version\fR)" or by nothing (if
+a version check like \(lq(>= \fIminimal-version\fR)\(rq or by nothing (if
 an unversioned dependency is deemed sufficient).
 .P
 Each exported \fIsymbol\fR (listed as \fIname\fR@\fIversion\fR, with
-\fIversion\fR being "Base" if the library is not versioned) is associated
+\fIversion\fR being \(lqBase\(rq if the library is not versioned) is associated
 to a \fIminimal-version\fR of its dependency template (the main dependency
 template is always used and will end up being combined with the dependency
 template referenced by \fIid-of-dependency-template\fR if present). The
@@ -56,7 +56,7 @@ Those fields are stored on lines starting with an asterisk. Currently,
 the only valid fields are:
 .TP
 .B Build\-Depends\-Package
-It indicates the name of the "\-dev" package associated to the library
+It indicates the name of the \(lq\-dev\(rq package associated to the library
 and is used by \fBdpkg\-shlibdeps\fP to make sure that the dependency
 generated is at least as strict as the corresponding build dependency
 (since dpkg 1.14.13).

man/deb-triggers.5

@@ -49,7 +49,7 @@ The trigger control directives currently supported are:
 .in +5
 Specifies that the package is interested in the named trigger. All
 triggers in which a package is interested must be listed using this
-directive in the triggers control file. The "noawait" variant does
+directive in the triggers control file. The \(lqnoawait\(rq variant does
 not put the triggering packages in triggers\-awaited state. This should
 be used when the functionality provided by the trigger is not crucial.
 .PP
@@ -70,7 +70,7 @@ Arranges that changes to this package's state will activate the
 specified trigger. The trigger will be activated at the start of
 the following operations: unpack, configure, remove (including for
 the benefit of a conflicting package), purge and deconfigure.
-The "noawait" variant does not put the triggering packages in
+The \(lqnoawait\(rq variant does not put the triggering packages in
 triggers\-awaited state. This should be used when the functionality
 provided by the trigger is not crucial.
 .PP
@@ -85,21 +85,21 @@ versions of the package will be activated.
 Unknown directives are an error which will prevent installation of the
 package.
 .PP
-The "\-noawait" variants should always be favored when possible since
+The \(lq\-noawait\(rq variants should always be favored when possible since
 triggering packages are not put in triggers\-awaited state and can thus
 be immediately configured without requiring the processing of the trigger.
 If the triggering packages are dependencies of other upgraded packages,
 it will avoid an early trigger processing run and make it possible
 to run the trigger only once as one of the last steps of the upgrade.
 .PP
-The "\-noawait" variants are only supported since dpkg 1.16.1, and
+The \(lq\-noawait\(rq variants are only supported since dpkg 1.16.1, and
 will lead to errors if used with an older dpkg. It is thus recommended
-to add a "Pre\-Depends: dpkg (>= 1.16.1)" to any package that wish to use
+to add a \(lqPre\-Depends: dpkg (>= 1.16.1)\(rq to any package that wish to use
 those directives.
 .PP
-The "\-await" alias variants are only supported since dpkg 1.17.21, and
+The \(lq\-await\(rq alias variants are only supported since dpkg 1.17.21, and
 will lead to errors if used with an older dpkg. It is thus recommended
-to add a "Pre\-Depends: dpkg (>= 1.17.21)" to any package that wish to use
+to add a \(lqPre\-Depends: dpkg (>= 1.17.21)\(rq to any package that wish to use
 those directives.
 .
 .SH SEE ALSO

man/deb-version.5

@@ -39,7 +39,7 @@ previous version numbering schemes, to be left behind.
 .TP
 .I upstream-version
 This is the main part of the version number.  It is
-usually the version number of the original ("upstream")
+usually the version number of the original (\(lqupstream\(rq)
 package from which the \fI.deb\fP file has been made,
 if this is applicable.  Usually this will be in the same
 format as that specified by the upstream author(s);
@@ -53,7 +53,7 @@ described below. The \fIupstream-version\fP
 portion of the version number is mandatory.
 .IP
 The \fIupstream-version\fP may contain only
-alphanumerics ("A-Za-z0-9") and the characters
+alphanumerics (\(lqA-Za-z0-9\(rq) and the characters
 .BR . " " + " " \- " " : " " ~
 (full stop, plus, hyphen, colon, tilde) and should
 start with a digit.  If there is no
@@ -74,11 +74,11 @@ It is optional; if it isn't present then the
 \fIupstream-version\fP may not contain a hyphen.
 This format represents the case where a piece of
 software was written specifically to be turned into a
-Debian package, and so there is only one "debianisation"
+Debian package, and so there is only one \(lqdebianisation\(rq
 of it and therefore no revision indication is required.
 .IP
 It is conventional to restart the
-\fIdebian-revision\fP at '1' each time time the
+\fIdebian-revision\fP at \(oq1\(cq each time time the
 \fIupstream-version\fP is increased.
 .IP
 Dpkg will break the version
@@ -102,8 +102,8 @@ is found it is returned.  The lexical comparison is a
 comparison of ASCII values modified so that all the letters
 sort earlier than all the non-letters and so that a tilde
 sorts before anything, even the end of a part.  For example,
-the following parts are in sorted order: '~~', '~~a', '~',
-the empty part, 'a'.
+the following parts are in sorted order: \(oq~~\(cq, \(oq~~a\(cq, \(oq~\(cq,
+the empty part, \(oqa\(cq.
 .PP
 Then the initial part of the remainder of each string which
 consists entirely of digit characters is determined.  The
@@ -122,7 +122,7 @@ mistakes in version numbering, and to cope with situations
 where the version numbering scheme changes.  It is
 \fBnot\fP intended to cope with version numbers containing
 strings of letters which the package management system cannot
-interpret (such as 'ALPHA' or 'pre\-'), or with
+interpret (such as \(oqALPHA\(cq or \(oqpre\-\(cq), or with
 silly orderings.
 .SH NOTES
 The tilde character and its special sorting properties were introduced

man/deb.5

@@ -75,7 +75,7 @@ as a series of plain files, of which the file
 .B control
 is mandatory and contains the core control information. The control
 tarball may optionally contain an entry for
-.RB ` . ',
+.RB \(oq . \(cq,
 the current directory.
 .PP
 The third, last required member is named
@@ -100,7 +100,7 @@ or
 .B data.tar
 and which should be safely ignored by older programs, will have names
 starting with an underscore,
-.RB ` _ '.
+.RB \(oq _ \(cq.
 .PP
 Those new members which won't be able to be safely ignored will be
 inserted before

man/dpkg-buildflags.1

@@ -66,7 +66,7 @@ The configuration files can contain comments on lines starting with a hash
 .BI \-\-dump
 Print to standard output all compilation flags and their values. It prints
 one flag per line separated from its value by an equal sign
-("\fIflag\fP=\fIvalue\fP"). This is the default action.
+(\(lq\fIflag\fP=\fIvalue\fP\(rq). This is the default action.
 .TP
 .BI \-\-list
 Print the list of flags supported by the current vendor
@@ -202,16 +202,16 @@ to support other languages).
 .P
 Each area feature can be enabled and disabled in the \fBDEB_BUILD_OPTIONS\fP
 and \fBDEB_BUILD_MAINT_OPTIONS\fP environment variable's area value with the
-"+" and "\-" modifier.
-For example, to enable the \fBhardening\fP "pie" feature and disable the
-"fortify" feature you can do this in \fBdebian/rules\fP:
+\(oq\fB+\fP\(cq and \(oq\fB\-\fP\(cq modifier.
+For example, to enable the \fBhardening\fP \(lqpie\(rq feature and disable the
+\(lqfortify\(rq feature you can do this in \fBdebian/rules\fP:
 .P
   export DEB_BUILD_MAINT_OPTIONS=hardening=+pie,\-fortify
 .P
 The special feature \fBall\fP (valid in any area) can be used to enable or
 disable all area features at the same time.
 Thus disabling everything in the \fBhardening\fP area and enabling only
-"format" and "fortify" can be achieved with:
+\(lqformat\(rq and \(lqfortify\(rq can be achieved with:
 .P
   export DEB_BUILD_MAINT_OPTIONS=hardening=\-all,+format,+fortify
 .
@@ -272,7 +272,7 @@ calls to \fBprintf\fP and \fBscanf\fP functions where the format string is
 not a string literal and there are no format arguments, as in
 \fBprintf(foo);\fP instead of \fPprintf("%s", foo);\fP
 This may be a security hole if the format string came from untrusted
-input and contains "%n".
+input and contains \(oq%n\(cq.
 .
 .TP
 .B fortify
@@ -282,7 +282,7 @@ to \fBCPPFLAGS\fP. During code generation the compiler
 knows a great deal of information about buffer sizes (where possible), and
 attempts to replace insecure unlimited length buffer function calls with
 length-limited ones. This is especially useful for old, crufty code.
-Additionally, format strings in writable memory that contain '%n' are
+Additionally, format strings in writable memory that contain \(oq%n\(cq are
 blocked. If an application depends on such a format string, it will need
 to be worked around.
 
@@ -450,7 +450,7 @@ $(MAKE) $(shell dpkg\-buildflags \-\-export=cmdline)
 .fi
 .RE
 .PP
-To set build flags in a shell script or shell fragment, "eval" can be
+To set build flags in a shell script or shell fragment, \fBeval\fP can be
 used to interpret the output and to export the flags in the environment:
 .PP
 .RS 4

man/dpkg-deb.1

@@ -221,7 +221,7 @@ will produce. The format is a string that will be output for each package
 listed.
 
 The string may reference any status field using the
-"${\fIfield-name\fR}" form, a list of the valid fields can be easily
+\(lq${\fIfield-name\fR}\(rq form, a list of the valid fields can be easily
 produced using
 .B \-I
 on the same package. A complete explanation of the formatting options
@@ -229,7 +229,7 @@ on the same package. A complete explanation of the formatting options
 explanation of the \fB\-\-showformat\fP option in
 .BR dpkg\-query (1).
 
-The default for this field is "${Package}\\t${Version}\\n".
+The default for this field is \(lq${Package}\\t${Version}\\n\(rq.
 .TP
 .BI \-z compress-level
 Specify which compression level to use on the compressor backend, when

man/dpkg-divert.1

@@ -36,8 +36,8 @@ File \fIdiversions\fP are a way of forcing
 not to install a file into its
 location, but to a \fIdiverted\fP location. Diversions can be used through the
 Debian package scripts to move a file away when it causes a conflict. System
-administrators can also use it to override some package's configuration
-file, or whenever some files (which aren't marked as 'conffiles') need to be
+administrators can also use it to override some package's configuration file,
+or whenever some files (which aren't marked as \(lqconffiles\(rq) need to be
 preserved by \fBdpkg\fP, when installing a newer version of a package which
 contains those files.
 .sp

man/dpkg-gensymbols.1

@@ -74,16 +74,17 @@ from the minimal version so that backports with a lower version number
 but the same upstream version still satisfy the generated dependencies.
 If the Debian revision can't be dropped because the symbol really got
 added by the Debian specific change, then one should suffix the version
-with "~".
+with \(oq\fB~\fP\(cq.
 .P
 Before applying any patch to the symbols file, the maintainer should
 double-check that it's sane. Public symbols are not supposed to disappear,
 so the patch should ideally only add new lines.
 .P
-Note that you can put comments in symbols files: any line with '#' as the
-first character is a comment except if it starts with '#include' (see
-section \fBUsing includes\fP). Lines starting with '#MISSING:' are special
-comments documenting symbols that have disappeared.
+Note that you can put comments in symbols files: any line with \(oq#\(cq as
+the first character is a comment except if it starts with \(oq#include\(cq
+(see section \fBUsing includes\fP).
+Lines starting with \(oq#MISSING:\(cq are special comments documenting
+symbols that have disappeared.
 .P
 Do not forget to check if old symbol versions need to be increased.
 There is no way \fBdpkg\-gensymbols\fP can warn about this. Blindly
@@ -150,7 +151,7 @@ symbols will continuously appear as MISSING in the diff in each new package
 revision.  This behaviour serves as a reminder for the maintainer that such a
 symbol needs to be removed from the symbol file or readded to the library. When
 the optional symbol, which was previously declared as MISSING, suddenly
-reappears in the next revision, it will be upgraded back to the "existing"
+reappears in the next revision, it will be upgraded back to the \(lqexisting\(rq
 status with its minimum version unchanged.
 
 This tag is useful for symbols which are private where their disappearance do

man/dpkg-maintscript-helper.1

@@ -75,7 +75,7 @@ maintainer scripts in version \fB3.0\-1\fP, should set \fIprior-version\fP
 to \fB3.0\-1~\fP.
 .TP
 .I package
-The package name. When the package is "Multi-Arch: same" this parameter
+The package name. When the package is \(lqMulti\-Arch: same\(rq this parameter
 must include the architecture qualifier, otherwise it should \fBnot\fP
 usually include the architecture qualifier (as it would disallow
 cross-grades, or switching from being architecture specific to

man/dpkg-name.1

@@ -57,12 +57,13 @@ Files will be moved into a subdirectory. If the directory given as argument exis
 the files will be moved into that directory otherwise the name of
 the target directory is extracted from the section field in the
 control part of the package. The target directory will be
-`unstable/binary\-\fIarchitecture\fP/\fIsection\fP'. If the section is
-not found in the control, then `no\-section' is assumed, and in this case,
-as well as for sections `non\-free' and `contrib' the target directory is
-`\fIsection\fP/binary\-\fIarchitecture\fP'. The section field isn't required
-so a lot of packages will find their way to the `no\-section' area. Use
-this option with care, it's messy.
+\(Founstable/binary\-\fIarchitecture\fP/\fIsection\fP\(Fc.
+If the section is not found in the control, then \fBno\-section\fP is assumed,
+and in this case, as well as for sections \fBnon\-free\fP and \fBcontrib\fP
+the target directory is \(Fo\fIsection\fP/binary\-\fIarchitecture\fP\(Fc.
+The section field is not required so a lot of packages will find their way
+to the \fBno\-section\fP area.
+Use this option with care, it's messy.
 .TP
 .BR \-c ", " \-\-create\-dir
 This option can used together with the \fB\-s\fP option. If a target
@@ -88,12 +89,12 @@ might depend on this naming structure.
 .SH EXAMPLES
 .TP
 .B dpkg\-name bar\-foo.deb
-The file `bar\-foo.deb' will be renamed to bar\-foo_1.0\-2_i386.deb or
+The file \fBbar\-foo.deb\fP will be renamed to bar\-foo_1.0\-2_i386.deb or
 something similar (depending on whatever information is in the control
-part of `bar\-foo.deb').
+part of \fBbar\-foo.deb\fP).
 .TP
 .B find /root/debian/ \-name \(aq*.deb\(aq | xargs \-n 1 dpkg\-name \-a
-All files with the extension `deb' in the directory /root/debian and its
+All files with the extension \fBdeb\fP in the directory /root/debian and its
 subdirectory's will be renamed by \fBdpkg\-name\fP if required into names
 with no architecture information.
 .TP

man/dpkg-parsechangelog.1

@@ -36,9 +36,9 @@ form.
 .SH OPTIONS
 .TP
 .BR \-l " \fIchangelog-file\fP"
-Specifies the changelog file to read information from. A '\-' can be
-used to specify reading from standard input. The
-default is
+Specifies the changelog file to read information from.
+A \(oq\-\(cq can be used to specify reading from standard input.
+The default is
 .BR debian/changelog .
 .TP
 .BR \-F " \fIchangelog-format\fP"
@@ -70,7 +70,8 @@ of the output. They need to be supported by the parser script
 in question. See also \fBNOTES\fP.
 .TP
 .BI \-\-file " file"
-Set the changelog filename to parse. Default is '-' (standard input).
+Set the changelog filename to parse.
+Default is \(oq-\(cq (standard input).
 .TP
 .BR \-l ", " \-\-label " \fIfile\fP"
 Set the name of the changelog file to use in error messages, instead

man/dpkg-query.1

@@ -137,11 +137,12 @@ asterisk (*) and question mark (?) will match a slash, and blackslash
 (\\) will be used as an escape character.
 
 If the first character in the \fIfilename-search-pattern\fP is none of
-"*[?/" then it will be considered a substring match and will be implicitly
-surrounded by "*" (as in *\fIfilename-search-pattern\fP*).
-If the subsequent string contains any of "*[?\\", then it will handled
-like a glob pattern, otherwise any trailing "/" or "/." will be removed
-and a literal path lookup will be performed.
+\(oq\fB*[?/\fP\(cq then it will be considered a substring match and will be
+implicitly surrounded by \(oq\fB*\fP\(cq (as in
+\fB*\fP\fIfilename-search-pattern\fP\fB*\fP).
+If the subsequent string contains any of \(oq\fB*[?\\\fP\(cq, then it will
+handled like a glob pattern, otherwise any trailing \(oq\fB/\fP\(cq or
+\(oq\fB/.\fP\(cq will be removed and a literal path lookup will be performed.
 
 This command will not list extra files created by maintainer scripts,
 nor will it list alternatives.
@@ -242,9 +243,10 @@ fields in control files):
 .TP
 .B binary:Package
 It contains the binary package name with a possible architecture qualifier
-like "libc6:amd64" (since dpkg 1.16.2). The architecture qualifier will
-only be present if the package has a \fBMulti\-Arch\fP field with a value
-of \fBsame\fP. This makes the package name unambiguous.
+like \(lqlibc6:amd64\(rq (since dpkg 1.16.2).
+The architecture qualifier will only be present if the package has a
+\fBMulti\-Arch\fP field with a value of \fBsame\fP.
+This makes the package name unambiguous.
 .TP
 .B binary:Summary
 It contains the package short description (since dpkg 1.16.2).

man/dpkg-shlibdeps.1

@@ -193,7 +193,7 @@ by default).
 .BI \-t type
 Prefer shared library dependency information tagged for the given
 package type. If no tagged information is available, falls back to untagged
-information. The default package type is "deb". Shared library dependency
+information. The default package type is \fBdeb\fP. Shared library dependency
 information is tagged for a given type by prefixing it with the name of the
 type, a colon, and whitespace.
 .TP
@@ -242,10 +242,10 @@ even if they are not yet used by other packages.
 .BI \-\-warnings= value
 \fIvalue\fP is a bit field defining the set of warnings that
 can be emitted by \fBdpkg\-shlibdeps\fP (since dpkg 1.14.17).
-Bit 0 (value=1) enables the warning "symbol \fIsym\fP used by \fIbinary\fP
-found in none of the libraries", bit 1 (value=2) enables the warning
-"package could avoid a useless dependency" and bit 2 (value=4)
-enables the warning "\fIbinary\fP should not be linked against \fIlibrary\fP".
+Bit 0 (value=1) enables the warning \(lqsymbol \fIsym\fP used by \fIbinary\fP
+found in none of the libraries\(rq, bit 1 (value=2) enables the warning
+\(lqpackage could avoid a useless dependency\(rq and bit 2 (value=4) enables
+the warning \(lq\fIbinary\fP should not be linked against \fIlibrary\fP\(rq.
 The default \fIvalue\fP is 3: the first two warnings are active by
 default, the last one is not. Set \fIvalue\fP to 7 if you want all
 warnings to be active.

man/dpkg-source.1

@@ -64,7 +64,7 @@ extracted directories will be too, and all the files and directories
 will inherit its group ownership.
 
 If the source package uses a non-standard format (currently this means all
-formats except "1.0"), its name will be stored in
+formats except \(lq1.0\(rq), its name will be stored in
 \fBdebian/source/format\fP so that the following builds of the source
 package use the same format by default.
 
@@ -81,7 +81,8 @@ additional parameters might be accepted.
 found in this ordered list:
 the format indicated with the \fI\-\-format\fP command line option,
 the format indicated in \fBdebian/source/format\fP,
-"1.0". The fallback to "1.0" is deprecated and will be removed at some
+\(lq1.0\(rq.
+The fallback to \(lq1.0\(rq is deprecated and will be removed at some
 point in the future, you should always document the desired source format
 in \fBdebian/source/format\fP. See section \fBSOURCE PACKAGE FORMATS\fP
 for an extensive description of the various source package formats.
@@ -207,12 +208,12 @@ contain (e.g. CVS/, .cvsignore, .svn/). The default regex is already
 very exhaustive, but if you need to replace it, please note that by
 default it can match any part of a path, so if you want to match the
 begin of a filename or only full filenames, you will need to provide
-the necessary anchors (e.g. '(^|/)', '($|/)') yourself.
+the necessary anchors (e.g. \(oq(^|/)\(cq, \(oq($|/)\(cq) yourself.
 .TP
 .BR \-\-extend\-diff\-ignore =\fIregex\fP
 The perl regular expression specified will extend the default value used by
 \fB\-\-diff\-ignore\fP and its current value, if set (since dpkg 1.15.6).
-It does this by concatenating "\fB|\fP\fIregex\fP" to the existing value.
+It does this by concatenating \(lq\fB|\fP\fIregex\fP\(rq to the existing value.
 This option is convenient to use in \fBdebian/source/options\fP to exclude
 some auto-generated files from the automatic patch generation.
 .TP
@@ -271,8 +272,8 @@ packages with broken versions, just for backwards compatibility.
 
 .SH SOURCE PACKAGE FORMATS
 If you don't know what source format to use, you should probably pick
-either "3.0 (quilt)" or "3.0 (native)". See
-https://wiki.debian.org/Projects/DebSrc3.0 for information on the
+either \(lq3.0 (quilt)\(rq or \(lq3.0 (native)\(rq.
+See https://wiki.debian.org/Projects/DebSrc3.0 for information on the
 deployment of those formats within Debian.
 
 .SS Format: 1.0
@@ -296,7 +297,7 @@ will be left over).
 
 Building a native package is just creating a single tarball with
 the source directory. Building a non-native package involves
-extracting the original tarball in a separate ".orig" directory and
+extracting the original tarball in a separate \(lq.orig\(rq directory and
 regenerating the \fB.diff.gz\fP by comparing the source package
 \fIdirectory\fP with the .orig directory.
 
@@ -425,10 +426,10 @@ Skips application of the debian diff on top of the upstream sources
 .SS Format: 2.0
 Extraction supported since dpkg 1.13.9, building supported since dpkg 1.14.8.
 Also known as wig&pen. This format is not recommended for wide-spread
-usage, the format "3.0 (quilt)" replaces it. Wig&pen was the first
-specification of a new-generation source package format.
+usage, the format \(lq3.0 (quilt)\(rq replaces it.
+Wig&pen was the first specification of a new-generation source package format.
 
-The behaviour of this format is the same as the "3.0 (quilt)" format
+The behaviour of this format is the same as the \(lq3.0 (quilt)\(rq format
 except that it doesn't use an explicit list of patches. All files in
 \fBdebian/patches/\fP matching the perl regular expression \fB[\\w\-]+\fP
 must be valid patches: they are applied at extraction time.
@@ -451,7 +452,8 @@ an original tarball (\fB.orig.tar.\fP\fIext\fP where \fIext\fP can be
 \fBgz\fP, \fBbz2\fP, \fBlzma\fP and \fBxz\fP) and a debian tarball
 (\fB.debian.tar.\fP\fIext\fP). It can also contain additional original
 tarballs (\fB.orig\-\fP\fIcomponent\fP\fB.tar.\fP\fIext\fP).
-\fIcomponent\fP can only contain alphanumeric characters and hyphens ("\-").
+\fIcomponent\fP can only contain alphanumeric characters and hyphens
+(\(oq\-\(cq).
 .PP
 .B Extracting
 .PP
@@ -598,7 +600,7 @@ Automatically create the main original tarball as empty if it's missing
 and if there are supplementary original tarballs (since dpkg 1.15.6).
 This option is meant to
 be used when the source package is just a bundle of multiple upstream
-software and where there's no "main" software.
+software and where there's no \(lqmain\(rq software.
 .TP
 .B \-\-no\-unapply\-patches, \-\-unapply\-patches
 By default, \fBdpkg\-source\fP will automatically unapply the patches in the
@@ -648,7 +650,7 @@ in the current directory. At least one file must be given.
 .BI \-\-target\-format= value
 \fBRequired\fP. Defines the real format of the generated source package.
 The generated .dsc file will contain this value in its \fBFormat\fP field
-and not "3.0 (custom)".
+and not \(lq3.0 (custom)\(rq.
 .
 .SS Format: 3.0 (git)
 Supported since dpkg 1.14.17.
@@ -662,13 +664,13 @@ git clone.
 .B Extracting
 .PP
 The bundle is cloned as a git repository to the target directory.
-If there is a gitshallow file, it is installed as `.git/shallow` inside
+If there is a gitshallow file, it is installed as \fI.git/shallow\fP inside
 the cloned git repository.
 .PP
 Note that by default the new repository will have the same branch checked
-out that was checked out in the original source. (Typically "master", but
-it could be anything.) Any other branches will be available under
-`remotes/origin/`.
+out that was checked out in the original source.
+(Typically \(lqmaster\(rq, but it could be anything.)
+Any other branches will be available under \fIremotes/origin/\fP.
 .PP
 .B Building
 .PP
@@ -715,23 +717,23 @@ various cleanup are done to save space.
 .SH DIAGNOSTICS
 .SS no source format specified in debian/source/format
 The file \fBdebian/source/format\fP should always exist and indicate the
-desired source format. For backwards compatibility, format "1.0" is
+desired source format. For backwards compatibility, format \(lq1.0\(rq is
 assumed when the file doesn't exist but you should not rely on this:
 at some point in the future \fBdpkg\-source\fP will be modified to fail
 when that file doesn't exist.
 
-The rationale is that format "1.0" is no longer the recommended format,
-you should usually pick one of the newer formats ("3.0 (quilt)", "3.0
-(native)") but \fBdpkg\-source\fP will not do this automatically for you.
+The rationale is that format \(lq1.0\(rq is no longer the recommended format,
+you should usually pick one of the newer formats (\(lq3.0 (quilt)\(rq, \(lq3.0
+(native)\(rq) but \fBdpkg\-source\fP will not do this automatically for you.
 If you want to continue using the old format, you should be explicit about
-it and put "1.0" in \fBdebian/source/format\fP.
+it and put \(lq1.0\(rq in \fBdebian/source/format\fP.
 .SS the diff modifies the following upstream files
-When using source format "1.0" it is usually a bad idea to modify
+When using source format \(lq1.0\(rq it is usually a bad idea to modify
 upstream files directly as the changes end up hidden and mostly
 undocumented in the .diff.gz file. Instead you should store your changes
 as patches in the debian directory and apply them at build-time. To avoid
-this complexity you can also use the format "3.0 (quilt)" that offers this
-natively.
+this complexity you can also use the format \(lq3.0 (quilt)\(rq that offers
+this natively.
 .SS cannot represent change to \fIfile\fP
 Changes to upstream sources are usually stored with patch files, but not
 all changes can be represented with patches: they can only alter the
@@ -757,7 +759,8 @@ or trailing spaces are allowed.
 .SS debian/source/include\-binaries
 This file contains a list of binary files (one per line) that should be
 included in the debian tarball. Leading and trailing spaces are stripped.
-Lines starting with "#" are comments and are skipped. Empty lines are ignored.
+Lines starting with \(oq\fB#\fP\(cq are comments and are skipped.
+Empty lines are ignored.
 .SS debian/source/options
 This file contains a list of long options that should be automatically
 prepended to the set of command line options of a \fBdpkg\-source \-\-build\fR
@@ -766,9 +769,11 @@ or \fBdpkg\-source \-\-print\-format\fR call. Options like
 this file.
 .P
 Each option should be put on a separate line. Empty lines and lines
-starting with "#" are ignored. The leading "\-\-" should be
-stripped and short options are not allowed. Optional spaces are allowed
-around the "=" symbol and optional quotes are allowed around the value.
+starting with \(oq\fB#\fP\(cq are ignored.
+The leading \(oq\fB\-\-\fP\(cq should be stripped and short options are
+not allowed.
+Optional spaces are allowed around the \(oq\fB=\fP\(cq symbol and optional
+quotes are allowed around the value.
 Here's an example of such a file:
 .P
   # let dpkg\-source create a debian.tar.bz2 with maximal compression
@@ -788,17 +793,19 @@ a preference tied to the maintainer or to the VCS repository where
 the source package is maintained.
 .SS debian/source/local\-patch\-header \fRand\fP debian/source/patch\-header
 Free form text that is put on top of the automatic patch generated
-in formats "2.0" or "3.0 (quilt)". \fBlocal\-patch\-header\fP is not
+in formats \(lq2.0\(rq or \(lq3.0 (quilt)\(rq. \fBlocal\-patch\-header\fP is not
 included in the generated source package while \fBpatch\-header\fP is.
 .SS debian/patches/series
 This file lists all patches that have to be applied (in the given order)
 on top of the upstream source package. Leading and trailing spaces are
-stripped. Lines starting with "#" are comments and are skipped. Empty
-lines are ignored. Remaining lines start with a patch filename (relative
+stripped.
+Lines starting with \(oq\fB#\fP\(cq are comments and are skipped.
+Empty lines are ignored.
+Remaining lines start with a patch filename (relative
 to the \fBdebian/patches/\fP directory) up to the first space character or
 the end of line. Optional \fBquilt\fP options can follow up to the end of line
-or the first "#" preceded by one or more spaces (which marks the start of
-a comment up to the end of line).
+or the first \(oq\fB#\fP\(cq preceded by one or more spaces (which marks the
+start of a comment up to the end of line).
 .SH BUGS
 The point at which field overriding occurs compared to certain
 standard output field settings is rather confused.

man/dpkg-statoverride.1

@@ -25,7 +25,7 @@ dpkg\-statoverride \- override ownership and mode of files
 .RI [ option "...] " command
 .
 .SH DESCRIPTION
-`\fBstat overrides\fR' are a way to tell
+\(lq\fBstat overrides\fR\(rq are a way to tell
 .BR dpkg (1)
 to use a different owner
 or mode for a path when a package is installed (this applies to any
@@ -46,8 +46,8 @@ Add an override for \fIpath\fP. \fIpath\fP does not need to exist
 when this command is used; the override will be stored and used later.
 Users and groups can be specified by their name (for example \fBroot\fR
 or \fBnobody\fR), or by their number by prepending the number with a
-`\fB#\fR' (for example \fB#0\fR or \fB#65534\fR). The \fImode\fR needs
-to be specified in octal.
+\(oq\fB#\fR\(cq (for example \fB#0\fR or \fB#65534\fR).
+The \fImode\fR needs to be specified in octal.
 
 If \fB\-\-update\fP is specified and \fIpath\fP exists, it is immediately
 set to the new owner and mode.
@@ -95,10 +95,10 @@ be used as the \fBdpkg\fP data directory.
 .I /var/lib/dpkg/statoverride
 File which contains the current list of stat overrides of the system. It
 is located in the \fBdpkg\fP administration directory, along with other files
-important to \fBdpkg\fP, such as `status' or `available'.
+important to \fBdpkg\fP, such as \fIstatus\fP or \fIavailable\fP.
 .br
 Note: \fBdpkg\-statoverride\fP preserves the old copy of this file, with
-extension "\-old", before replacing it with the new one.
+extension \(lq\-old\(rq, before replacing it with the new one.
 .
 .SH SEE ALSO
 .BR dpkg (1).

man/dpkg.1

@@ -287,9 +287,9 @@ not be shown.
 .TP
 .B \-\-set\-selections
 Set package selections using file read from stdin. This file should be
-in the format '\fIpackage\fP \fIstate\fP', where state is one of
+in the format \(lq\fIpackage\fP \fIstate\fP\(rq, where state is one of
 \fBinstall\fP, \fBhold\fP, \fBdeinstall\fP or \fBpurge\fP. Blank lines
-and comment lines beginning with '#' are also permitted.
+and comment lines beginning with \(oq#\(cq are also permitted.
 
 The \fIavailable\fP file needs to be up-to-date for this command to be
 useful, otherwise unknown packages will be ignored with a warning. See
@@ -323,7 +323,7 @@ architecture \fBdpkg\fP is built for (i.e. the output of
 \fB\-\-print\-architecture\fP) can never be removed from that list.
 .TP
 .B \-\-print\-architecture
-Print architecture of packages \fBdpkg\fP installs (for example, "i386").
+Print architecture of packages \fBdpkg\fP installs (for example, \(lqi386\(rq).
 .TP
 .B \-\-print\-foreign\-architectures
 Print a newline-separated list of the extra architectures \fBdpkg\fP is
@@ -473,7 +473,7 @@ Configure also any unpacked but unconfigured packages on which the current
 package depends.
 
 \fBhold\fP:
-Process packages even when marked "hold".
+Process packages even when marked \(lqhold\(rq.
 
 \fBremove\-reinstreq\fP:
 Remove a package, even if it's broken and marked to require
@@ -646,10 +646,13 @@ previously excluded paths matching the specified patterns during install
 \fIWarning: take into account that depending on the excluded paths you
 might completely break your system, use with caution.\fP
 
-The glob patterns use the same wildcards used in the shell, were '*' matches
-any sequence of characters, including the empty string and also '/'. For
-example, \fI'/usr/*/READ*'\fP matches \fI'/usr/share/doc/package/README'\fP.
-As usual, '?' matches any single character (again, including '/'). And '['
+The glob patterns use the same wildcards used in the shell, were
+\(oq*\(cq matches any sequence of characters, including the empty string
+and also \(oq/\(cq.
+For example, \(Fo\fI/usr/*/READ*\fP\(Fc matches
+\(Fo\fI/usr/share/doc/package/README\fP\(Fc.
+As usual, \(oq?\(cq matches any single character (again, including \(oq/\(cq).
+And \(oq[\(cq
 starts a character class, which can contain a list of characters, ranges
 and complementations. See \fBglob\fP(7) for detailed information about
 globbing. Note: the current implementation might re-include more directories
@@ -674,14 +677,14 @@ matches a file name making the decision.
 Sets the output format for the \fB\-\-verify\fP command (since dpkg 1.17.2).
 
 The only currently supported output format is \fBrpm\fP, which consists
-of a line for every path that failed any check. The lines start with 9
-characters to report each specific check result, a '\fB?\fP' implies the
-check could not be done (lack of support, file permissions, etc), '\fB.\fP'
-implies the check passed, and an alphanumeric character implies a specific
-check failed; the md5sum verification is denoted with a '\fB5\fP' on
-the third character. The line is followed by a space and an attribute
-character (currently '\fBc\fP' for conffiles), another
-space and the pathname.
+of a line for every path that failed any check.
+The lines start with 9 characters to report each specific check result,
+a \(oq\fB?\fP\(cq implies the check could not be done (lack of support,
+file permissions, etc), \(oq\fB.\fP\(cq implies the check passed, and
+an alphanumeric character implies a specific check failed; the md5sum
+verification is denoted with a \(oq\fB5\fP\(cq on the third character.
+The line is followed by a space and an attribute character (currently
+\(oq\fBc\fP\(cq for conffiles), another space and the pathname.
 .TP
 \fB\-\-status\-fd \fR\fIn\fR
 Send machine-readable package status and progress information to file
@@ -717,17 +720,17 @@ The output format used is the same as in \fB\-\-status\-fd\fP.
 Log status change updates and actions to \fIfilename\fP, instead of
 the default \fI/var/log/dpkg.log\fP. If this option is given multiple
 times, the last filename is used. Log messages are of the form
-`YYYY-MM-DD HH:MM:SS startup \fItype\fP \fIcommand\fP' for each dpkg
+\(oqYYYY-MM-DD HH:MM:SS startup \fItype\fP \fIcommand\fP\(cq for each dpkg
 invocation where \fItype\fP is \fBarchives\fP (with a \fIcommand\fP of
 \fBunpack\fP or \fBinstall\fP) or \fBpackages\fP (with a \fIcommand\fP of
 \fBconfigure\fP, \fBtriggers\-only\fP, \fBremove\fP or \fBpurge\fP);
-`YYYY-MM-DD HH:MM:SS status \fIstate\fP \fIpkg\fP \fIinstalled-version\fP'
+\(oqYYYY-MM-DD HH:MM:SS status \fIstate\fP \fIpkg\fP \fIinstalled-version\fP\(cq
 for status change updates;
-`YYYY-MM-DD HH:MM:SS \fIaction\fP \fIpkg\fP \fIinstalled-version\fP
-\fIavailable-version\fP' for actions where \fIaction\fP is one of
+\(oqYYYY-MM-DD HH:MM:SS \fIaction\fP \fIpkg\fP \fIinstalled-version\fP
+\fIavailable-version\fP\(cq for actions where \fIaction\fP is one of
 \fBinstall\fP, \fBupgrade\fP, \fBconfigure\fP, \fBtrigproc\fP,
 \fBdisappear\fP, \fBremove\fP or \fBpurge\fP; and
-`YYYY-MM-DD HH:MM:SS conffile \fIfilename\fP \fIdecision\fP' for conffile
+\(oqYYYY-MM-DD HH:MM:SS conffile \fIfilename\fP \fIdecision\fP\(cq for conffile
 changes where \fIdecision\fP is either \fBinstall\fP or \fBkeep\fP.
 .TP
 \fB\-\-no\-debsig\fP
@@ -878,7 +881,7 @@ To remove an installed elvis package:
 
 To install a package, you first need to find it in an archive or
 CDROM. The \fIavailable\fP file shows that the vim package is in section
-"editors":
+\fBeditors\fP:
 .br
 \fB     cd /media/cdrom/pool/main/v/vim\fP
 \fB     dpkg \-i vim_4.5\-3.deb\fP

man/dpkg.cfg.5

@@ -25,7 +25,7 @@ This file contains default options for dpkg. Each line contains a
 single option which is exactly the same as a normal command line
 option for dpkg except for the leading hyphens which are not used
 here. Quotes surrounding option values are stripped. Comments are
-allowed by starting a line with a hash sign ("\fB#\fR").
+allowed by starting a line with a hash sign (\(oq\fB#\fR\(cq).
 .
 .SH FILES
 .I /etc/dpkg/dpkg.cfg.d/[0-9a-zA-Z_-]*

man/dselect.1

@@ -60,12 +60,13 @@ configuration file \fI/etc/dpkg/dselect.cfg\fP or the files on the
 configuration directory \fI/etc/dpkg/dselect.cfg.d/\fP. Each line in the
 configuration file is either an option (exactly the same as the
 command line option but without leading hyphens) or a comment (if it starts
-with a \fB#\fR).
+with a \(oq\fB#\fR\(cq).
 .br
 .TP
 .BI \-\-admindir " directory"
-Changes the directory where the dpkg `\fIstatus\fP', `\fIavailable\fP' and
-similar files are located. This defaults to \fI/var/lib/dpkg\fP
+Changes the directory where the dpkg \(oq\fIstatus\fP\(cq,
+\(oq\fIavailable\fP\(cq and similar files are located.
+This defaults to \fI/var/lib/dpkg\fP
 and normally there shouldn't be any need to change it.
 .TP
 .BR \-D "\fIfile\fP, " \-\-debug " \fIfile\fP"
@@ -128,9 +129,9 @@ overriding the compiled-in colors. Use standard curses color names.
 .IP
 Optionally, after the color specification is another colon, and an
 attribute specification. This is a list of one or more attributes,
-separated by plus ("+") characters. Available attributes include (not all
-of these will work on all terminals): normal, standout, underline, reverse,
-blink, bright, dim, bold
+separated by plus (\(oq+\(cq) characters.
+Available attributes include (not all of these will work on all terminals):
+normal, standout, underline, reverse, blink, bright, dim, bold
 .TP
 .BR \-? ", " \-\-help
 Print a brief help text and exit successfully.
@@ -246,7 +247,7 @@ Unless \fBdselect\fP is run in expert
 or immediate mode, a help screen is first displayed when choosing this
 command from the menu. The user is \fIstrongly\fP advised to study all of
 the information presented in the online help screens, when one pops up.
-The online help screens can at any time be invoked with the \fB'?'\fP key.
+The online help screens can at any time be invoked with the \(oq\fB?\fP\(cq key.
 .sp
 .SS Screen layout
 .sp
@@ -257,15 +258,15 @@ the group header. The bottom half of the screen shows some details
 about the package currently selected in the top half of the screen.
 The type of detail that is displayed can be varied.
 .sp
-Pressing the \fB'I'\fP key toggles a full-screen display of the packages
+Pressing the \(oq\fBI\fP\(cq key toggles a full-screen display of the packages
 list, an enlarged view of the package details, or the equally split screen.
 .sp
 .SS Package details view
 .sp
 The package details view by default shows the extended package description
 for the package that is currently selected in the packages status list.
-The type of detail can be toggled by pressing the \fB'i'\fP key. This
-alternates between:
+The type of detail can be toggled by pressing the \(oq\fBi\fP\(cq key.
+This alternates between:
  - the extended description
  - the control information for the installed version
  - the control information for the available version
@@ -283,12 +284,12 @@ and packages known from the available packages database.
 For every package, the list shows the package's status, priority, section,
 installed and available architecture, installed and available versions,
 the package name and its short description, all in one line.
-By pressing the \fB'A'\fP key, the display of the installed and available
-architecture can be toggled between on an off.
-By pressing the \fB'V'\fP key, the display of the installed and available
-version can be toggled between on an off.
-By pressing the \fB'v'\fP key, the package status display is toggled between
-verbose and shorthand.
+By pressing the \(oq\fBA\fP\(cq key, the display of the installed and
+available architecture can be toggled between on an off.
+By pressing the \(oq\fBV\fP\(cq key, the display of the installed and
+available version can be toggled between on an off.
+By pressing the \(oq\fBv\fP\(cq key, the package status display is toggled
+between verbose and shorthand.
 Shorthand display is the default.
 .sp
 The shorthand status indication consists
@@ -341,20 +342,21 @@ commands mapped to the following keys:
 .SS Searching and sorting
 .sp
 The list of packages can be searched by package name. This
-is done by pressing \fB'/'\fP, and typing a simple search
+is done by pressing \(oq\fB/\fP\(cq, and typing a simple search
 string. The string is interpreted as a
 .BR regex (7)
 regular expression.
-If you add \fB'/d'\fP to the search expression, dselect will also search
-in descriptions. If you add \fB'/i'\fP the search will be case insensitive.
-You may combine these two suffixes like this: \fB'/id'\fP.
-Repeated searching is accomplished by repeatedly pressing
-the \fB'n'\fP or \fB'\\'\fP keys, until the wanted package is found.
+If you add \(oq\fB/d\fP\(cq to the search expression, dselect will also
+search in descriptions.
+If you add \(oq\fB/i\fP\(cq the search will be case insensitive.
+You may combine these two suffixes like this: \(oq\fB/id\fP\(cq.
+Repeated searching is accomplished by repeatedly pressing the
+\(oq\fBn\fP\(cq or \(oq\fB\\\fP\(cq keys, until the wanted package is found.
 If the search reaches the bottom of the list, it wraps to the top
 and continues searching from there.
 .sp
 The list sort order can be varied by pressing
-the \fB'o'\fP and \fB'O'\fP keys repeatedly.
+the \(oq\fBo\fP\(cq and \(oq\fBO\fP\(cq keys repeatedly.
 The following nine sort orderings can be selected:
  alphabet          available           status
  priority+section  available+priority  status+priority
@@ -409,10 +411,11 @@ it is best to follow up the suggestions made by \fBdselect\fP.
 .sp
 The listed packages' selection state may be reverted to the original
 settings, as they were before the unresolved depends or conflicts
-were created, by pressing the \fB'R'\fP key. By pressing the \fB'D'\fP
-key, the automatic suggestions are reset, but the change that caused
-the dependency resolution screen to be prompted is kept as requested.
-Finally, by pressing \fB'U'\fP, the selections are again set to the
+were created, by pressing the \(oq\fBR\fP\(cq key.
+By pressing the \(oq\fBD\fP\(cq key, the automatic suggestions are reset,
+but the change that caused the dependency resolution screen to be prompted
+is kept as requested.
+Finally, by pressing \(oq\fBU\fP\(cq, the selections are again set to the
 automatic suggestion values.
 .sp
 .SS Establishing the requested selections
@@ -424,21 +427,21 @@ However, if there are any unresolved depends, \fBdselect\fP will again
 prompt the user with a dependency resolution screen.
 .sp
 To alter a set of selections that creates unresolved depends or
-conflicts and forcing \fBdselect\fP to accept it, press the \fB'Q'\fP
+conflicts and forcing \fBdselect\fP to accept it, press the \(oq\fBQ\fP\(cq
 key. This sets the selections as specified by the user,
 unconditionally. Generally, don't do this unless you've read
 the fine print.
 .sp
 The opposite effect, to back out any selections change requests and
 go back to the previous list of selections, is attained by pressing
-the \fB'X'\fP or \fBescape\fP keys. By repeatedly pressing these
+the \(oq\fBX\fP\(cq or \fBescape\fP keys. By repeatedly pressing these
 keys, any possibly detrimental changes to the requested package
 selections can be backed out completely to the last established
 settings.
 .sp
 If you mistakenly establish some settings and wish to revert all the
 selections to what is currently installed on the system, press the
-\fB'C'\fP key.
+\(oq\fBC\fP\(cq key.
 This is somewhat similar to using the unhold command on all packages,
 but provides a more obvious panic button in cases where the user
 pressed \fBenter\fP by accident.

man/dselect.cfg.5

@@ -25,7 +25,7 @@ This file contains default options for dselect. Each line contains a
 single option which is exactly the same as a normal command line
 option for dselect except for the leading hyphens which are not used
 here. Quotes surrounding option values are stripped. Comments are
-allowed by starting a line with a hash sign ("\fB#\fR").
+allowed by starting a line with a hash sign (\(oq\fB#\fR\(cq).
 .
 .SH FILES
 .I /etc/dpkg/dselect.cfg.d/[0-9a-zA-Z_-]*

man/start-stop-daemon.8

@@ -218,7 +218,7 @@ Change to this username/uid before starting the process. You can also
 specify a group by appending a
 .BR : ,
 then the group or gid in the same way
-as you would for the `chown' command (\fIuser\fP\fB:\fP\fIgroup\fP).
+as you would for the \fBchown\fP(1) command (\fIuser\fP\fB:\fP\fIgroup\fP).
 If a user is specified without a group, the primary GID for that user is used.
 When using this option
 you must realize that the primary and supplemental groups are set as well,

man/update-alternatives.1

@@ -138,7 +138,8 @@ option,
 will list all of the choices for the link group
 of which given
 .I name
-is the master alternative name. The current choice is marked with a '*'.
+is the master alternative name.
+The current choice is marked with a \(oq*\(cq.
 You will then be prompted for your choice regarding this link group.
 Depending on the choice made, the link group might no longer be in
 .I auto
@@ -311,7 +312,7 @@ List all master alternative names (those controlling a link group)
 and their status (since version 1.15.0).
 Each line contains up to 3 fields (separated by
 one or more spaces). The first field is the alternative name, the second
-one is the status (either "auto" or "manual"), and the last one contains
+one is the status (either \fBauto\fP or \fBmanual\fP), and the last one contains
 the current choice in the alternative (beware: it's a filename and thus
 might contain spaces).
 .TP