- <STRONG>terminfo</STRONG> <STRONG>termcap</STRONG> Representative Terminals
- ---------------------------------------------------------------
- <STRONG>%p1%c</STRONG> <STRONG>%.</STRONG> adm
- <STRONG>%p1%d</STRONG> <STRONG>%d</STRONG> hp, ANSI standard, vt100
- <STRONG>%p1%'x'%+%c</STRONG> <STRONG>%+x</STRONG> concept
- <STRONG>%i</STRONG> <STRONG>%i</STRONG>q ANSI standard, vt100
- <STRONG>%p1%?%'x'%>%t%p1%'y'%+%;</STRONG> <STRONG>%>xy</STRONG> concept
- <STRONG>%p2</STRONG> is printed before <STRONG>%p1</STRONG> <STRONG>%r</STRONG> hp
-
-
-</PRE><H3><a name="h3-Use_-Option-_-u_">Use= Option [-u]</a></H3><PRE>
- The <STRONG>-u</STRONG> option produces a <STRONG>terminfo</STRONG> source description of the first ter-
- minal <EM>termname</EM> which is relative to the sum of the descriptions given
- by the entries for the other terminals <EM>termnames</EM>. It does this by ana-
- lyzing the differences between the first <EM>termname</EM> and the other
- <EM>termnames</EM> and producing a description with <STRONG>use=</STRONG> fields for the other
- terminals. In this manner, it is possible to retrofit generic terminfo
- entries into a terminal's description. Or, if two similar terminals
- exist, but were coded at different times or by different people so that
- each description is a full description, using <STRONG>infocmp</STRONG> will show what
- can be done to change one description to be relative to the other.
-
- A capability will get printed with an at-sign (@) if it no longer
- exists in the first <EM>termname</EM>, but one of the other <EM>termname</EM> entries
- contains a value for it. A capability's value gets printed if the
- value in the first <EM>termname</EM> is not found in any of the other <EM>termname</EM>
- entries, or if the first of the other <EM>termname</EM> entries that has this
- capability gives a different value for the capability than that in the
- first <EM>termname</EM>.
-
- The order of the other <EM>termname</EM> entries is significant. Since the ter-
- minfo compiler <STRONG>tic</STRONG> does a left-to-right scan of the capabilities, spec-
- ifying two <STRONG>use=</STRONG> entries that contain differing entries for the same
+ <STRONG><EM>terminfo</EM></STRONG> <STRONG><EM>termcap</EM></STRONG> Terminal Types
+ ----------------------------------------------------
+ <STRONG>%p1%c</STRONG> <STRONG>%.</STRONG> ansi-m
+ <STRONG>%p1%d</STRONG> <STRONG>%d</STRONG> ansi, vt100
+ <STRONG>%p1%'</STRONG> <STRONG>'%+%c</STRONG> <STRONG>%+x</STRONG> vt52
+ <STRONG>%i</STRONG> <STRONG>%iq</STRONG> ansi, vt100
+ <STRONG>%p1%?%'x'%>%t%p1%'y'%+%;</STRONG> <STRONG>%>xy</STRONG> annarbor4080
+ <STRONG>%p2</STRONG>...<STRONG>%p1</STRONG> <STRONG>%r</STRONG> hpgeneric
+
+
+</PRE><H3><a name="h3-Use_Option_u_">Use= Option [-u]</a></H3><PRE>
+ The <STRONG>-u</STRONG> option produces a <STRONG>terminfo</STRONG> source description of the first
+ terminal <EM>terminal-type</EM> which is relative to the sum of the descriptions
+ given by the entries for the other <EM>terminal-types</EM>. It does this by
+ analyzing the differences between the first <EM>terminal-types</EM> and the
+ other <EM>terminal-types</EM> and producing a description with <STRONG>use=</STRONG> fields for
+ the other terminals. In this manner, it is possible to retrofit
+ generic terminfo entries into a terminal's description. Or, if two
+ similar terminals exist, but were coded at different times or by
+ different people so that each description is a full description, using
+ <STRONG>infocmp</STRONG> will show what can be done to change one description to be
+ relative to the other.
+
+ A capability will be printed with an at-sign (@) if it no longer exists
+ in the first <EM>terminal-type</EM>, but one of the other <EM>terminal-type</EM> entries
+ contains a value for it. A capability's value will be printed if the
+ value in the first <EM>terminal-type</EM> is not found in any of the other
+ <EM>terminal-type</EM> entries, or if the first of the other <EM>terminal-type</EM>
+ entries that has this capability gives a different value for the
+ capability than that in the first <EM>terminal-type</EM>.
+
+ The order of the other <EM>terminal-type</EM> entries is significant. Since the
+ terminfo compiler <STRONG>tic</STRONG> does a left-to-right scan of the capabilities,
+ specifying two <STRONG>use=</STRONG> entries that contain differing entries for the same