Bug#726063: Xserver(1): Too long line in the manual and some minor changes
Package: xserver-common
Version: 2:1.12.4-6
Severity: minor
Tags: patch
Dear Maintainer,
From "groff -b -ww -mandoc -z"
<groff: Xserver.1>:504: warning [p 6, 8.2i]: can't break line
Inputfile: /usr/share/man/man1/Xserver.1.gz
Changes:
Use macros "IR" or "RI" for mixed italic and roman strings
Use extra space (\, or \/) between italic and roman letters
Protect full stop at end of abbreviations with '\&'
Remove extra word space or add
Dash for a range is \(en
Use extra small space (\|) around '|' meaning 'or'
Do not hyphenate path names that contain a hyphen
Some cosmetic changes.
Patch:
--- Xserver.1 2013-10-11 01:22:38.000000000 +0000
+++ Xserver.1.new 2013-10-11 18:56:54.000000000 +0000
@@ -39,13 +39,13 @@ frequently a link or a copy of the appro
driving the most frequently used server on a given machine.
.SH "STARTING THE SERVER"
The X server is usually started from the X Display Manager program
-\fIxdm\fP(1) or a similar display manager program.
+\fIxdm\/\fP(1) or a similar display manager program.
This utility is run from the system boot files and takes care of keeping
the server running, prompting for usernames and passwords, and starting up
the user sessions.
.PP
Installations that run more than one window system may need to use the
-\fIxinit\fP(1) utility instead of a display manager. However, \fIxinit\fP is
+\fIxinit\/\fP(1) utility instead of a display manager. However, \fIxinit\fP is
to be considered a tool for building startup scripts and is not
intended for use by end users. Site administrators are \fBstrongly\fP
urged to use a display manager, or build other interfaces for novice users.
@@ -54,7 +54,7 @@ The X server may also be started directl
method is usually reserved for testing and is not recommended for
normal operation. On some platforms, the user must have special
permission to start the X server, often because access to certain
-devices (e.g. \fI/dev/mouse\fP) is restricted.
+devices (e.g.\& \fI/dev/mouse\/\fP) is restricted.
.PP
When the X server starts up, it typically takes over the display. If
you are running on a workstation whose console is the display, you may
@@ -73,11 +73,11 @@ should override values specified via oth
The X server runs as the given \fIdisplaynumber\fP, which by default is 0.
If multiple X servers are to run simultaneously on a host, each must have
a unique display number. See the DISPLAY
-NAMES section of the \fIX\fP(7) manual page to learn how to
+NAMES section of the \fIX\/\fP(7) manual page to learn how to
specify which display number clients should try to use.
.TP 8
.B \-a \fInumber\fP
-sets pointer acceleration (i.e. the ratio of how much is reported to how much
+sets pointer acceleration (i.e.\& the ratio of how much is reported to how much
the user actually moved the pointer).
.TP 8
.B \-ac
@@ -97,18 +97,18 @@ Audit lines are sent as standard error o
.TP 8
.B \-auth \fIauthorization-file\fP
specifies a file which contains a collection of authorization records used
-to authenticate access. See also the \fIxdm\fP(1) and
-\fIXsecurity\fP(7) manual pages.
+to authenticate access. See also the \fIxdm\/\fP(1) and
+\fIXsecurity\/\fP(7) manual pages.
.TP 8
.BI \-background\ none
Asks the driver not to clear the background on startup, if the driver supports that.
-May be useful for smooth transition with eg. fbdev driver.
+May be useful for smooth transition with eg.\& fbdev driver.
For security reasons this is not the default as the screen contents might
show a previous user session.
.TP 8
.B \-br
sets the default root window to solid black instead of the standard root weave
-pattern. This is the default unless -retro or -wr is specified.
+pattern. This is the default unless -retro or -wr is specified.
.TP 8
.B \-bs
disables backing store support on all screens.
@@ -117,7 +117,7 @@ disables backing store support on all sc
turns off key-click.
.TP 8
.B c \fIvolume\fP
-sets key-click volume (allowable range: 0-100).
+sets key-click volume (allowable range: 0\(en100).
.TP 8
.B \-cc \fIclass\fP
sets the visual class for the root window of color screens.
@@ -145,16 +145,16 @@ default state is platform and configurat
disables DPMS (display power management services). The default state
is platform and configuration specific.
.TP 8
-.BI \-extension extensionName
+.BI "\-extension " extensionName
disables named extension. If an unknown extension name is specified,
a list of accepted extension names is printed.
.TP 8
-.BI +extension extensionName
+.BI "+extension " extensionName
enables named extension. If an unknown extension name is specified,
a list of accepted extension names is printed.
.TP 8
.B \-f \fIvolume\fP
-sets beep (bell) volume (allowable range: 0-100).
+sets beep (bell) volume (allowable range: 0\(en100).
.TP 8
.B \-fc \fIcursorFont\fP
sets default cursor font.
@@ -213,7 +213,7 @@ turns off auto-repeat.
.B r
turns on auto-repeat.
.TP 8
-.B -retro
+.B \-retro
starts the stipple with the classic stipple and cursor visible. The default
is to start with a black root window, and to suppress display of the cursor
until the first time an application calls XDefineCursor(). For the Xorg
@@ -227,13 +227,13 @@ sets screen-saver timeout time in minute
disables save under support on all screens.
.TP 8
.B \-seat \fIseat\fP
-seat to run on. Takes a string identifying a seat in a platform
+seat to run on. Takes a string identifying a seat in a platform
specific syntax. On platforms which support this feature this may be
used to limit the server to expose only a specific subset of devices
connected to the system.
.TP 8
.B \-t \fInumber\fP
-sets pointer acceleration threshold in pixels (i.e. after how many pixels
+sets pointer acceleration threshold in pixels (i.e.\& after how many pixels
pointer acceleration should take effect).
.TP 8
.B \-terminate
@@ -276,8 +276,8 @@ pattern.
loads the specified extension at init.
This is a no-op for most implementations.
.TP 8
-.B [+-]xinerama
-enables(+) or disables(-) the XINERAMA extension. The default state is
+.B [+\-]xinerama
+enables(+) or disables(\-) the XINERAMA extension. The default state is
platform and configuration specific.
.SH SERVER DEPENDENT OPTIONS
Some X servers accept the following options:
@@ -298,7 +298,7 @@ A value of zero makes the stack size as
of \-1 leaves the stack space limit unchanged.
.TP 8
.B \-render
-.BR default | mono | gray | color
+.BR default \||\| mono \||\| gray \||\| color
sets the color allocation policy that will be used by the render extension.
.RS 8
.TP 8
@@ -336,7 +336,7 @@ enables XDMCP and sends Query packets to
enable XDMCP and broadcasts BroadcastQuery packets to the network. The
first responding display manager will be chosen for the session.
.TP 8
-.B \-multicast [\fIaddress\fP [\fIhop count\fP]]
+.B \-multicast [\fIaddress\fP [\fIhop count\/\fP]]
Enable XDMCP and multicast BroadcastQuery packets to the network.
The first responding display manager is chosen for the session. If an
address is specified, the multicast is sent to that address. If no
@@ -358,7 +358,7 @@ default. This option must be specified
.B \-from \fIlocal-address\fP
specifies the local address to connect from (useful if the connecting host
has multiple network interfaces). The \fIlocal-address\fP may be expressed
-in any form acceptable to the host platform's \fIgethostbyname\fP(3)
+in any form acceptable to the host platform's \fIgethostbyname\/\fP(3)
implementation.
.TP 8
.B \-once
@@ -379,14 +379,14 @@ data (not that it is very private, being
Yet another XDMCP specific value, this one allows the display manager to
identify each display so that it can locate the shared key.
.SH XKEYBOARD OPTIONS
-X servers that support the XKEYBOARD (a.k.a. \*qXKB\*q) extension accept the
+X servers that support the XKEYBOARD (a.k.a.\& \*qXKB\*q) extension accept the
following options. All layout files specified on the command line must be
located in the XKB base directory or a subdirectory, and specified as the
relative path from the XKB base directory. The default XKB base directory is
.IR /usr/lib/X11/xkb .
.TP 8
-.BR [+-]accessx " [ \fItimeout\fP [ \fItimeout_mask\fP [ \fIfeedback\fP [ \fIoptions_mask\fP ] ] ] ]"
-enables(+) or disables(-) AccessX key sequences.
+.BR [+\-]accessx " [ \fItimeout\fP [ \fItimeout_mask\fP [ \fIfeedback\fP [ \fIoptions_mask\fP ] ] ] ]"
+enables(+) or disables(\-) AccessX key sequences.
.TP 8
.B \-xkbdir \fIdirectory\fP
base directory for keyboard layout files. This option is not available
@@ -407,13 +407,13 @@ loads keyboard description in \fIfilenam
The X server supports client connections via a platform-dependent subset of
the following transport types: TCP\/IP, Unix Domain sockets, DECnet,
and several varieties of SVR4 local connections. See the DISPLAY
-NAMES section of the \fIX\fP(7) manual page to learn how to
+NAMES section of the \fIX\/\fP(7) manual page to learn how to
specify which transport type clients should try to use.
.SH GRANTING ACCESS
The X server implements a platform-dependent subset of the following
authorization protocols: MIT-MAGIC-COOKIE-1, XDM-AUTHORIZATION-1,
XDM-AUTHORIZATION-2, SUN-DES-1, and MIT-KERBEROS-5. See the
-\fIXsecurity\fP(7) manual page for information on the
+\fIXsecurity\/\fP(7) manual page for information on the
operation of these protocols.
.PP
Authorization data required by the above protocols is passed to the
@@ -425,7 +425,7 @@ automatically allowed access to the serv
send one of the authorization records contained in the file in the
connection setup information will be allowed access. See the
\fIXau\fP manual page for a description of the binary format of this
-file. See \fIxauth\fP(1) for maintenance of this file, and distribution
+file. See \fIxauth\/\fP(1) for maintenance of this file, and distribution
of its contents to remote hosts.
.PP
The X server also uses a host-based access control list for deciding
@@ -434,9 +434,9 @@ If no other authorization mechanism is b
this list initially consists of the host on which the server is running as
well as any machines listed in the file \fI/etc/X\fBn\fI.hosts\fR, where
\fBn\fP is the display number of the server. Each line of the file should
-contain either an Internet hostname (e.g. expo.lcs.mit.edu) or a DECnet
-hostname in double colon format (e.g. hydra::) or a complete name in the format
-\fIfamily\fP:\fIname\fP as described in the \fIxhost\fP(1) manual page.
+contain either an Internet hostname (e.g.\& expo.lcs.mit.edu) or a DECnet
+hostname in double colon format (e.g.\& hydra::) or a complete name in the format
+\fIfamily\/\fP:\fIname\fP as described in the \fIxhost\/\fP(1) manual page.
There should be no leading or trailing spaces on any lines. For example:
.sp
.in +8
@@ -452,13 +452,13 @@ local:
Users can add or remove hosts from this list and enable or disable access
control using the \fIxhost\fP command from the same machine as the server.
.PP
-If the X FireWall Proxy (\fIxfwp\fP) is being used without a sitepolicy,
+If the X FireWall Proxy (\fIxfwp\/\fP) is being used without a sitepolicy,
host-based authorization must be turned on for clients to be able to
-connect to the X server via the \fIxfwp\fP. If \fIxfwp\fP is run without
+connect to the X server via the \fIxfwp\/\fP. If \fIxfwp\fP is run without
a configuration file and thus no sitepolicy is defined, if \fIxfwp\fP
is using an X server where xhost + has been run to turn off host-based
authorization checks, when a client tries to connect to this X server
-via \fIxfwp\fP, the X server will deny the connection. See \fIxfwp\fP(1)
+via \fIxfwp\/\fP, the X server will deny the connection. See \fIxfwp\/\fP(1)
for more information about this proxy.
.PP
The X protocol intrinsically does not have any notion of window operation
@@ -466,7 +466,7 @@ permissions or place any restrictions on
connect to a display, it has full run of the screen.
X servers that support the SECURITY extension fare better because clients
can be designated untrusted via the authorization they use to connect; see
-the \fIxauth\fP(1) manual page for details. Restrictions are imposed
+the \fIxauth\/\fP(1) manual page for details. Restrictions are imposed
on untrusted clients that curtail the mischief they can do. See the SECURITY
extension specification for a complete list of these restrictions.
.PP
@@ -498,16 +498,18 @@ is possible.
The X server can obtain fonts from directories and/or from font servers.
The list of directories and font servers
the X server uses when trying to open a font is controlled
-by the \fIfont path\fP.
+by the \fIfont path\/\fP.
.LP
+.na
The default font path is
-/usr/share/fonts/X11/misc,/usr/share/fonts/X11/cyrillic,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,built-ins .
+/usr/share/fonts/X11/misc,\:/usr/share/fonts/X11/cyrillic,\:/usr/share/fonts/X11/100dpi/:unscaled,\:/usr/share/fonts/X11/75dpi/:unscaled,\:/usr/share/fonts/X11/Type1,\:/usr/share/fonts/X11/100dpi,\:/usr/share/fonts/X11/75dpi,\:\%/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,\:built-ins .
+.ad
.LP
-A special kind of directory can be specified using the \fBcatalogue\fP:
-prefix. Directories specified this way can contain symlinks pointing to the
-real font directories. See the FONTPATH.D section for details.
+A special kind of directory can be specified using the \fBcatalogue\/\fP:
+prefix. Directories specified this way can contain symlinks pointing to the
+real font directories. See the FONTPATH.D section for details.
.LP
-The font path can be set with the \fB\-fp\fP option or by \fIxset\fP(1)
+The font path can be set with the \fB\-fp\fP option or by \fIxset\/\fP(1)
after the server has started.
.SH "FONTPATH.D"
You can specify a special kind of font path in the form \fBcatalogue:<dir>\fR.
@@ -515,7 +517,7 @@ The directory specified after the catalo
and each symlink destination will be added as a local fontfile FPE.
.PP
The symlink can be suffixed by attributes such as '\fBunscaled\fR', which
-will be passed through to the underlying fontfile FPE. The only exception is
+will be passed through to the underlying fontfile FPE. The only exception is
the newly introduced '\fBpri\fR' attribute, which will be used for ordering
the font paths specified by the symlinks.
@@ -531,7 +533,7 @@ An example configuration:
This will add /usr/share/X11/fonts/misc as the first FPE with the attribute
\N'39'unscaled', second FPE will be /usr/share/X11/fonts/75dpi, also with
-the attribute 'unscaled' etc. This is functionally equivalent to setting
+the attribute 'unscaled' etc. This is functionally equivalent to setting
the following font path:
.nf
@@ -544,49 +546,49 @@ the following font path:
.SH FILES
.TP 30
-.I /etc/X\fBn\fP.hosts
+.I /etc/X\fBn\/\fP.hosts
Initial access control list for display number \fBn\fP
.TP 30
-.IR /usr/share/fonts/X11/misc , /usr/share/fonts/X11/75dpi , /usr/share/fonts/X11/100dpi
+.IR /usr/share/fonts/X11/misc ", " /usr/share/fonts/X11/75dpi ", " /usr/share/fonts/X11/100dpi
Bitmap font directories
.TP 30
-.IR /usr/share/fonts/X11/TTF , /usr/share/fonts/X11/Type1
+.IR /usr/share/fonts/X11/TTF ", " /usr/share/fonts/X11/Type1
Outline font directories
.TP 30
.I /tmp/.X11-unix/X\fBn\fP
Unix domain socket for display number \fBn\fP
.TP 30
-.I /usr/adm/X\fBn\fPmsgs
-Error log file for display number \fBn\fP if run from \fIinit\fP(8)
+.I /usr/adm/X\fBn\/\fPmsgs
+Error log file for display number \fBn\fP if run from \fIinit\/\fP(8)
.TP 30
.I /usr/lib/X11/xdm/xdm-errors
-Default error log file if the server is run from \fIxdm\fP(1)
+Default error log file if the server is run from \fIxdm\/\fP(1)
.SH "SEE ALSO"
-General information: \fIX\fP(7)
+General information: \fIX\/\fP(7)
.PP
Protocols:
.I "X Window System Protocol,"
.I "The X Font Service Protocol,"
.I "X Display Manager Control Protocol"
.PP
-Fonts: \fIbdftopcf\fP(1), \fImkfontdir\fP(1), \fImkfontscale\fP(1),
-\fIxfs\fP(1), \fIxlsfonts\fP(1), \fIxfontsel\fP(1), \fIxfd\fP(1),
+Fonts: \fIbdftopcf\/\fP(1), \fImkfontdir\/\fP(1), \fImkfontscale\/\fP(1),
+\fIxfs\/\fP(1), \fIxlsfonts\/\fP(1), \fIxfontsel\/\fP(1), \fIxfd\/\fP(1),
.I "X Logical Font Description Conventions"
.PP
-Keyboards: \fIxkeyboard-config\fP(7)
+Keyboards: \fIxkeyboard-config\/\fP(7)
.PP
-Security: \fIXsecurity\fP(7), \fIxauth\fP(1), \fIXau\fP(1),
-\fIxdm\fP(1), \fIxhost\fP(1), \fIxfwp\fP(1),
+Security: \fIXsecurity\/\fP(7), \fIxauth\/\fP(1), \fIXau\/\fP(1),
+\fIxdm\/\fP(1), \fIxhost\/\fP(1), \fIxfwp\/\fP(1),
.I "Security Extension Specification"
.PP
-Starting the server: \fIstartx\fP(1), \fIxdm\fP(1), \fIxinit\fP(1)
+Starting the server: \fIstartx\/\fP(1), \fIxdm\/\fP(1), \fIxinit\/\fP(1)
.PP
-Controlling the server once started: \fIxset\fP(1), \fIxsetroot\fP(1),
-\fIxhost\fP(1), \fIxinput\fP(1), \fIxrandr\fP(1)
+Controlling the server once started: \fIxset\/\fP(1), \fIxsetroot\/\fP(1),
+\fIxhost\/\fP(1), \fIxinput\/\fP(1), \fIxrandr\/\fP(1)
.PP
Server-specific man pages:
-\fIXorg\fP(1), \fIXdmx\fP(1), \fIXephyr\fP(1), \fIXnest\fP(1),
-\fIXvfb\fP(1), \fIXquartz\fP(1), \fIXWin\fP(1).
+\fIXorg\/\fP(1), \fIXdmx\/\fP(1), \fIXephyr\/\fP(1), \fIXnest\/\fP(1),
+\fIXvfb\/\fP(1), \fIXquartz\/\fP(1), \fIXWin\/\fPx(1).
.PP
Server internal documentation:
.I "Definition of the Porting Layer for the X v11 Sample Server"
-- System Information:
Debian Release: 7.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable')
Architecture: i386 (i586)
Kernel: Linux 3.2.46-1-rt67-1
Locale: LANG=is_IS, LC_CTYPE=is_IS (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages xserver-common depends on:
ii x11-common 1:7.7+3~deb7u1
ii x11-xkb-utils 7.7~1
ii xkb-data 2.5.1-3
Versions of packages xserver-common recommends:
ii xauth 1:1.0.7-1
ii xfonts-base 1:1.0.3
xserver-common suggests no packages.
-- no debconf information
--
Bjarni I. Gislason
Reply to: