[PATCH 29/52] Set `SCREEN` data type name in italics.

[G. Branden Robinson]

* man/curs_color.3x:
* man/curs_initscr.3x:
* man/curs_memleaks.3x: ...not bold.

* man/curs_sp_funcs.3x:
* man/curs_terminfo.3x: ...and not roman.
---
 man/curs_color.3x    |  2 +-
 man/curs_initscr.3x  | 24 ++++++++++++------------
 man/curs_memleaks.3x |  2 +-
 man/curs_sp_funcs.3x |  2 +-
 man/curs_terminfo.3x |  2 +-
 5 files changed, 16 insertions(+), 16 deletions(-)

diff --git a/man/curs_color.3x b/man/curs_color.3x
index 20b06288e..7f30c2707 100644
--- a/man/curs_color.3x
+++ b/man/curs_color.3x
@@ -529,7 +529,7 @@ .SH HISTORY
 .PP
 SVr4 made internal changes,
 e.g., moving the storage for the color state
-from \fBSP\fP (the \fBSCREEN\fP structure)
+from \fBSP\fP (the \fISCREEN\fP structure)
 to \fB\%cur_term\fP (the \fB\%TERMINAL\fP structure),
 but provided the same set of library functions.
 .PP
diff --git a/man/curs_initscr.3x b/man/curs_initscr.3x
index fcb73d677..c530bd9fc 100644
--- a/man/curs_initscr.3x
+++ b/man/curs_initscr.3x
@@ -91,7 +91,7 @@ .SS newterm
 \fBnewterm\fP.
 .PP
 The routine \fBnewterm\fP should be called once for each terminal.
-It returns a variable of type \fBSCREEN *\fP which should be saved
+It returns a variable of type \fISCREEN *\fP which should be saved
 as a reference to that terminal.
 \fBnewterm\fP's arguments are
 .bP
@@ -138,14 +138,14 @@ .SS set_term
 The \fBset_term\fP routine is used to switch between different terminals.
 The screen reference \fInew\fP becomes the new current terminal.
 The previous terminal is returned by the routine.
-This is the only routine which manipulates \fBSCREEN\fP pointers;
+This is the only routine which manipulates \fISCREEN\fP pointers;
 all other routines affect only the current terminal.
 .SS delscreen
 The \fBdelscreen\fP routine frees storage associated with the
-\fBSCREEN\fP data structure.
+\fISCREEN\fP data structure.
 The \fBendwin\fP routine does not do
 this, so \fBdelscreen\fP should be called after \fBendwin\fP if a
-particular \fBSCREEN\fP is no longer needed.
+particular \fISCREEN\fP is no longer needed.
 .SH RETURN VALUE
 \fBendwin\fP returns the integer \fBERR\fP upon failure and \fBOK\fP
 upon successful completion.
@@ -193,15 +193,15 @@ .SS Differences
 .PP
 Calling \fBendwin\fP does not dispose of the memory allocated in \fBinitscr\fP
 or \fBnewterm\fP.
-Deleting a \fBSCREEN\fP provides a way to do this:
+Deleting a \fISCREEN\fP provides a way to do this:
 .bP
 X/Open Curses does not say what happens to \fBWINDOW\fPs when \fBdelscreen\fP
-\*(``frees storage associated with the \fBSCREEN\fP\*(''
+\*(``frees storage associated with the \fISCREEN\fP\*(''
 nor does the SVr4 documentation help,
-adding that it should be called after \fBendwin\fP if a \fBSCREEN\fP
+adding that it should be called after \fBendwin\fP if a \fISCREEN\fP
 is no longer needed.
 .bP
-However, \fBWINDOW\fPs are implicitly associated with a \fBSCREEN\fP.
+However, \fI\%WINDOW\fPs are implicitly associated with a \fISCREEN\fP.
 so that it is reasonable to expect \fBdelscreen\fP to deal with these.
 .bP
 SVr4 curses deletes the standard \fBWINDOW\fP structures
@@ -217,7 +217,7 @@ .SS Differences
 deleting only the standard \fBWINDOW\fP structures.
 .SS "High-level versus Low-level"
 Different implementations may disagree regarding the level of some functions.
-For example, \fBSCREEN\fP (returned by \fBnewterm\fP) and
+For example, \fISCREEN\fP (returned by \fBnewterm\fP) and
 \fBTERMINAL\fP (returned by \fBsetupterm\fP(3X)) hold file descriptors for
 the output stream.
 If an application switches screens using \fBset_term\fR,
@@ -228,7 +228,7 @@ .SS "High-level versus Low-level"
 For example
 .bP
 NetBSD's \fBbaudrate\fP(3X) function uses the descriptor in \fBTERMINAL\fP.
-\fI\%ncurses\fP and SVr4 use the descriptor in \fBSCREEN\fP.
+\fI\%ncurses\fP and SVr4 use the descriptor in \fISCREEN\fP.
 .bP
 NetBSD and \fI\%ncurses\fP use the descriptor
 in \fBTERMINAL\fP
@@ -236,7 +236,7 @@ .SS "High-level versus Low-level"
 e.g.,
 \fBdef_shell_mode\fP(3X),
 \fBdef_prog_mode\fP(3X).
-SVr4 curses uses the descriptor in \fBSCREEN\fP.
+SVr4 curses uses the descriptor in \fISCREEN\fP.
 .SS "Unset \fITERM\fP Variable"
 If the \fITERM\fP variable is missing or empty, \fBinitscr\fP uses the
 value \*(``unknown\*('',
@@ -274,7 +274,7 @@ .SS "Signal Handlers"
 Although it \fIusually\fP works as expected, there are limitations:
 .RS 5
 .bP
-Walking the \fBSCREEN\fP list is unsafe, since all list management
+Walking the \fISCREEN\fP list is unsafe, since all list management
 is done without any signal blocking.
 .bP
 On systems which have \fBREENTRANT\fP turned on, \fBset_term\fP uses
diff --git a/man/curs_memleaks.3x b/man/curs_memleaks.3x
index 77d05ac34..db2bccf2f 100644
--- a/man/curs_memleaks.3x
+++ b/man/curs_memleaks.3x
@@ -114,7 +114,7 @@ .SH PORTABILITY
 of the memory allocated by curses:
 .bP
 The portable part of \fB\%exit_curses\fP can be freed using \fB\%delscreen\fP,
-passing the \fBSCREEN*\fP pointer returned by \fB\%newterm\fP.
+passing the \fISCREEN*\fP pointer returned by \fB\%newterm\fP.
 .IP
 In some implementations, there is a global variable \fBsp\fP
 which could be used, e.g., if the screen were only initialized
diff --git a/man/curs_sp_funcs.3x b/man/curs_sp_funcs.3x
index aaf33d63c..4e733e5fd 100644
--- a/man/curs_sp_funcs.3x
+++ b/man/curs_sp_funcs.3x
@@ -221,7 +221,7 @@ .SH DESCRIPTION
 .SS "Improved Functions"
 Most of the functions are new versions of existing functions.
 A parameter is added at the front of the parameter list.
-It is a SCREEN pointer.
+It is a \fISCREEN\fP pointer.
 .PP
 The existing functions all use the current screen,
 which is a static variable.
diff --git a/man/curs_terminfo.3x b/man/curs_terminfo.3x
index aeee9db81..4fd72b1ec 100644
--- a/man/curs_terminfo.3x
+++ b/man/curs_terminfo.3x
@@ -664,7 +664,7 @@ .SS "Other Portability Issues"
 actual terminal state, and that an application should touch and refresh
 the window before resuming normal curses calls.
 Both \fI\%ncurses\fP and System V Release 4 curses implement \fBmvcur\fP
-using the SCREEN data allocated in either \fBinitscr\fP or
+using the \fISCREEN\fP data allocated in either \fBinitscr\fP or
 \fBnewterm\fP.
 So though it is documented as a terminfo function,
 \fBmvcur\fP is really a curses function which is not well specified.
-- 
2.30.2

signature.asc
Description: PGP signature