> From: Matthieu Herrb <[email protected]> > Date: Sun, 30 Aug 2015 15:24:13 +0200 > > From: Ingo Schwarze <[email protected]> > > some X manuals use then escape sequence \/ when they want to render > a slash. That's bad because \/ is not a slash but an italic > correction, never producing any output, having no effect at all in > terminal output, and only changing spacing in a minor way in typeset > output. > > Signed-off-by: Matthieu Herrb <[email protected]>
Reviewed-by: Mark Kettenis <[email protected]> > --- > man/X.man | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git man/X.man man/X.man > index 16b4c96..bc9fc1a 100644 > --- man/X.man > +++ man/X.man > @@ -224,7 +224,7 @@ The hostname part of the display name should be the empty > string. > For example: \fI:0\fP, \fI:1\fP, and \fI:0.1\fP. The most efficient > local transport will be chosen. > .TP 8 > -.I TCP\/IP > +.I TCP/IP > .br > The hostname part of the display name should be the server machine's > hostname or IP address. Full Internet names, abbreviated names, IPv4 > @@ -487,7 +487,7 @@ implementation dependent. > If the name is not found, the color is looked up in the > X server's database. > The text form of this database is commonly stored in the file > -\fI\__datadir__/X11/rgb.txt\fP. > +\fI__datadir__/X11/rgb.txt\fP. > .PP > A numerical color specification > consists of a color space name and a set of values in the following syntax: > @@ -1164,7 +1164,7 @@ A wide variety of error messages are generated from > various programs. > The default error handler in \fIXlib\fP (also used by many toolkits) uses > standard resources to construct diagnostic messages when errors occur. The > defaults for these messages are usually stored in > -\fI\__datadir__/X11/XErrorDB\fP. If this file is not present, > +\fI__datadir__/X11/XErrorDB\fP. If this file is not present, > error messages will be rather terse and cryptic. > .PP > When the X Toolkit Intrinsics encounter errors converting resource strings to > -- > 2.4.6 _______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
