ncurses 5.9 - patch 20130720

[ncurses.git] / man / tic.1m

diff --git a/man/tic.1m b/man/tic.1m
index d0d08765504c21c1a09fdcd9bcb00c1b785ec7e2..5c3a63fa9cbd6afcd81e14d59b01a3122a0429e9 100644 (file)
--- a/man/tic.1m
+++ b/man/tic.1m
@@ -26,8 +26,12 @@
 .\" authorization.                                                           *
 .\"***************************************************************************
 .\"
-.\" $Id: tic.1m,v 1.57 2013/02/02 22:09:02 tom Exp $
+.\" $Id: tic.1m,v 1.58 2013/07/20 19:31:25 tom Exp $
 .TH @TIC@ 1M ""
+.ie \n(.g .ds `` \(lq
+.el       .ds `` ``
+.ie \n(.g .ds '' \(rq
+.el       .ds '' ''
 .ds n 5
 .ds d @TERMINFO@
 .de bP
@@ -275,7 +279,7 @@ The debug flag levels are as follows:
 Names of files created and linked
 .TP
 2
-Information related to the ``use'' facility
+Information related to the \*(``use\*('' facility
 .TP
 3
 Statistics from the hashing algorithm
@@ -306,7 +310,7 @@ That is, if you supply a capability name which \fB@TIC@\fP does not recognize,
 it will infer its type (boolean, number or string) from the syntax and
 make an extended table entry for that.
 User-defined capability strings
-whose name begins with ``k'' are treated as function keys.
+whose name begins with \*(``k\*('' are treated as function keys.
 .SS PARAMETERS
 .TP
 \fIfile\fR
@@ -315,7 +319,7 @@ format [see \fBterminfo\fR(\*n)].
 Each description in the file
 describes the capabilities of a particular terminal.
 .IP
-If \fIfile\fR is ``-'', then the data is read from the standard input.
+If \fIfile\fR is \*(``-\*('', then the data is read from the standard input.
 The \fIfile\fR parameter may also be the path of a character-device.
 .SS PROCESSING
 .PP