- The <STRONG>scr_dump</STRONG> routine dumps the current contents of the virtual screen
- to the file <EM>filename</EM>.
-
- The <STRONG>scr_restore</STRONG> routine sets the virtual screen to the contents of
- <EM>filename</EM>, which must have been written using <STRONG>scr_dump</STRONG>. The next call
- to <STRONG>doupdate</STRONG> restores the screen to the way it looked in the dump file.
-
- The <STRONG>scr_init</STRONG> routine reads in the contents of <EM>filename</EM> and uses them to
- initialize the <STRONG>curses</STRONG> data structures about what the terminal currently
- has on its screen. If the data is determined to be valid, <STRONG>curses</STRONG> bases
- its next update of the screen on this information rather than clearing
- the screen and starting from scratch. <STRONG>scr_init</STRONG> is used after <STRONG>initscr</STRONG>
- or a <STRONG>system</STRONG> call to share the screen with another process which has
- done a <STRONG>scr_dump</STRONG> after its <STRONG><A HREF="curs_initscr.3x.html">endwin(3x)</A></STRONG> call. The data is declared in-
- valid if the terminfo capabilities <STRONG>rmcup</STRONG> and <STRONG>nrrmc</STRONG> exist; also if the
- terminal has been written to since the preceding <STRONG>scr_dump</STRONG> call.
-
- The <STRONG>scr_set</STRONG> routine is a combination of <STRONG>scr_restore</STRONG> and <STRONG>scr_init</STRONG>. It
- tells the program that the information in <EM>filename</EM> is what is currently
+ The <B>scr_dump</B> routine dumps the current contents of the <I>virtual</I> <I>screen</I>
+ to the file <I>filename</I>.
+
+ The <B>scr_restore</B> routine sets the <I>virtual</I> <I>screen</I> to the contents of
+ <I>filename</I>, which must have been written using <B>scr_dump</B>. The next call
+ to <B>doupdate</B> restores the <I>physical</I> <I>screen</I> to the way it looked in the
+ dump file.
+
+ The <B>scr_init</B> routine reads in the contents of <I>filename</I> and uses them to
+ initialize the <B>curses</B> data structures about what the terminal currently
+ has on its screen. If the data is determined to be valid, <B>curses</B> bases
+ its next update of the screen on this information rather than clearing
+ the screen and starting from scratch. <B>scr_init</B> is used after <B>initscr</B>
+ or a <B>system</B> call to share the screen with another process which has
+ done a <B>scr_dump</B> after its <B><A HREF="curs_initscr.3X.html">endwin(3X)</A></B> call. The data is declared in-
+ valid
+
+ <B>o</B> if the terminfo capabilities <B>rmcup</B> and <B>nrrmc</B> exist, also
+
+ <B>o</B> if the terminal has been written to since the preceding <B>scr_dump</B>
+ call.
+
+ The <B>scr_set</B> routine is a combination of <B>scr_restore</B> and <B>scr_init</B>. It
+ tells the program that the information in <I>filename</I> is what is currently