+</PRE><H2><a name="h2-BUGS">BUGS</a></H2><PRE>
+ If you call <STRONG>tgetstr</STRONG> to fetch <STRONG>ca</STRONG> or any other parameterized string
+ capability, be aware that it is returned in <EM>terminfo</EM> notation, not the
+ older and not-quite-compatible <EM>termcap</EM> notation. This does not cause
+ problems if all you do with it is call <STRONG>tgoto</STRONG> or <STRONG>tparm</STRONG>, which both
+ expand <EM>terminfo</EM>-style strings as <EM>terminfo</EM> does. (The <STRONG>tgoto</STRONG> function,
+ if configured to support <EM>termcap,</EM> checks if the string is indeed
+ <EM>terminfo</EM>-style by looking for "<STRONG>%p</STRONG>" parameters or "<STRONG><</STRONG>...<STRONG>></STRONG>" delays, and
+ invokes a <EM>termcap</EM>-style parser if the string appears not to use
+ <EM>terminfo</EM> syntax.)
+
+ Because <EM>terminfo</EM>'s syntax for padding in string capabilities differs
+ from <EM>termcap</EM>'s, users can be surprised.
+
+ <STRONG>o</STRONG> <STRONG>tputs("50")</STRONG> in a <EM>terminfo</EM> system transmits "50" rather than busy-
+ waiting for 50 milliseconds.
+
+ <STRONG>o</STRONG> However, if <EM>ncurses</EM> is configured to support <EM>termcap</EM>, it may also
+ have been configured to support BSD-style padding.
+
+ In that case, <STRONG>tputs</STRONG> inspects strings passed to it, looking for
+ digits at the beginning of the string.
+
+ <STRONG>tputs("50")</STRONG> in a <EM>termcap</EM> system may busy-wait for 50 milliseconds
+ rather than transmitting "50".
+
+ <EM>termcap</EM> has nothing analogous to <EM>terminfo</EM>'s <STRONG>sgr</STRONG> string. One
+ consequence is that <EM>termcap</EM> applications assume that <STRONG>me</STRONG> (equivalent to
+ <EM>terminfo</EM>'s <STRONG>sgr0</STRONG> capability) does not reset the alternate character set.
+ <EM>ncurses</EM> checks for, and modifies the data shared with, the <EM>termcap</EM>
+ interface to accommodate the latter's limitation in this respect.
+
+