ncurses 5.7 - patch 20100918

[ncurses.git] / man / terminfo.tail

diff --git a/man/terminfo.tail b/man/terminfo.tail
index fc6af2e03508a67e74b8bd09369a0669f3c101b1..41b3348b33437bf27d93acf41b671d3e5eb2d2bf 100644 (file)
--- a/man/terminfo.tail
+++ b/man/terminfo.tail
@@ -1,9 +1,11 @@
-.\" $Id: terminfo.tail,v 1.38 2003/01/05 22:47:05 tom Exp $
+.\" $Id: terminfo.tail,v 1.51 2010/07/31 16:02:40 tom Exp $

 .\" Beginning of terminfo.tail file
 .\" Beginning of terminfo.tail file

+.\" This file is part of ncurses.
+.\" See "terminfo.head" for copyright.

 .ps +1
 .ps +1

-.PP
+.

 .SS A Sample Entry
 .SS A Sample Entry

-.PP
+.

 The following entry, describing an ANSI-standard terminal, is representative
 of what a \fBterminfo\fR entry for a modern terminal typically looks like.
 .PP
 The following entry, describing an ANSI-standard terminal, is representative
 of what a \fBterminfo\fR entry for a modern terminal typically looks like.
 .PP


@@ -23,7 +25,7 @@ of what a \fBterminfo\fR entry for a modern terminal typically looks like.
         kf11=\\E[W, kf12=\\E[X, kf2=\\E[N, kf3=\\E[O, kf4=\\E[P,
         kf5=\\E[Q, kf6=\\E[R, kf7=\\E[S, kf8=\\E[T, kf9=\\E[U,
         kich1=\\E[L, mc4=\\E[4i, mc5=\\E[5i, nel=\\r\\E[S,
         kf11=\\E[W, kf12=\\E[X, kf2=\\E[N, kf3=\\E[O, kf4=\\E[P,
         kf5=\\E[Q, kf6=\\E[R, kf7=\\E[S, kf8=\\E[T, kf9=\\E[U,
         kich1=\\E[L, mc4=\\E[4i, mc5=\\E[5i, nel=\\r\\E[S,

-        op=\\E[37;40m, rep=%p1%c\\E[%p2%{1}%-%db,
+        op=\\E[37;40m, rep=%p1%c\\E[%p2%{1}%\-%db,

         rin=\\E[%p1%dT, s0ds=\\E(B, s1ds=\\E)B, s2ds=\\E*B,
         s3ds=\\E+B, setab=\\E[4%p1%dm, setaf=\\E[3%p1%dm,
         setb=\\E[4%?%p1%{1}%=%t4%e%p1%{3}%=%t6%e%p1%{4}%=%t1%e%p1%{6}%=%t3%e%p1%d%;m,
         rin=\\E[%p1%dT, s0ds=\\E(B, s1ds=\\E)B, s2ds=\\E*B,
         s3ds=\\E+B, setab=\\E[4%p1%dm, setaf=\\E[3%p1%dm,
         setb=\\E[4%?%p1%{1}%=%t4%e%p1%{3}%=%t6%e%p1%{4}%=%t1%e%p1%{6}%=%t3%e%p1%d%;m,


@@ -271,22 +273,22 @@ Thus the model 33 teletype is described as
 .DT
 .nf
 .ft CW
 .DT
 .nf
 .ft CW

-.in -7
-       \s-133\||\|tty33\||\|tty\||\|model 33 teletype,
+.\".in -2
+\s-133\||\|tty33\||\|tty\||\|model 33 teletype,

        bel=^G, cols#72, cr=^M, cud1=^J, hc, ind=^J, os,\s+1
        bel=^G, cols#72, cr=^M, cud1=^J, hc, ind=^J, os,\s+1

-.in +7
+.\".in +2

 .ft R
 .PP
 .ft R
 .PP

-while the Lear Siegler \s-1ADM\-3\s0 is described as
+while the Lear Siegler \s-1ADM-3\s0 is described as

 .PP
 .DT
 .nf
 .ft CW
 .PP
 .DT
 .nf
 .ft CW

-.in -7
-       \s-1adm3\||\|3\||\|lsi adm3,
+.\".in -2
+\s-1adm3\||\|3\||\|lsi adm3,

        am, bel=^G, clear=^Z, cols#80, cr=^M, cub1=^H, cud1=^J,
        ind=^J, lines#24,\s+1
        am, bel=^G, clear=^Z, cols#80, cr=^M, cub1=^H, cud1=^J,
        ind=^J, lines#24,\s+1

-.in +7
+.\".in +2

 .ft R
 .fi
 .PP
 .ft R
 .fi
 .PP


@@ -295,7 +297,7 @@ while the Lear Siegler \s-1ADM\-3\s0 is described as
 Cursor addressing and other strings requiring parameters
 in the terminal are described by a
 parameterized string capability, with
 Cursor addressing and other strings requiring parameters
 in the terminal are described by a
 parameterized string capability, with

-.IR printf (3S)
+.IR printf (3)

 like escapes \fB%x\fR in it.
 For example, to address the cursor, the
 .B cup
 like escapes \fB%x\fR in it.
 For example, to address the cursor, the
 .B cup


@@ -323,7 +325,9 @@ The \fB%\fR encodings have the following meanings:
 outputs `%'
 .TP
 %\fI[[\fP:\fI]flags][width[.precision]][\fPdoxXs\fI]\fP
 outputs `%'
 .TP
 %\fI[[\fP:\fI]flags][width[.precision]][\fPdoxXs\fI]\fP

-as in \fBprintf\fP, flags are [-+#] and space
+as in \fBprintf\fP, flags are [\-+#] and space.
+Use a `:' to allow the next character to be a `\-' flag,
+avoiding interpreting "%\-" as an operator.

 .TP
 %c
 print pop() like %c in \fBprintf\fP
 .TP
 %c
 print pop() like %c in \fBprintf\fP


@@ -331,20 +335,20 @@ print pop() like %c in \fBprintf\fP
 %s
 print pop() like %s in \fBprintf\fP
 .TP
 %s
 print pop() like %s in \fBprintf\fP
 .TP

-%p[1-9]
+%p[1\-9]

 push \fIi\fP'th parameter
 .TP
 push \fIi\fP'th parameter
 .TP

-%P[a-z]
-set dynamic variable [a-z] to pop()
+%P[a\-z]
+set dynamic variable [a\-z] to pop()

 .TP
 .TP

-%g[a-z]
-get dynamic variable [a-z] and push it
+%g[a\-z]
+get dynamic variable [a\-z] and push it

 .TP
 .TP

-%P[A-Z]
-set static variable [a-z] to pop()
+%P[A\-Z]
+set static variable [a\-z] to pop()

 .TP
 .TP

-%g[A-Z]
-get static variable [a-z] and push it
+%g[A\-Z]
+get static variable [a\-z] and push it

 .IP
 The terms "static" and "dynamic" are misleading.
 Historically, these are simply two different sets of variables,
 .IP
 The terms "static" and "dynamic" are misleading.
 Historically, these are simply two different sets of variables,


@@ -361,34 +365,46 @@ integer constant \fInn\fP
 %l
 push strlen(pop)
 .TP
 %l
 push strlen(pop)
 .TP

-%+ %- %* %/ %m
+%+ %\- %* %/ %m

 arithmetic (%m is mod): push(pop() op pop())
 .TP
 %& %| %^
 arithmetic (%m is mod): push(pop() op pop())
 .TP
 %& %| %^

-bit operations: push(pop() op pop())
+bit operations (AND, OR and exclusive-OR): push(pop() op pop())

 .TP
 %= %> %<
 logical operations: push(pop() op pop())
 .TP
 %A, %O
 .TP
 %= %> %<
 logical operations: push(pop() op pop())
 .TP
 %A, %O

-logical and & or operations (for conditionals)
+logical AND and OR operations (for conditionals)

 .TP
 %! %~
 .TP
 %! %~

-unary operations push(op pop())
+unary operations (logical and bit complement): push(op pop())

 .TP
 %i
 add 1 to first two parameters (for ANSI terminals)
 .TP
 %? \fIexpr\fP %t \fIthenpart\fP %e \fIelsepart\fP %;
 .TP
 %i
 add 1 to first two parameters (for ANSI terminals)
 .TP
 %? \fIexpr\fP %t \fIthenpart\fP %e \fIelsepart\fP %;

-if-then-else, %e \fIelsepart\fP is optional.
-else-if's are possible a la Algol 68:
-.br
+This forms an if-then-else.
+The %e \fIelsepart\fP is optional.
+Usually the %? \fIexpr\fP part pushes a value onto the stack,
+and %t pops it from the stack, testing if it is nonzero (true).
+If it is zero (false), control passes to the %e (else) part.
+.IP
+It is possible to form else-if's a la Algol 68:
+.RS

 %? c\d1\u %t b\d1\u %e c\d2\u %t b\d2\u %e c\d3\u %t b\d3\u %e c\d4\u %t b\d4\u %e %;
 %? c\d1\u %t b\d1\u %e c\d2\u %t b\d2\u %e c\d3\u %t b\d3\u %e c\d4\u %t b\d4\u %e %;

-.br
-c\di\u are conditions, b\di\u are bodies.
+.RE
+.IP
+where c\di\u are conditions, b\di\u are bodies.
+.IP
+Use the \fB\-f\fP option of \fBtic\fP or \fB@INFOCMP@\fP to see
+the structure of if-then-else's.
+Some strings, e.g., \fBsgr\fP can be very complicated when written
+on one line.
+The \fB\-f\fP option splits the string into lines with the parts indented.

 .PP
 Binary operations are in postfix form with the operands in the usual order.
 .PP
 Binary operations are in postfix form with the operands in the usual order.

-That is, to get x-5 one would use "%gx%{5}%-".
+That is, to get x\-5 one would use "%gx%{5}%-".

 %P and %g variables are
 persistent across escape-string evaluations.
 .PP
 %P and %g variables are
 persistent across escape-string evaluations.
 .PP


@@ -526,7 +542,7 @@ automatically, so you need not compose insert/delete strings for
 an entry with \fBcsr\fR).
 .PP
 Yet another way to construct insert and delete might be to use a combination of
 an entry with \fBcsr\fR).
 .PP
 Yet another way to construct insert and delete might be to use a combination of

-index with the memory-lock feature found on some terminals (like the HP-700/90
+index with the memory-lock feature found on some terminals (like the HP\-700/90

 series, which however also has insert/delete).
 .PP
 Inserting lines at the top or bottom of the screen can also be
 series, which however also has insert/delete).
 .PP
 Inserting lines at the top or bottom of the screen can also be


@@ -743,9 +759,9 @@ For example, the DEC vt220 supports most of the modes:
 .PP
 .TS
 center;
 .PP
 .TS
 center;

-l c c
-l c c
-lw28 lw6 lw2 lw20.
+l l l
+l l l
+lw18 lw14 lw18.

 \fBtparm parameter     attribute       escape sequence\fP
 
 none   none    \\E[0m
 \fBtparm parameter     attribute       escape sequence\fP
 
 none   none    \\E[0m


@@ -778,9 +794,9 @@ Writing out the above sequences, along with their dependencies yields
 .PP
 .TS
 center;
 .PP
 .TS
 center;

-l c c
-l c c
-lw28 lw6 lw2 lw20.
+l l l
+l l l
+lw18 lw14 lw18.

 \fBsequence    when to output  terminfo translation\fP
 
 \\E[0  always  \\E[0
 \fBsequence    when to output  terminfo translation\fP
 
 \\E[0  always  \\E[0


@@ -801,6 +817,12 @@ Putting this all together into the sgr sequence gives:
 .fi
 .PP
 Remember that if you specify sgr, you must also specify sgr0.
 .fi
 .PP
 Remember that if you specify sgr, you must also specify sgr0.

+Also, some implementations rely on sgr being given if sgr0 is,
+Not all terminfo entries necessarily have an sgr string, however.
+Many terminfo entries are derived from termcap entries
+which have no sgr string.
+The only drawback to adding an sgr string is that termcap also
+assumes that sgr0 does not exit alternate character set mode.

 .PP
 Terminals with the ``magic cookie'' glitch
 .RB ( xmc )
 .PP
 Terminals with the ``magic cookie'' glitch
 .RB ( xmc )


@@ -973,28 +995,36 @@ with the rest of the terminfo description.
 They are normally sent to the terminal, by the
 .I init
 option of the
 They are normally sent to the terminal, by the
 .I init
 option of the

-.IR tput
+.IR @TPUT@

 program, each time the user logs in.
 They will be printed in the following order:
 program, each time the user logs in.
 They will be printed in the following order:

+.RS
+.TP

 run the program
 run the program

-.BR iprog ;
+.BR iprog
+.TP

 output
 output

-.BR is1 ;
-.BR is2 ;
+.BR is1
+.BR is2
+.TP

 set the margins using
 .BR mgc ,
 .BR smgl
 and
 set the margins using
 .BR mgc ,
 .BR smgl
 and

-.BR smgr ;
+.BR smgr
+.TP

 set tabs using
 .B tbc
 and
 set tabs using
 .B tbc
 and

-.BR hts ;
+.BR hts
+.TP

 print the file
 print the file

-.BR if ;
+.BR if
+.TP

 and finally
 output
 .BR is3 .
 and finally
 output
 .BR is3 .

+.RE

 .PP
 Most initialization is done with
 .BR is2 .
 .PP
 Most initialization is done with
 .BR is2 .


@@ -1005,17 +1035,21 @@ and special cases in
 .B is1
 and
 .BR is3 .
 .B is1
 and
 .BR is3 .

-A pair of sequences that does a harder reset from a totally unknown state
-can be analogously given as
+.PP
+A set of sequences that does a harder reset from a totally unknown state
+can be given as

 .BR rs1 ,
 .BR rs2 ,
 .BR rs1 ,
 .BR rs2 ,

-.BR rf ,
+.BR rf

 and
 .BR rs3 ,
 analogous to
 and
 .BR rs3 ,
 analogous to

-.B is2
+.B is1 ,
+.B is2 ,
+.B if

 and
 and

-.BR if .
+.BR is3
+respectively.

 These strings are output by the
 .IR reset
 program, which is used when the terminal gets into a wedged state.
 These strings are output by the
 .IR reset
 program, which is used when the terminal gets into a wedged state.


@@ -1033,6 +1067,28 @@ normally be part of
 but it causes an annoying glitch of the screen and is not normally
 needed since the terminal is usually already in 80 column mode.
 .PP
 but it causes an annoying glitch of the screen and is not normally
 needed since the terminal is usually already in 80 column mode.
 .PP

+The
+.IR reset
+program writes strings
+including
+.BR iprog ,
+etc., in the same order as the
+.IR init
+program, using 
+.BR rs1 ,
+etc., instead of
+.BR is1 ,
+etc.
+If any of
+.BR rs1 ,
+.BR rs2 ,
+.BR rs3 ,
+or
+.BR rf
+reset capability strings are missing, the
+.IR reset
+program falls back upon the corresponding initialization capability string.
+.PP

 If there are commands to set and clear tab stops, they can be given as
 .B tbc
 (clear all tab stops)
 If there are commands to set and clear tab stops, they can be given as
 .B tbc
 (clear all tab stops)


@@ -1046,7 +1102,7 @@ or
 .BR if .
 .SS Delays and Padding
 .PP
 .BR if .
 .SS Delays and Padding
 .PP

-Many older and slower terminals don't support either XON/XOFF or DTR
+Many older and slower terminals do not support either XON/XOFF or DTR

 handshaking, including hard copy terminals and some very archaic CRTs
 (including, for example, DEC VT100s).
 These may require padding characters
 handshaking, including hard copy terminals and some very archaic CRTs
 (including, for example, DEC VT100s).
 These may require padding characters


@@ -1058,7 +1114,7 @@ close to full), set
 .BR xon .
 This capability suppresses the emission of padding.
 You can also set it
 .BR xon .
 This capability suppresses the emission of padding.
 You can also set it

-for memory-mapped console devices effectively that don't have a speed limit.
+for memory-mapped console devices effectively that do not have a speed limit.

 Padding information should still be included so that routines can
 make better decisions about relative costs, but actual pad characters will
 not be transmitted.
 Padding information should still be included so that routines can
 make better decisions about relative costs, but actual pad characters will
 not be transmitted.


@@ -1118,9 +1174,9 @@ This alternate character set may be specified by the \fBacsc\fR capability.
 .PP
 .TS H
 center expand;
 .PP
 .TS H
 center expand;

-c l l c
-c l l c
-lw28 lw6 lw2 lw20.
+l l l l
+l l l l
+lw25 lw10 lw6 lw6.

 .\".TH
 \fBGlyph       ACS     Ascii   VT100\fR
 \fBName        Name    Default Name\fR
 .\".TH
 \fBGlyph       ACS     Ascii   VT100\fR
 \fBName        Name    Default Name\fR


@@ -1128,7 +1184,7 @@ UK pound sign             ACS_STERLING    f       }
 arrow pointing down    ACS_DARROW      v       .
 arrow pointing left    ACS_LARROW      <       ,
 arrow pointing right   ACS_RARROW      >       +
 arrow pointing down    ACS_DARROW      v       .
 arrow pointing left    ACS_LARROW      <       ,
 arrow pointing right   ACS_RARROW      >       +

-arrow pointing up      ACS_UARROW      ^       -
+arrow pointing up      ACS_UARROW      ^       \-

 board of squares       ACS_BOARD       #       h
 bullet                 ACS_BULLET      o       ~
 checker board (stipple)        ACS_CKBOARD     :       a
 board of squares       ACS_BOARD       #       h
 bullet                 ACS_BULLET      o       ~
 checker board (stipple)        ACS_CKBOARD     :       a


@@ -1136,7 +1192,7 @@ degree symbol     ACS_DEGREE      \e      f
 diamond                ACS_DIAMOND     +       `
 greater-than-or-equal-to       ACS_GEQUAL      >       z
 greek pi               ACS_PI  *       {
 diamond                ACS_DIAMOND     +       `
 greater-than-or-equal-to       ACS_GEQUAL      >       z
 greek pi               ACS_PI  *       {

-horizontal line        ACS_HLINE       -       q
+horizontal line        ACS_HLINE       \-      q

 lantern symbol         ACS_LANTERN     #       i
 large plus or crossover        ACS_PLUS        +       n
 less-than-or-equal-to  ACS_LEQUAL      <       y
 lantern symbol         ACS_LANTERN     #       i
 large plus or crossover        ACS_PLUS        +       n
 less-than-or-equal-to  ACS_LEQUAL      <       y


@@ -1145,8 +1201,8 @@ lower right corner        ACS_LRCORNER    +       j
 not-equal              ACS_NEQUAL      !       |
 plus/minus             ACS_PLMINUS     #       g
 scan line 1            ACS_S1          ~       o
 not-equal              ACS_NEQUAL      !       |
 plus/minus             ACS_PLMINUS     #       g
 scan line 1            ACS_S1          ~       o

-scan line 3            ACS_S3          -       p
-scan line 7            ACS_S7          -       r
+scan line 3            ACS_S3          \-      p
+scan line 7            ACS_S7          \-      r

 scan line 9            ACS_S9          \&_     s
 solid square block     ACS_BLOCK       #       0
 tee pointing down      ACS_TTEE        +       w
 scan line 9            ACS_S9          \&_     s
 solid square block     ACS_BLOCK       #       0
 tee pointing down      ACS_TTEE        +       w


@@ -1171,7 +1227,7 @@ Most color terminals are either `Tektronix-like' or `HP-like'.
 Tektronix-like
 terminals have a predefined set of N colors (where N usually 8), and can set
 character-cell foreground and background characters independently, mixing them
 Tektronix-like
 terminals have a predefined set of N colors (where N usually 8), and can set
 character-cell foreground and background characters independently, mixing them

-into N * N color-pairs.
+into N\ *\ N color-pairs.

 On HP-like terminals, the use must set each color
 pair up separately (foreground and background are not independently settable).
 Up to M color-pairs may be set up from 2*M different colors.
 On HP-like terminals, the use must set each color
 pair up separately (foreground and background are not independently settable).
 Up to M color-pairs may be set up from 2*M different colors.


@@ -1256,7 +1312,7 @@ which color pair is current.
 On a Tektronix-like terminal, the capability \fBccc\fR may be present to
 indicate that colors can be modified.
 If so, the \fBinitc\fR capability will
 On a Tektronix-like terminal, the capability \fBccc\fR may be present to
 indicate that colors can be modified.
 If so, the \fBinitc\fR capability will

-take a color number (0 to \fBcolors\fR - 1)and three more parameters which
+take a color number (0 to \fBcolors\fR \- 1)and three more parameters which

 describe the color.
 These three parameters default to being interpreted as RGB
 (Red, Green, Blue) values.
 describe the color.
 These three parameters default to being interpreted as RGB
 (Red, Green, Blue) values.


@@ -1268,7 +1324,7 @@ terminal-dependent.
 On an HP-like terminal, \fBinitp\fR may give a capability for changing a
 color-pair value.
 It will take seven parameters; a color-pair number (0 to
 On an HP-like terminal, \fBinitp\fR may give a capability for changing a
 color-pair value.
 It will take seven parameters; a color-pair number (0 to

-\fBmax_pairs\fR - 1), and two triples describing first background and then
+\fBmax_pairs\fR \- 1), and two triples describing first background and then

 foreground colors.
 These parameters must be (Red, Green, Blue) or
 (Hue, Lightness, Saturation) depending on \fBhls\fR.
 foreground colors.
 These parameters must be (Red, Green, Blue) or
 (Hue, Lightness, Saturation) depending on \fBhls\fR.


@@ -1469,9 +1525,9 @@ A capability can be canceled by placing \fBxx@\fR to the left of the
 use reference that imports it, where \fIxx\fP is the capability.
 For example, the entry
 .PP
 use reference that imports it, where \fIxx\fP is the capability.
 For example, the entry
 .PP

-       2621-nl, smkx@, rmkx@, use=2621,
+       2621\-nl, smkx@, rmkx@, use=2621,

 .PP
 .PP

-defines a 2621-nl that does not have the \fBsmkx\fR or \fBrmkx\fR capabilities,
+defines a 2621\-nl that does not have the \fBsmkx\fR or \fBrmkx\fR capabilities,

 and hence does not turn on the function key labels when in visual mode.
 This is useful for different modes for a terminal, or for different
 user preferences.
 and hence does not turn on the function key labels when in visual mode.
 This is useful for different modes for a terminal, or for different
 user preferences.


@@ -1479,39 +1535,39 @@ user preferences.
 .SS Pitfalls of Long Entries
 .PP
 Long terminfo entries are unlikely to be a problem; to date, no entry has even
 .SS Pitfalls of Long Entries
 .PP
 Long terminfo entries are unlikely to be a problem; to date, no entry has even

-approached terminfo's 4K string-table maximum.
+approached terminfo's 4096-byte string-table maximum.

 Unfortunately, the termcap
 Unfortunately, the termcap

-translations are much more strictly limited (to 1K), thus termcap translations
+translations are much more strictly limited (to 1023 bytes), thus termcap translations

 of long terminfo entries can cause problems.
 .PP
 of long terminfo entries can cause problems.
 .PP

-The man pages for 4.3BSD and older versions of tgetent() instruct the user to
-allocate a 1K buffer for the termcap entry.
+The man pages for 4.3BSD and older versions of \fBtgetent()\fP instruct the user to
+allocate a 1024-byte buffer for the termcap entry.

 The entry gets null-terminated by
 the termcap library, so that makes the maximum safe length for a termcap entry
 The entry gets null-terminated by
 the termcap library, so that makes the maximum safe length for a termcap entry

-1k-1 (1023) bytes.
+1k\-1 (1023) bytes.

 Depending on what the application and the termcap library
 Depending on what the application and the termcap library

-being used does, and where in the termcap file the terminal type that tgetent()
+being used does, and where in the termcap file the terminal type that \fBtgetent()\fP

 is searching for is, several bad things can happen.
 .PP
 Some termcap libraries print a warning message or exit if they find an
 is searching for is, several bad things can happen.
 .PP
 Some termcap libraries print a warning message or exit if they find an

-entry that's longer than 1023 bytes; others don't; others truncate the
+entry that's longer than 1023 bytes; others do not; others truncate the

 entries to 1023 bytes.
 Some application programs allocate more than
 entries to 1023 bytes.
 Some application programs allocate more than

-the recommended 1K for the termcap entry; others don't.
+the recommended 1K for the termcap entry; others do not.

 .PP
 Each termcap entry has two important sizes associated with it: before
 "tc" expansion, and after "tc" expansion.
 "tc" is the capability that
 tacks on another termcap entry to the end of the current one, to add
 on its capabilities.
 .PP
 Each termcap entry has two important sizes associated with it: before
 "tc" expansion, and after "tc" expansion.
 "tc" is the capability that
 tacks on another termcap entry to the end of the current one, to add
 on its capabilities.

-If a termcap entry doesn't use the "tc"
+If a termcap entry does not use the "tc"

 capability, then of course the two lengths are the same.
 .PP
 The "before tc expansion" length is the most important one, because it
 affects more than just users of that particular terminal.
 This is the
 length of the entry as it exists in /etc/termcap, minus the
 capability, then of course the two lengths are the same.
 .PP
 The "before tc expansion" length is the most important one, because it
 affects more than just users of that particular terminal.
 This is the
 length of the entry as it exists in /etc/termcap, minus the

-backslash-newline pairs, which tgetent() strips out while reading it.
+backslash-newline pairs, which \fBtgetent()\fP strips out while reading it.

 Some termcap libraries strip off the final newline, too (GNU termcap does not).
 Now suppose:
 .TP 5
 Some termcap libraries strip off the final newline, too (GNU termcap does not).
 Now suppose:
 .TP 5


@@ -1524,15 +1580,15 @@ and the application has only allocated a 1k buffer,
 *
 and the termcap library (like the one in BSD/OS 1.1 and GNU) reads
 the whole entry into the buffer, no matter what its length, to see
 *
 and the termcap library (like the one in BSD/OS 1.1 and GNU) reads
 the whole entry into the buffer, no matter what its length, to see

-if it's the entry it wants,
+if it is the entry it wants,

 .TP 5
 *
 .TP 5
 *

-and tgetent() is searching for a terminal type that either is the
+and \fBtgetent()\fP is searching for a terminal type that either is the

 long entry, appears in the termcap file after the long entry, or
 long entry, appears in the termcap file after the long entry, or

-doesn't appear in the file at all (so that tgetent() has to search
+does not appear in the file at all (so that \fBtgetent()\fP has to search

 the whole termcap file).
 .PP
 the whole termcap file).
 .PP

-Then tgetent() will overwrite memory, perhaps its stack, and probably core dump
+Then \fBtgetent()\fP will overwrite memory, perhaps its stack, and probably core dump

 the program.
 Programs like telnet are particularly vulnerable; modern telnets
 pass along values like the terminal type automatically.
 the program.
 Programs like telnet are particularly vulnerable; modern telnets
 pass along values like the terminal type automatically.


@@ -1545,36 +1601,36 @@ here but will return incorrect data for the terminal.
 .PP
 The "after tc expansion" length will have a similar effect to the
 above, but only for people who actually set TERM to that terminal
 .PP
 The "after tc expansion" length will have a similar effect to the
 above, but only for people who actually set TERM to that terminal

-type, since tgetent() only does "tc" expansion once it's found the
+type, since \fBtgetent()\fP only does "tc" expansion once it is found the

 terminal type it was looking for, not while searching.
 .PP
 In summary, a termcap entry that is longer than 1023 bytes can cause,
 on various combinations of termcap libraries and applications, a core
 dump, warnings, or incorrect operation.
 terminal type it was looking for, not while searching.
 .PP
 In summary, a termcap entry that is longer than 1023 bytes can cause,
 on various combinations of termcap libraries and applications, a core
 dump, warnings, or incorrect operation.

-If it's too long even before
+If it is too long even before

 "tc" expansion, it will have this effect even for users of some other
 terminal types and users whose TERM variable does not have a termcap
 entry.
 .PP
 "tc" expansion, it will have this effect even for users of some other
 terminal types and users whose TERM variable does not have a termcap
 entry.
 .PP

-When in -C (translate to termcap) mode, the \fBncurses\fR implementation of
-\fBtic\fR(1) issues warning messages when the pre-tc length of a termcap
+When in \-C (translate to termcap) mode, the \fBncurses\fR implementation of
+\fB@TIC@\fR(1M) issues warning messages when the pre-tc length of a termcap

 translation is too long.
 translation is too long.

-The -c (check) option also checks resolved (after tc
+The \-c (check) option also checks resolved (after tc

 expansion) lengths.
 .SS Binary Compatibility
 It is not wise to count on portability of binary terminfo entries between
 commercial UNIX versions.
 The problem is that there are at least two versions
 expansion) lengths.
 .SS Binary Compatibility
 It is not wise to count on portability of binary terminfo entries between
 commercial UNIX versions.
 The problem is that there are at least two versions

-of terminfo (under HP-UX and AIX) which diverged from System V terminfo after
+of terminfo (under HP\-UX and AIX) which diverged from System V terminfo after

 SVr1, and have added extension capabilities to the string table that (in the
 binary format) collide with System V and XSI Curses extensions.
 .SH EXTENSIONS
 SVr1, and have added extension capabilities to the string table that (in the
 binary format) collide with System V and XSI Curses extensions.
 .SH EXTENSIONS

-Some SVr4 \fBcurses\fR implementations, and all previous to SVr4, don't
+Some SVr4 \fBcurses\fR implementations, and all previous to SVr4, do not

 interpret the %A and %O operators in parameter strings.
 .PP
 SVr4/XPG4 do not specify whether \fBmsgr\fR licenses movement while in
 an alternate-character-set mode (such modes may, among other things, map
 interpret the %A and %O operators in parameter strings.
 .PP
 SVr4/XPG4 do not specify whether \fBmsgr\fR licenses movement while in
 an alternate-character-set mode (such modes may, among other things, map

-CR and NL to characters that don't trigger local motions).
+CR and NL to characters that do not trigger local motions).

 The \fBncurses\fR implementation ignores \fBmsgr\fR in \fBALTCHARSET\fR
 mode.
 This raises the possibility that an XPG4
 The \fBncurses\fR implementation ignores \fBmsgr\fR in \fBALTCHARSET\fR
 mode.
 This raises the possibility that an XPG4


@@ -1601,37 +1657,41 @@ the XSI Curses standard and (in some cases) different extension sets.
 Here
 is a summary, accurate as of October 1995:
 .PP
 Here
 is a summary, accurate as of October 1995:
 .PP

-\fBSVR4, Solaris, ncurses\fR --
+\fBSVR4, Solaris, ncurses\fR \-\-

 These support all SVr4 capabilities.
 .PP
 These support all SVr4 capabilities.
 .PP

-\fBSGI\fR --
+\fBSGI\fR \-\-

 Supports the SVr4 set, adds one undocumented extended string
 capability (\fBset_pglen\fR).
 .PP
 Supports the SVr4 set, adds one undocumented extended string
 capability (\fBset_pglen\fR).
 .PP

-\fBSVr1, Ultrix\fR --
+\fBSVr1, Ultrix\fR \-\-

 These support a restricted subset of terminfo capabilities.
 The booleans
 end with \fBxon_xoff\fR; the numerics with \fBwidth_status_line\fR; and the
 strings with \fBprtr_non\fR.
 .PP
 These support a restricted subset of terminfo capabilities.
 The booleans
 end with \fBxon_xoff\fR; the numerics with \fBwidth_status_line\fR; and the
 strings with \fBprtr_non\fR.
 .PP

-\fBHP/UX\fR --
+\fBHP/UX\fR \-\-

 Supports the SVr1 subset, plus the SVr[234] numerics \fBnum_labels\fR,
 \fBlabel_height\fR, \fBlabel_width\fR, plus function keys 11 through 63, plus
 \fBplab_norm\fR, \fBlabel_on\fR, and \fBlabel_off\fR, plus some incompatible
 extensions in the string table.
 .PP
 Supports the SVr1 subset, plus the SVr[234] numerics \fBnum_labels\fR,
 \fBlabel_height\fR, \fBlabel_width\fR, plus function keys 11 through 63, plus
 \fBplab_norm\fR, \fBlabel_on\fR, and \fBlabel_off\fR, plus some incompatible
 extensions in the string table.
 .PP

-\fBAIX\fR --
+\fBAIX\fR \-\-

 Supports the SVr1 subset, plus function keys 11 through 63, plus a number
 of incompatible string table extensions.
 .PP
 Supports the SVr1 subset, plus function keys 11 through 63, plus a number
 of incompatible string table extensions.
 .PP

-\fBOSF\fR --
+\fBOSF\fR \-\-

 Supports both the SVr4 set and the AIX extensions.
 .SH FILES
 .TP 25
 \*d/?/*
 files containing terminal descriptions
 .SH SEE ALSO
 Supports both the SVr4 set and the AIX extensions.
 .SH FILES
 .TP 25
 \*d/?/*
 files containing terminal descriptions
 .SH SEE ALSO

-\fBtic\fR(1M), \fBcurses\fR(3X), \fBprintf\fR(3S), \fBterm\fR(\*n).
+\fB@TIC@\fR(1M),
+\fB@INFOCMP@\fR(1M),
+\fBcurses\fR(3X),
+\fBprintf\fR(3),
+\fBterm\fR(\*n).

 .SH AUTHORS
 Zeyd M. Ben-Halim, Eric S. Raymond, Thomas E. Dickey.
 Based on pcurses by Pavel Curtis.
 .SH AUTHORS
 Zeyd M. Ben-Halim, Eric S. Raymond, Thomas E. Dickey.
 Based on pcurses by Pavel Curtis.