<!--
****************************************************************************
- * Copyright (c) 1998-2010,2015 Free Software Foundation, Inc. *
+ * Copyright (c) 1998-2016,2017 Free Software Foundation, Inc. *
* *
* Permission is hereby granted, free of charge, to any person obtaining a *
* copy of this software and associated documentation files (the *
* sale, use or other dealings in this Software without prior written *
* authorization. *
****************************************************************************
- * @Id: term.5,v 1.22 2015/04/26 14:50:23 tom Exp @
+ * @Id: term.5,v 1.26 2017/02/18 16:58:21 tom Exp @
-->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
<HTML>
made.
The compiled file is created with the <STRONG>tic</STRONG> program, and
- read by the routine <EM>setupterm</EM>. The file is divided into
- six parts: the header, terminal names, boolean flags, num-
- bers, strings, and string table.
+ read by the routine <STRONG><A HREF="curs_terminfo.3x.html">setupterm(3x)</A></STRONG>. The file is divided
+ into six parts: the header, terminal names, boolean flags,
+ numbers, strings, and string table.
The header section begins the file. This section contains
six short integers in the format described below. These
The terminal names section comes next. It contains the
first line of the terminfo description, listing the vari-
- ous names for the terminal, separated by the `|' charac-
+ ous names for the terminal, separated by the "|" charac-
ter. The section is terminated with an ASCII NUL charac-
ter.
</PRE><H2><a name="h2-PORTABILITY">PORTABILITY</a></H2><PRE>
- Note that it is possible for <EM>setupterm</EM> to expect a differ-
+ Note that it is possible for <STRONG>setupterm</STRONG> to expect a differ-
ent set of capabilities than are actually present in the
file. Either the database may have been updated since
- <EM>setupterm</EM> has been recompiled (resulting in extra unrecog-
+ <STRONG>setupterm</STRONG> has been recompiled (resulting in extra unrecog-
nized entries in the file) or the program may have been
recompiled more recently than the database was updated
- (resulting in missing entries). The routine <EM>setupterm</EM>
+ (resulting in missing entries). The routine <STRONG>setupterm</STRONG>
must be prepared for both possibilities - this is why the
numbers and sizes are included. Also, new capabilities
must always be added at the end of the lists of boolean,