man: Switch from groff escape sequences to UTF-8

This will make writting and translating the man pages easier.

debian/changelog

@@ -28,6 +28,7 @@ dpkg (1.18.11) UNRELEASED; urgency=medium
       pathnames, the release date and the dpkg suite version. And makes it
       possible to use UTF-8 in the source and convert to the more conservative
       groff escape sequences on the output.
+    - Switch from groff escape sequences to UTF-8 in man pages sources.
   * Build system:
     - Add support for profiling perl modules.
     - Clean up compiler and linker automatic flag usage in configure.

man/deb-changelog.man

@@ -95,7 +95,7 @@ The information here will be copied to the \fBChanged\-By\fP field in the
 when the upload has been installed in the distribution archive.
 .PP
 The \fIdate\fP has the following format (compatible and with the same
-semantics of RFC2822 and RFC5322, or what \(Fodate \-R\(Fc generates):
+semantics of RFC2822 and RFC5322, or what «date \-R» generates):
 .IP
 \fIday-of-week\fP\fB,\fP \fIdd\fP \fImonth\fP \fIyyyy\fP \fIhh\fP\fB:\fP\fImm\fP\fB:\fP\fIss\fP \fB+\fP\fIzzzz\fP
 .PP
@@ -127,15 +127,15 @@ Is the two-digit seconds (\fB00\fP-\fB60\fP).
 .TP
 .RI [\fB+-\fP] zzzz
 Is the time zone offset from Coordinated Universal Time (UTC).
-\(oq\fB+\fP\(cq indicates that the time is ahead of (i.e., east of) UTC and
-\(oq\fB\-\fP\(cq indicates that the time is behind (i.e., west of) UTC.
+‘\fB+\fP’ indicates that the time is ahead of (i.e., east of) UTC and
+‘\fB\-\fP’ indicates that the time is behind (i.e., west of) UTC.
 The first two digits indicate the hour difference from UTC and the last
 two digits indicate the number of additional minutes difference from UTC.
 The last two digits must be in the range \fB00\fP-\fB59\fP.
 .PP
-The first \(lqtitle\(rq line with the package name must start at the left
+The first “title” line with the package name must start at the left
 hand margin.
-The \(lqtrailer\(rq line with the maintainer and date details must be
+The “trailer” line with the maintainer and date details must be
 preceded by exactly one space.
 The maintainer details and the date must be separated by exactly two
 spaces.

man/deb-changes.man

@@ -98,19 +98,19 @@ The currently known values, in increasing order of urgency, are:
 .BR low ", " medium ", " high ", " critical " and " emergency .
 .TP
 .BR Maintainer: " \fIfullname-email\fP (required)"
-Should be in the format \(lqJoe Bloggs <jbloggs@example.org>\(rq, and is
+Should be in the format “Joe Bloggs <jbloggs@example.org>”, and is
 typically the person who created the package, as opposed to the author of
 the software that was packaged.
 .TP
 .BI Changed\-By: " fullname-email"
-Should be in the format \(lqJoe Bloggs <jbloggs@example.org>\(rq, and is
+Should be in the format “Joe Bloggs <jbloggs@example.org>”, and is
 typically the person who prepared the package changes for this release.
 .TP
 .BR Description: " (recommended)"
 .TQ
 .RB " \fIbinary-package-name\fP " \fB\-\fP " \fIbinary-package-summary\fP"
 This multiline field contains a list of binary package names followed by
-a space, a dash (\(oq\fB\-\fP\(cq) and their possibly truncated short
+a space, a dash (‘\fB\-\fP’) and their possibly truncated short
 descriptions.
 .TP
 .BI Closes: " bug-number-list"
@@ -130,7 +130,7 @@ matadata entry.
 This multiline field contains the concatenated text of all changelog
 entries that are part of the upload.
 To make this a valid multiline field empty lines are replaced with a
-single full stop (\(oq.\(cq) and all lines are indented by one space
+single full stop (‘.’) and all lines are indented by one space
 character.
 The exact content depends on the changelog format.
 .TP

man/deb-control.man

@@ -55,7 +55,7 @@ are described in
 .BR deb\-version (5).
 .TP
 .BR Maintainer: " \fIfullname-email\fP (recommended)"
-Should be in the format \(lqJoe Bloggs <jbloggs@foo.com>\(rq, and is typically
+Should be in the format “Joe Bloggs <jbloggs@foo.com>”, and is typically
 the person who created the package, as opposed to the author of the
 software that was packaged.
 .TP
@@ -67,7 +67,7 @@ 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 \(oq\fB.\fP\(cq following the preceding space.
+contain a single ‘\fB.\fP’ following the preceding space.
 .TP
 .BI Section: " section"
 This is a general field that gives the package a category based on the
@@ -161,7 +161,7 @@ different than the name of the package itself.
 If the source version differs from the binary version, then the
 \fIsource-name\fP will be followed by a \fIsource-version\fP in parenthesis.
 This can happen for example on a binary-only non-maintainer upload, or when
-setting a different binary version via \(Fo\fBdpkg\-gencontrol \-v\fP\(Fc.
+setting a different binary version via «\fBdpkg\-gencontrol \-v\fP».
 .TP
 .BI Subarchitecture: " value"
 .TQ
@@ -211,13 +211,13 @@ 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 \(lqpipe\(rq) symbols,
-\(oq\fB|\fP\(cq.
+of packages separated by vertical bar (or “pipe”) symbols,
+‘\fB|\fP’.
 The groups are separated by commas.
-Commas are to be read as \(lqAND\(rq, and pipes as \(lqOR\(rq, with pipes
+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 \(oq\fB:\fP\(cq, optionally followed by a version
+appended after a colon ‘\fB:\fP’, optionally followed by a version
 number specification in parentheses.
 .LP
 An architecture qualifier name can be a real Debian architecture name
@@ -227,12 +227,12 @@ 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 \(oq\fB>>\fP\(cq, in which case any later
+A version number may start with a ‘\fB>>\fP’, 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
+Accepted version relationships are ‘\fB>>\fP’ for greater than,
+‘\fB<<\fP’ for less than, ‘\fB>=\fP’ for greater than or
+equal to, ‘\fB<=\fP’ for less than or equal to, and ‘\fB=\fP’
 for equal to.
 .TP
 .BI Breaks: " package-list"
@@ -269,7 +269,7 @@ In the
 .B Breaks
 and
 .B Conflicts
-fields, the comma should be read as \(lqOR\(rq.
+fields, the comma should be read as “OR”.
 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.
@@ -286,12 +286,12 @@ 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 (\(lqmail\-transport\-agent\(rq) on which
+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 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 \(oq\fB|\fP\(cq to
+know the package names for all of them, and using ‘\fB|\fP’ to
 separate the list.
 .LP
 The syntax of
@@ -309,7 +309,7 @@ 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 \(oq\fB=\fP\(cq
+This field must be a list of source package names with strict ‘\fB=\fP’
 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.man

@@ -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 \(oq . \(cq,
+.RB ‘ . ’,
 that is, the current directory.
 .PP
 The second gzipped tarfile is the filesystem archive, containing

man/deb-origin.man

@@ -26,7 +26,7 @@ The files in \fB%PKGCONFDIR%/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
-\(oq\fB#\fP\(cq.
+‘\fB#\fP’.
 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
@@ -36,7 +36,7 @@ the field.
 The file should be named according to the vendor name.
 The usual convention is to name the vendor file using the vendor name
 in all lowercase, but some variation is permitted.
-Namely, spaces are mapped to dashes (\(oq\fB\-\fP\(cq), and the file
+Namely, spaces are mapped to dashes (‘\fB\-\fP’), and the file
 can have the same casing as the value in \fBVendor\fP field, or it can
 be capitalized.
 .SH FIELDS

man/deb-split.man

@@ -29,23 +29,23 @@ The file names might contain a trailing slash (since dpkg 1.15.6).
 .PP
 The first member is named \fBdebian\-split\fP and contains a series
 of lines, separated by newlines. Currently eight lines are present:
-.IP \(bu 4
+.IP • 4
 The format version number, \fB2.1\fP at the time this manual page was
 written.
-.IP \(bu
+.IP •
 The package name.
-.IP \(bu
+.IP •
 The package version.
-.IP \(bu
+.IP •
 The md5sum of the package.
-.IP \(bu
+.IP •
 The total size of the package.
-.IP \(bu
+.IP •
 The maximum part size.
-.IP \(bu
+.IP •
 The current part number, followed by a slash and the total amount of
-parts (as in \(oq1/10\(cq).
-.IP \(bu
+parts (as in ‘1/10’).
+.IP •
 The package architecture (since dpkg 1.16.1).
 .PP
 Programs which read multi-part archives should be prepared for the minor

man/deb-src-control.man

@@ -25,7 +25,7 @@ deb\-src\-control \- Debian source packages' master control file format
 debian/control
 .
 .SH DESCRIPTION
-Each Debian source package contains the master \(Focontrol\(Fc file,
+Each Debian source package contains the master «control» 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
@@ -42,7 +42,7 @@ 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 \(oq\fB#\fP\(cq are treated as comments.
+Lines starting with a ‘\fB#\fP’ are treated as comments.
 .
 .SH SOURCE FIELDS
 .TP
@@ -55,7 +55,7 @@ long and must start with an alphanumeric character.
 
 .TP
 .BR Maintainer: " \fIfullname-email\fP (recommended)"
-Should be in the format \(FoJoe Bloggs <jbloggs@foo.com>\(Fc, and references the
+Should be in the format «Joe Bloggs <jbloggs@foo.com>», and references the
 person who currently maintains the package, as opposed to the author of the
 software or the original packager.
 
@@ -185,13 +185,13 @@ The syntax of the
 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 \(lqpipe\(rq)
-symbols, \(oq\fB|\fP\(cq.
+Each group is a list of packages separated by vertical bar (or “pipe”)
+symbols, ‘\fB|\fP’.
 The groups are separated by commas.
-Commas are to be read as \(lqAND\(rq, and pipes as \(lqOR\(rq, with pipes
+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 \(oq\fB:\fP\(cq,
+appended after a colon ‘\fB:\fP’,
 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.
@@ -202,8 +202,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 \(lqAND\(rq.
-Specifying alternative packages using a \(lqpipe\(rq is not supported.
+as an “AND”.
+Specifying alternative packages using a “pipe” 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
@@ -220,22 +220,22 @@ 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 \(oq\fB>>\fP\(cq, in which case any
+A version number may start with a ‘\fB>>\fP’, 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
+Accepted version relationships are ‘\fB>>\fP’ for greater than,
+‘\fB<<\fP’ for less than, ‘\fB>=\fP’ for greater than or
+equal to, ‘\fB<=\fP’ for less than or equal to, and ‘\fB=\fP’
 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 \(lqNOT\(rq.
+names, meaning “NOT”.
 
 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 \(lqNOT\(rq.
+and can be prefixed with an exclamation mark, meaning “NOT”.
 A restriction formula represents a disjunctive normal form expression.
 
 Note that dependencies on packages in the

man/deb-symbols.man

@@ -45,11 +45,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 \(lq(>= \fIminimal-version\fR)\(rq or by nothing (if
+a version check like “(>= \fIminimal-version\fR)” 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 \(lqBase\(rq if the library is not versioned) is associated
+\fIversion\fR being “Base” 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
@@ -61,7 +61,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 \(lq\-dev\(rq package associated to the library
+It indicates the name of the “\-dev” 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.man

@@ -42,7 +42,7 @@ The trigger control directives currently supported are:
 .IP
 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 \(lqnoawait\(rq variant does
+directive in the triggers control file. The “noawait” 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.
 .TP
@@ -56,7 +56,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 \(lqnoawait\(rq variant does not put the triggering packages in
+The “noawait” 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.
 .IP
@@ -70,21 +70,21 @@ versions of the package will be activated.
 Unknown directives are an error which will prevent installation of the
 package.
 .PP
-The \(lq\-noawait\(rq variants should always be favored when possible since
+The “\-noawait” 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 \(lq\-noawait\(rq variants are only supported since dpkg 1.16.1, and
+The “\-noawait” 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 \(lqPre\-Depends: dpkg (>= 1.16.1)\(rq to any package that wish to use
+to add a “Pre\-Depends: dpkg (>= 1.16.1)” to any package that wish to use
 those directives.
 .PP
-The \(lq\-await\(rq alias variants are only supported since dpkg 1.17.21, and
+The “\-await” 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 \(lqPre\-Depends: dpkg (>= 1.17.21)\(rq to any package that wish to use
+to add a “Pre\-Depends: dpkg (>= 1.17.21)” to any package that wish to use
 those directives.
 .
 .SH SEE ALSO

man/deb-version.man

@@ -40,7 +40,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 (\(lqupstream\(rq)
+usually the version number of the original (“upstream”)
 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);
@@ -54,7 +54,7 @@ described below. The \fIupstream-version\fP
 portion of the version number is mandatory.
 .IP
 The \fIupstream-version\fP may contain only
-alphanumerics (\(lqA-Za-z0-9\(rq) and the characters
+alphanumerics (“A-Za-z0-9”) and the characters
 .BR . " " + " " \- " " : " " ~
 (full stop, plus, hyphen, colon, tilde) and should
 start with a digit.  If there is no
@@ -75,11 +75,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 \(lqdebianisation\(rq
+Debian package, and so there is only one “debianisation”
 of it and therefore no revision indication is required.
 .IP
 It is conventional to restart the
-\fIdebian-revision\fP at \(oq1\(cq each time the
+\fIdebian-revision\fP at ‘1’ each time the
 \fIupstream-version\fP is increased.
 .IP
 Dpkg will break the version
@@ -103,8 +103,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: \(oq~~\(cq, \(oq~~a\(cq, \(oq~\(cq,
-the empty part, \(oqa\(cq.
+the following parts are in sorted order: ‘~~’, ‘~~a’, ‘~’,
+the empty part, ‘a’.
 .PP
 Then the initial part of the remainder of each string which
 consists entirely of digit characters is determined.  The
@@ -123,7 +123,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 \(oqALPHA\(cq or \(oqpre\-\(cq), or with
+interpret (such as ‘ALPHA’ or ‘pre\-’), or with
 silly orderings.
 .SH NOTES
 The tilde character and its special sorting properties were introduced

man/deb.man

@@ -77,7 +77,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 \(oq . \(cq,
+.RB ‘ . ’,
 the current directory.
 .PP
 The third, last required member is named
@@ -102,7 +102,7 @@ or
 .B data.tar
 and which should be safely ignored by older programs, will have names
 starting with an underscore,
-.RB \(oq _ \(cq.
+.RB ‘ _ ’.
 .PP
 Those new members which won't be able to be safely ignored will be
 inserted before

man/deb822.man

@@ -43,14 +43,14 @@ The ordering of the paragraphs in control files is significant.
 
 Each paragraph consists of a series of data fields.
 Each field consists of the field name followed by a colon
-(U+003A \(oq\fB:\fP\(cq), and then the data/value associated with that field.
+(U+003A ‘\fB:\fP’), and then the data/value associated with that field.
 The field name is composed of US-ASCII characters excluding control
 characters, space, and colon (i.e., characters in the ranges
-U+0021 \(oq\fB!\fP\(cq through U+0039 \(oq\fB9\fP\(cq, and
-U+003B \(oq\fB;\fP\(cq through U+007E \(oq\fB~\fP\(cq, inclusive).
+U+0021 ‘\fB!\fP’ through U+0039 ‘\fB9\fP’, and
+U+003B ‘\fB;\fP’ through U+007E ‘\fB~\fP’, inclusive).
 Field names must not begin with the comment character
-(U+0023 \(oq\fB#\fP\(cq), nor with the hyphen character
-(U+002D \(oq\fB\-\fP\(cq).
+(U+0023 ‘\fB#\fP’), nor with the hyphen character
+(U+002D ‘\fB\-\fP’).
 
 The field ends at the end of the line or at the end of the last continuation
 line (see below).
@@ -118,9 +118,9 @@ Paragraph separators (empty lines) and lines consisting only of
 U+0020 \fBSPACE\fP and U+0009 \fBTAB\fP, are not allowed within field
 values or between fields.
 Empty lines in field values are usually escaped by representing them by a
-U+0020 \fBSPACE\fP followed by a dot (U+002E \(oq\fB.\fP\(cq).
+U+0020 \fBSPACE\fP followed by a dot (U+002E ‘\fB.\fP’).
 
-Lines starting with U+0023 \(oq\fB#\fP\(cq, without any preceding whitespace
+Lines starting with U+0023 ‘\fB#\fP’, without any preceding whitespace
 are comments lines that are only permitted in source package control files
 (\fIdebian/control\fP) and in \fBdeb\-origin\fP(5) files.
 These comment lines are ignored, even between two continuation lines.

man/dpkg-buildflags.man

@@ -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
-(\(lq\fIflag\fP=\fIvalue\fP\(rq). This is the default action.
+(“\fIflag\fP=\fIvalue\fP”). 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
-\(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:
+‘\fB+\fP’ and ‘\fB\-\fP’ modifier.
+For example, to enable the \fBhardening\fP “pie” feature and disable the
+“fortify” 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
-\(lqformat\(rq and \(lqfortify\(rq can be achieved with:
+“format” and “fortify” can be achieved with:
 .P
   export DEB_BUILD_MAINT_OPTIONS=hardening=\-all,+format,+fortify
 .
@@ -277,7 +277,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 \(oq%n\(cq.
+input and contains ‘%n’.
 .
 .TP
 .B fortify
@@ -287,7 +287,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 \(oq%n\(cq are
+Additionally, format strings in writable memory that contain ‘%n’ are
 blocked. If an application depends on such a format string, it will need
 to be worked around.
 

man/dpkg-buildpackage.man

@@ -97,7 +97,7 @@ All long options can be specified both on the command line and in the
 \fBdpkg\-buildpackage\fP system and user configuration files.
 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 \(oq\fB#\fP\(cq).
+it starts with a ‘\fB#\fP’).
 
 .TP
 .BI \-\-build= type

man/dpkg-deb.man

@@ -46,7 +46,7 @@ and run it for you.
 .PP
 For most commands taking an input archive argument, the archive can be
 read from standard input if the archive name is given as a single minus
-character (\(Fo\fB\-\fP\(Fc); otherwise lack of support will be documented in
+character («\fB\-\fP»); otherwise lack of support will be documented in
 their respective command description.
 .
 .SH COMMANDS
@@ -172,7 +172,7 @@ subdirectory of the specified directory (since dpkg 1.16.1).
 The target directory (but not its parents) will be created if necessary.
 
 The input archive is not (currently) processed sequentially, so reading
-it from standard input (\(Fo\fB-\fP\(Fc) is \fBnot\fP supported.
+it from standard input («\fB-\fP») is \fBnot\fP supported.
 .TP
 .BR \-\-ctrl\-tarfile " \fIarchive\fP"
 Extracts the control data from a binary package and sends it to standard
@@ -217,7 +217,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
-\(lq${\fIfield-name\fR}\(rq form, a list of the valid fields can be easily
+“${\fIfield-name\fR}” 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
@@ -225,7 +225,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 \(lq${Package}\\t${Version}\\n\(rq.
+The default for this field is “${Package}\\t${Version}\\n”.
 .TP
 .BI \-z compress-level
 Specify which compression level to use on the compressor backend, when

man/dpkg-divert.man

@@ -37,7 +37,7 @@ 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 \(lqconffiles\(rq) need to be
+or whenever some files (which aren't marked as “conffiles”) need to be
 preserved by \fBdpkg\fP, when installing a newer version of a package which
 contains those files.
 .sp

man/dpkg-gensymbols.man

@@ -35,13 +35,13 @@ so that it ends up included in the control information of the package.
 When generating those files, it uses as input some symbols files
 provided by the maintainer. It looks for the following files (and uses the
 first that is found):
-.IP \(bu 4
+.IP • 4
 debian/\fIpackage\fR.symbols.\fIarch\fR
-.IP \(bu 4
+.IP • 4
 debian/symbols.\fIarch\fR
-.IP \(bu 4
+.IP • 4
 debian/\fIpackage\fR.symbols
-.IP \(bu 4
+.IP • 4
 debian/symbols
 .P
 The main interest of those files is to provide the minimal version
@@ -74,16 +74,16 @@ 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 \(oq\fB~\fP\(cq.
+with ‘\fB~\fP’.
 .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 \(oq#\(cq as
-the first character is a comment except if it starts with \(oq#include\(cq
+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 \(oq#MISSING:\(cq are special comments documenting
+Lines starting with ‘#MISSING:’ are special comments documenting
 symbols that have disappeared.
 .P
 Do not forget to check if old symbol versions need to be increased.
@@ -151,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 \(lqexisting\(rq
+reappears in the next revision, it will be upgraded back to the “existing”
 status with its minimum version unchanged.
 
 This tag is useful for symbols which are private where their disappearance do
@@ -357,13 +357,13 @@ alphanumerical order of their names.
 When the set of exported symbols differ between architectures, it may become
 inefficient to use a single symbol file. In those cases, an include directive
 may prove to be useful in a couple of ways:
-.IP \(bu 4
+.IP • 4
 You can factorize the common part in some external file
 and include that file in your \fIpackage\fR.symbols.\fIarch\fR file by
 using an include directive like this:
 
 #include "\fIpackages\fR.symbols.common"
-.IP \(bu
+.IP •
 The include directive may also be tagged like any symbol:
 
 (tag|...|tagN)#include "file-to-include"
@@ -397,14 +397,14 @@ to do it is the following:
 .SS Good library management
 .P
 A well-maintained library has the following features:
-.IP \(bu 4
+.IP • 4
 its API is stable (public symbols are never dropped, only new public
 symbols are added) and changes in incompatible ways only when the SONAME
 changes;
-.IP \(bu 4
+.IP • 4
 ideally, it uses symbol versioning to achieve ABI stability despite
 internal changes and API extension;
-.IP \(bu 4
+.IP • 4
 it doesn't export private symbols (such symbols can be tagged optional as
 workaround).
 .P

man/dpkg-maintscript-helper.man

@@ -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 \(lqMulti\-Arch: same\(rq this parameter
+The package name. When the package is “Multi\-Arch: same” 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-mergechangelogs.man

@@ -37,8 +37,8 @@ part of the version number after the last tilde is dropped so that
 1.0\-1~exp1 and 1.0\-1~exp5 are considered to be the same entry. When the
 same version is available in both \fInew-a\fP and \fInew-b\fP, a standard
 line-based 3-way merge is attempted (provided that the module
-Algorithm::Merge is available \[em] it's part of the package
-libalgorithm\-merge\-perl \[em] otherwise you get a global conflict on the
+Algorithm::Merge is available — it's part of the package
+libalgorithm\-merge\-perl — otherwise you get a global conflict on the
 content of the entry).
 .
 .SH OPTIONS

man/dpkg-name.man

@@ -57,10 +57,10 @@ 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
-\(Founstable/binary\-\fIarchitecture\fP/\fIsection\fP\(Fc.
+«unstable/binary\-\fIarchitecture\fP/\fIsection\fP».
 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 target directory is «\fIsection\fP/binary\-\fIarchitecture\fP».
 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.
@@ -93,12 +93,12 @@ 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 \fBbar\-foo.deb\fP).
 .TP
-.B find /root/debian/ \-name \(aq*.deb\(aq | xargs \-n 1 dpkg\-name \-a
+.B find /root/debian/ \-name '*.deb' | xargs \-n 1 dpkg\-name \-a
 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
-.B find \-name \(aq*.deb\(aq | xargs \-n 1 dpkg\-name \-a \-o \-s \-c
+.B find \-name '*.deb' | xargs \-n 1 dpkg\-name \-a \-o \-s \-c
 .B Don't do this.
 Your archive will be messed up completely because a lot of packages
 don't come with section information.

man/dpkg-parsechangelog.man

@@ -37,7 +37,7 @@ form.
 .TP
 .BR \-l " \fIchangelog-file\fP"
 Specifies the changelog file to read information from.
-A \(oq\-\(cq can be used to specify reading from standard input.
+A ‘\-’ can be used to specify reading from standard input.
 The default is
 .BR debian/changelog .
 .TP
@@ -68,7 +68,7 @@ of the output.
 .TP
 .BI \-\-file " file"
 Set the changelog filename to parse.
-Default is \(oq-\(cq (standard input).
+Default is ‘-’ (standard input).
 .TP
 .BR \-l ", " \-\-label " \fIfile\fP"
 Set the name of the changelog file to use in error messages, instead
@@ -162,7 +162,7 @@ a parser for that alternative format.
 
 In order to have \fBdpkg\-parsechangelog\fP run the new parser, a line must
 be included within the last 40 lines of the changelog file, matching the Perl
-regular expression: \(lq\fB\\schangelog-format:\\s+([0-9a-z]+)\\W\fP\(rq.
+regular expression: “\fB\\schangelog-format:\\s+([0-9a-z]+)\\W\fP”.
 The part in parentheses should be the name of the format. For example:
 
        @@@ changelog-format: \fIotherformat\fP @@@

man/dpkg-query.man

@@ -43,7 +43,7 @@ filename expansion. For example this will list all package names starting
 with \*(lqlibc6\*(rq:
 
 .nf
-  \fBdpkg\-query \-l \(aqlibc6*\(aq\fP
+  \fBdpkg\-query \-l 'libc6*'\fP
 .fi
 
 The first three columns of the output show the desired action, the package
@@ -137,12 +137,12 @@ asterisk (\fB*\fP) and question mark (\fB?\fP) will match a slash,
 and blackslash (\fB\\\fP) will be used as an escape character.
 
 If the first character in the \fIfilename-search-pattern\fP is none of
-\(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’ then it will be considered a substring match and will be
+implicitly surrounded by ‘\fB*\fP’ (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.
+If the subsequent string contains any of ‘\fB*[?\\\fP’, then it will
+handled like a glob pattern, otherwise any trailing ‘\fB/\fP’ or
+‘\fB/.\fP’ 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.
@@ -180,7 +180,7 @@ This option is used to specify the format of the output \fB\-\-show\fP
 will produce. The format is a string that will be output for each package
 listed.
 
-In the format string, \(lq\fB\e\fP\(rq introduces escapes:
+In the format string, “\fB\e\fP” introduces escapes:
 
 .nf
     \fB\en\fP  newline
@@ -188,13 +188,13 @@ In the format string, \(lq\fB\e\fP\(rq introduces escapes:
     \fB\et\fP  tab
 .fi
 
-\(lq\fB\e\fP\(rq before any other character suppresses any special
-meaning of the following character, which is useful for \(lq\fB\e\fP\(rq
-and \(lq\fB$\fP\(rq.
+“\fB\e\fP” before any other character suppresses any special
+meaning of the following character, which is useful for “\fB\e\fP”
+and “\fB$\fP”.
 
 Package information can be included by inserting
 variable references to package fields using the syntax
-\(lq\fB${\fP\fIfield\fR[\fB;\fP\fIwidth\fR]\fB}\fP\(rq. Fields are
+“\fB${\fP\fIfield\fR[\fB;\fP\fIwidth\fR]\fB}\fP”. Fields are
 printed right-aligned unless the width is negative in which case left
 alignment will be used. The following \fIfield\fRs are recognized but
 they are not necessarily available in the status file (only internal
@@ -243,7 +243,7 @@ fields in control files):
 .TP
 .B binary:Package
 It contains the binary package name with a possible architecture qualifier
-like \(lqlibc6:amd64\(rq (since dpkg 1.16.2).
+like “libc6:amd64” (since dpkg 1.16.2).
 An architecture qualifier will be present to make the package name unambiguous,
 for example if the package has a \fBMulti\-Arch\fP field with a value of
 \fBsame\fP or the package is of a foreign architecture.
@@ -253,7 +253,7 @@ It contains the package short description (since dpkg 1.16.2).
 .TP
 .B db:Status\-Abbrev
 It contains the abbreviated package status (as three characters),
-such as \(lqii \(rq or \(lqiHR\(rq (since dpkg 1.16.2).
+such as “ii ” or “iHR” (since dpkg 1.16.2).
 See the \fB\-\-list\fP command description for more details.
 .TP
 .B db:Status\-Want
@@ -277,14 +277,14 @@ It contains the source package version for this binary package
 (since dpkg 1.16.2)
 .RE
 .IP
-The default format string is \(lq\fB${binary:Package}\et${Version}\en\fP\(rq.
+The default format string is “\fB${binary:Package}\et${Version}\en\fP”.
 Actually, all other fields found in the status file (i.e. user defined
 fields) can be requested, too. They will be printed as-is, though, no
 conversion nor error checking is done on them. To get the name of the
 \fBdpkg\fP maintainer and the installed version, you could run:
 
 .nf
-  \fBdpkg\-query \-W \-f=\(aq${binary:Package} ${Version}\\t${Maintainer}\\n\(aq dpkg\fP
+  \fBdpkg\-query \-W \-f='${binary:Package} ${Version}\\t${Maintainer}\\n' dpkg\fP
 .fi
 .
 .SH EXIT STATUS

man/dpkg-shlibdeps.man

@@ -81,7 +81,7 @@ other binary packages.
 Per-system overriding shared library dependency information.
 \fIarch\fR is the architecture of the current system (obtained by
 .BR "dpkg\-architecture \-qDEB_HOST_ARCH" ).
-.IP "Output from \(lq\fBdpkg\-query \-\-control\-path\fR \fIpackage\fR symbols\(rq"
+.IP "Output from “\fBdpkg\-query \-\-control\-path\fR \fIpackage\fR symbols”"
 Package-provided shared library dependency information.
 Unless overridden by \fB\-\-admindir\fP, those files are located in
 %ADMINDIR%.
@@ -116,7 +116,7 @@ Shared library information generated by the current build process that also invo
 They are only used if the library is found in a package's build tree. The
 shlibs file in that build tree takes precedence over shlibs files from
 other binary packages.
-.IP "Output from \(lq\fBdpkg\-query \-\-control\-path\fP \fIpackage\fR shlibs\(rq"
+.IP "Output from “\fBdpkg\-query \-\-control\-path\fP \fIpackage\fR shlibs”"
 Package-provided shared library dependency information.
 Unless overridden by \fB\-\-admindir\fP, those files are located in
 %ADMINDIR%.
@@ -247,10 +247,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 \(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.
+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”.
 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.man

@@ -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 \(lq1.0\(rq), its name will be stored in
+formats except “1.0”), 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,8 +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,
-\(lq1.0\(rq.
-The fallback to \(lq1.0\(rq is deprecated and will be removed at some
+“1.0”.
+The fallback to “1.0” 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.
@@ -210,12 +210,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. \(oq(^|/)\(cq, \(oq($|/)\(cq) yourself.
+the necessary anchors (e.g. ‘(^|/)’, ‘($|/)’) 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 \(lq\fB|\fP\fIregex\fP\(rq to the existing value.
+It does this by concatenating “\fB|\fP\fIregex\fP” 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
@@ -283,7 +283,7 @@ 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 \(lq3.0 (quilt)\(rq or \(lq3.0 (native)\(rq.
+either “3.0 (quilt)” or “3.0 (native)”.
 See https://wiki.debian.org/Projects/DebSrc3.0 for information on the
 deployment of those formats within Debian.
 
@@ -311,7 +311,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 \(lq.orig\(rq directory and
+extracting the original tarball in a separate “.orig” directory and
 regenerating the \fB.diff.gz\fP by comparing the source package
 \fIdirectory\fP with the .orig directory.
 
@@ -440,10 +440,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 \(lq3.0 (quilt)\(rq replaces it.
+usage, the format “3.0 (quilt)” 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 \(lq3.0 (quilt)\(rq format
+The behaviour of this format is the same as the “3.0 (quilt)” 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.
@@ -467,7 +467,7 @@ an original tarball (\fB.orig.tar.\fP\fIext\fP where \fIext\fP can be
 (\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
-(\(oq\-\(cq).
+(‘\-’).
 Optionally each original tarball can be accompanied by a detached
 upstream signature (\fB.orig.tar.\fP\fIext\fP\fB.asc\fP and
 \fB.orig\-\fP\fIcomponent\fP\fB.tar.\fP\fIext\fP\fB.asc\fP), extraction
@@ -619,7 +619,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 \(lqmain\(rq software.
+software and where there's no “main” software.
 .TP
 .B \-\-no\-unapply\-patches, \-\-unapply\-patches
 By default, \fBdpkg\-source\fP will automatically unapply the patches in the
@@ -669,7 +669,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 \(lq3.0 (custom)\(rq.
+and not “3.0 (custom)”.
 .
 .SS Format: 3.0 (git)
 Supported since dpkg 1.14.17.
@@ -688,7 +688,7 @@ 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 \(lqmaster\(rq, but it could be anything.)
+(Typically “master”, but it could be anything.)
 Any other branches will be available under \fIremotes/origin/\fP.
 .PP
 .B Building
@@ -736,22 +736,22 @@ 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 \(lq1.0\(rq is
+desired source format. For backwards compatibility, format “1.0” 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 \(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.
+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.
 If you want to continue using the old format, you should be explicit about
-it and put \(lq1.0\(rq in \fBdebian/source/format\fP.
+it and put “1.0” in \fBdebian/source/format\fP.
 .SS the diff modifies the following upstream files
-When using source format \(lq1.0\(rq it is usually a bad idea to modify
+When using source format “1.0” 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 \(lq3.0 (quilt)\(rq that offers
+this complexity you can also use the format “3.0 (quilt)” that offers
 this natively.
 .SS cannot represent change to \fIfile\fP
 Changes to upstream sources are usually stored with patch files, but not
@@ -778,7 +778,7 @@ 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 \(oq\fB#\fP\(cq are comments and are skipped.
+Lines starting with ‘\fB#\fP’ 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
@@ -788,10 +788,10 @@ 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 \(oq\fB#\fP\(cq are ignored.
-The leading \(oq\fB\-\-\fP\(cq should be stripped and short options are
+starting with ‘\fB#\fP’ are ignored.
+The leading ‘\fB\-\-\fP’ should be stripped and short options are
 not allowed.
-Optional spaces are allowed around the \(oq\fB=\fP\(cq symbol and optional
+Optional spaces are allowed around the ‘\fB=\fP’ symbol and optional
 quotes are allowed around the value.
 Here's an example of such a file:
 .P
@@ -812,18 +812,18 @@ 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 \(lq2.0\(rq or \(lq3.0 (quilt)\(rq. \fBlocal\-patch\-header\fP is not
+in formats “2.0” or “3.0 (quilt)”. \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 \(oq\fB#\fP\(cq are comments and are skipped.
+Lines starting with ‘\fB#\fP’ 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 \(oq\fB#\fP\(cq preceded by one or more spaces (which marks the
+or the first ‘\fB#\fP’ 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

man/dpkg-statoverride.man

@@ -25,7 +25,7 @@ dpkg\-statoverride \- override ownership and mode of files
 .RI [ option "...] " command
 .
 .SH DESCRIPTION
-\(lq\fBstat overrides\fR\(rq are a way to tell
+“\fBstat overrides\fR” 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,7 +46,7 @@ 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
-\(oq\fB#\fR\(cq (for example \fB#0\fR or \fB#65534\fR).
+‘\fB#\fR’ (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
@@ -111,7 +111,7 @@ is located in the \fBdpkg\fP administration directory, along with other files
 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 \(lq\-old\(rq, before replacing it with the new one.
+extension “\-old”, before replacing it with the new one.
 .
 .SH SEE ALSO
 .BR dpkg (1).

man/dpkg.cfg.man

@@ -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 (\(oq\fB#\fR\(cq).
+allowed by starting a line with a hash sign (‘\fB#\fR’).
 .
 .SH FILES
 .I %PKGCONFDIR%/dpkg.cfg.d/[0-9a-zA-Z_-]*

man/dpkg.man

@@ -264,8 +264,8 @@ available. With action \fB\-\-merge\-avail\fP, old information is
 combined with information from \fIPackages-file\fP. With action
 \fB\-\-update\-avail\fP, old information is replaced with the information
 in the \fIPackages-file\fP. The \fIPackages-file\fP distributed with
-Debian is simply named \(Fo\fIPackages\fP\(Fc. If the \fIPackages-file\fP
-argument is missing or named \(Fo\fB\-\fP\(Fc then it will be read from
+Debian is simply named «\fIPackages\fP». If the \fIPackages-file\fP
+argument is missing or named «\fB\-\fP» then it will be read from
 standard input (since dpkg 1.17.7). \fBdpkg\fP keeps its record of
 available packages in \fI%ADMINDIR%/available\fP.
 
@@ -295,9 +295,9 @@ not be shown.
 .TP
 .B \-\-set\-selections
 Set package selections using file read from stdin. This file should be
-in the format \(lq\fIpackage\fP \fIstate\fP\(rq, where state is one of
+in the format “\fIpackage\fP \fIstate\fP”, where state is one of
 \fBinstall\fP, \fBhold\fP, \fBdeinstall\fP or \fBpurge\fP. Blank lines
-and comment lines beginning with \(oq\fB#\fP\(cq are also permitted.
+and comment lines beginning with ‘\fB#\fP’ 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
@@ -341,7 +341,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, \(lqi386\(rq).
+Print architecture of packages \fBdpkg\fP installs (for example, “i386”).
 .TP
 .B \-\-print\-foreign\-architectures
 Print a newline-separated list of the extra architectures \fBdpkg\fP is
@@ -451,10 +451,10 @@ See \fBdpkg\-query\fP(1) for more information about the following actions.
 .SH OPTIONS
 All options can be specified both on the command line and in the \fBdpkg\fP
 configuration file \fI%PKGCONFDIR%/dpkg.cfg\fP or fragment files (with names
-matching this shell pattern \(aq[0-9a-zA-Z_-]*\(aq) on the configuration
+matching this shell pattern '[0-9a-zA-Z_-]*') on the configuration
 directory \fI%PKGCONFDIR%/dpkg.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 \(oq\fB#\fP\(cq).
+without leading hyphens) or a comment (if it starts with a ‘\fB#\fP’).
 .br
 .TP
 \fB\-\-abort\-after=\fP\fInumber\fP
@@ -517,7 +517,7 @@ Configure also any unpacked but unconfigured packages on which the current
 package depends.
 
 \fBhold\fP:
-Process packages even when marked \(lqhold\(rq.
+Process packages even when marked “hold”.
 
 \fBremove\-reinstreq\fP:
 Remove a package, even if it's broken and marked to require
@@ -650,18 +650,18 @@ installed. This is an alias of \fB\-\-refuse\-downgrade\fP.
 .BI \-\-admindir= dir
 Change default administrative directory, which contains many files that
 give information about status of installed or uninstalled packages, etc.
-(Defaults to \(Fo\fI%ADMINDIR%\fP\(Fc)
+(Defaults to «\fI%ADMINDIR%\fP»)
 .TP
 .BI \-\-instdir= dir
 Change default installation directory which refers to the directory where
 packages are to be installed. \fBinstdir\fP is also the directory passed
 to \fBchroot\fP(2) before running package's installation scripts, which
 means that the scripts see \fBinstdir\fP as a root directory.
-(Defaults to \(Fo\fI/\fP\(Fc)
+(Defaults to «\fI/\fP»)
 .TP
 .BI \-\-root= dir
-Changing \fBroot\fP changes \fBinstdir\fP to \(Fo\fIdir\fP\(Fc and
-\fBadmindir\fP to \(Fo\fIdir\fP\fB%ADMINDIR%\fP\(Fc.
+Changing \fBroot\fP changes \fBinstdir\fP to «\fIdir\fP» and
+\fBadmindir\fP to «\fIdir\fP\fB%ADMINDIR%\fP».
 .TP
 \fB\-O\fP, \fB\-\-selected\-only\fP
 Only process the packages that are selected for installation. The
@@ -699,12 +699,12 @@ previously excluded paths matching the specified patterns during install
 might completely break your system, use with caution.\fP
 
 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
+‘*’ 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 ‘[’
 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
@@ -744,13 +744,13 @@ 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 \(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
+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 failure (the file contents have changed) is denoted with
-a \(oq\fB5\fP\(cq on the third character.
+a ‘\fB5\fP’ 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.
+‘\fBc\fP’ for conffiles), another space and the pathname.
 .TP
 \fB\-\-status\-fd \fR\fIn\fR
 Send machine-readable package status and progress information to file
@@ -925,7 +925,7 @@ name of the script running, one of \fBpreinst\fP, \fBpostinst\fP,
 .TP
 .B DPKG_MAINTSCRIPT_DEBUG
 Defined by \fBdpkg\fP on the maintainer script environment to a value
-(\(oq\fB0\fP\(cq or \(oq\fB1\fP\(cq) noting whether debugging has been
+(‘\fB0\fP’ or ‘\fB1\fP’) noting whether debugging has been
 requested (with the \fB\-\-debug\fP option) for the maintainer scripts
 (since dpkg 1.18.4).
 .
@@ -981,7 +981,7 @@ To list installed packages related to the editor \fBvi\fP(1) (note that
 default, and the \fBdpkg\-query\fP \fB\-\-load\-avail\fP option should
 be used instead for that):
 .br
-\fB     dpkg \-l \(aq*vi*\(aq\fP
+\fB     dpkg \-l '*vi*'\fP
 .br
 
 To see the entries in \fI%ADMINDIR%/available\fP of two packages:

man/dsc.man

@@ -96,7 +96,7 @@ The exact format and sorting algorithm are described in
 The name of the distribution this package is originating from.
 .TP
 .BR Maintainer: " \fIfullname-email\fP (recommended)"
-Should be in the format \(lqJoe Bloggs <jbloggs@foo.com>\(rq, and is
+Should be in the format “Joe Bloggs <jbloggs@foo.com>”, and is
 typically the person who created the package, as opposed to the author
 of the software that was packaged.
 .TP
@@ -185,12 +185,12 @@ and the currently known optional keys are:
 .TP
 .B arch
 The architecture restriction from the binary package \fBArchitecture\fP
-field, with spaces converted to \(oq,\(cq.
+field, with spaces converted to ‘,’.
 .TP
 .B profile
 The normalized build-profile restriction formula from the binary package
-\fBBuild\-Profile\fP field, with ORs converted to \(oq+\(cq and ANDs to
-\(oq,\(cq.
+\fBBuild\-Profile\fP field, with ORs converted to ‘+’ and ANDs to
+‘,’.
 .TP
 .B essential
 If the binary package is essential, this key will contain the value of the

man/dselect.cfg.man

@@ -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 (\(oq\fB#\fR\(cq).
+allowed by starting a line with a hash sign (‘\fB#\fR’).
 .
 .SH FILES
 .I %PKGCONFDIR%/dselect.cfg.d/[0-9a-zA-Z_-]*

man/dselect.man

@@ -60,12 +60,12 @@ configuration file \fI%PKGCONFDIR%/dselect.cfg\fP or the files on the
 configuration directory \fI%PKGCONFDIR%/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 \(oq\fB#\fR\(cq).
+with a ‘\fB#\fR’).
 .br
 .TP
 .BI \-\-admindir " directory"
-Changes the directory where the dpkg \(oq\fIstatus\fP\(cq,
-\(oq\fIavailable\fP\(cq and similar files are located.
+Changes the directory where the dpkg ‘\fIstatus\fP’,
+‘\fIavailable\fP’ and similar files are located.
 This defaults to \fI%ADMINDIR%\fP
 and normally there shouldn't be any need to change it.
 .TP
@@ -129,7 +129,7 @@ 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 (\(oq+\(cq) characters.
+separated by plus (‘+’) characters.
 Available attributes include (not all of these will work on all terminals):
 .BR normal ", " standout ", " underline ", " reverse ", " blink ", "
 .BR bright ", " dim ", " bold
@@ -246,7 +246,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 \(oq\fB?\fP\(cq key.
+The online help screens can at any time be invoked with the ‘\fB?\fP’ key.
 .sp
 .SS Screen layout
 .sp
@@ -257,14 +257,14 @@ 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 \(oq\fBI\fP\(cq key toggles a full-screen display of the packages
+Pressing the ‘\fBI\fP’ 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 \(oq\fBi\fP\(cq key.
+The type of detail can be toggled by pressing the ‘\fBi\fP’ key.
 This alternates between:
  - the extended description
  - the control information for the installed version
@@ -283,11 +283,11 @@ 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 \(oq\fBA\fP\(cq key, the display of the installed and
+By pressing the ‘\fBA\fP’ 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
+By pressing the ‘\fBV\fP’ 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
+By pressing the ‘\fBv\fP’ key, the package status display is toggled
 between verbose and shorthand.
 Shorthand display is the default.
 .sp
@@ -341,21 +341,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 \(oq\fB/\fP\(cq, and typing a simple search
+is done by pressing ‘\fB/\fP’, and typing a simple search
 string. The string is interpreted as a
 .BR regex (7)
 regular expression.
-If you add \(oq\fB/d\fP\(cq to the search expression, dselect will also
+If you add ‘\fB/d\fP’ 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.
+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
-\(oq\fBn\fP\(cq or \(oq\fB\\\fP\(cq keys, until the wanted package is found.
+‘\fBn\fP’ or ‘\fB\\\fP’ 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 \(oq\fBo\fP\(cq and \(oq\fBO\fP\(cq keys repeatedly.
+the ‘\fBo\fP’ and ‘\fBO\fP’ keys repeatedly.
 The following nine sort orderings can be selected:
  alphabet          available           status
  priority+section  available+priority  status+priority
@@ -410,11 +410,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 \(oq\fBR\fP\(cq key.
-By pressing the \(oq\fBD\fP\(cq key, the automatic suggestions are reset,
+were created, by pressing the ‘\fBR\fP’ key.
+By pressing the ‘\fBD\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 \(oq\fBU\fP\(cq, the selections are again set to the
+Finally, by pressing ‘\fBU\fP’, the selections are again set to the
 automatic suggestion values.
 .sp
 .SS Establishing the requested selections
@@ -426,21 +426,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 \(oq\fBQ\fP\(cq
+conflicts and forcing \fBdselect\fP to accept it, press the ‘\fBQ\fP’
 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 \(oq\fBX\fP\(cq or \fBescape\fP keys. By repeatedly pressing these
+the ‘\fBX\fP’ 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
-\(oq\fBC\fP\(cq key.
+‘\fBC\fP’ 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/po/po4a.cfg

@@ -2,7 +2,7 @@
 [po4a_paths] po/dpkg-man.pot $lang:po/$lang.po
 
 # Make sure the man pages are generated with the right encoding.
-[po4a_alias:man] man opt:"-L UTF-8 -A UTF-8"
+[po4a_alias:man] man opt:"-M UTF-8 -L UTF-8 -A UTF-8"
 
 [type:man] deb.man $lang:$lang/deb.man \
            add_$lang:po/$lang.add

man/update-alternatives.man

@@ -139,7 +139,7 @@ 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 \(oq*\(cq.
+The current choice is marked with a ‘*’.
 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
@@ -289,7 +289,7 @@ Call \fB\-\-config\fP on all alternatives. It can be usefully combined with
 \fB\-\-skip\-auto\fP to review and configure all alternatives which are
 not configured in automatic mode. Broken alternatives are also displayed.
 Thus a simple way to fix all broken alternatives is to call
-\fByes \[aq]\[aq] | update\-alternatives \-\-force \-\-all\fR.
+\fByes '' | update\-alternatives \-\-force \-\-all\fR.
 .TP
 \fB\-\-auto\fR \fIname\fR
 Switch the link group behind the alternative for