bug-ncurses
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[PATCH 33/52] Set `WINDOW` data type name in italics.


From: G. Branden Robinson
Subject: [PATCH 33/52] Set `WINDOW` data type name in italics.
Date: Fri, 22 Dec 2023 17:07:11 -0600

* man/curs_initscr.3x:
* man/curs_util.3x:
* man/scr_dump.5: ...not bold.

* man/ncurses.3x: ...and not roman.

...and protect it from hyphenation (perhaps unnecessarily).
---
 man/curs_initscr.3x |  6 +++---
 man/curs_util.3x    |  4 ++--
 man/ncurses.3x      |  4 ++--
 man/scr_dump.5      | 18 +++++++++---------
 4 files changed, 16 insertions(+), 16 deletions(-)

diff --git a/man/curs_initscr.3x b/man/curs_initscr.3x
index 8a9b23891..01b788269 100644
--- a/man/curs_initscr.3x
+++ b/man/curs_initscr.3x
@@ -195,7 +195,7 @@ .SS Differences
 or \fBnewterm\fP.
 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
+X/Open Curses does not say what happens to \fI\%WINDOW\fPs when \fBdelscreen\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 \fISCREEN\fP
@@ -204,7 +204,7 @@ .SS Differences
 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
+SVr4 curses deletes the standard \fI\%WINDOW\fP structures
 \fBstdscr\fP and \fBcurscr\fP as well as a work area \fBnewscr\fP.
 SVr4 curses ignores other windows.
 .bP
@@ -214,7 +214,7 @@ .SS Differences
 .bP
 NetBSD copied this feature of \fI\%ncurses\fP in 2001.
 PDCurses follows the SVr4 model,
-deleting only the standard \fBWINDOW\fP structures.
+deleting only the standard \fI\%WINDOW\fP structures.
 .SS "High-level versus Low-level"
 Different implementations may disagree regarding the level of some functions.
 For example, \fISCREEN\fP (returned by \fBnewterm\fP) and
diff --git a/man/curs_util.3x b/man/curs_util.3x
index d38078dc0..30d866c10 100644
--- a/man/curs_util.3x
+++ b/man/curs_util.3x
@@ -246,7 +246,7 @@ .SS putwin/getwin
 It returns a pointer to the new window.
 There are a few caveats:
 .bP
-the data written is a copy of the \fBWINDOW\fP structure,
+the data written is a copy of the \fI\%WINDOW\fP structure,
 and its associated character cells.
 The format differs between the wide-character (\fI\%ncursesw\fP) and
 non-wide (\fI\%ncurses\fP) libraries.
@@ -347,7 +347,7 @@ .SS putwin/getwin file-format
 and were later (in 1988) incorporated into SVr4.
 Oddly, there are no such functions in the 4.3BSD curses sources.
 .bP
-Most implementations simply dump the binary \fBWINDOW\fP structure to the file.
+Most implementations simply dump the binary \fI\%WINDOW\fP structure to the 
file.
 These include SVr4 curses, NetBSD and PDCurses,
 as well as older \fI\%ncurses\fP versions.
 This implementation
diff --git a/man/ncurses.3x b/man/ncurses.3x
index c0d2e546f..b3b727960 100644
--- a/man/ncurses.3x
+++ b/man/ncurses.3x
@@ -1599,7 +1599,7 @@ .SS "Error Checking"
 omitting some of the SVr4 documentation.
 .PP
 Unlike other implementations, this one checks parameters such as pointers
-to WINDOW structures to ensure they are not null.
+to \fI\%WINDOW\fP structures to ensure they are not null.
 The main reason for providing this behavior is to guard against programmer
 error.
 The standard interface does not provide a way for the library
@@ -1630,7 +1630,7 @@ .SS "Extensions Versus Portability"
 The routine \fBwresize\fP is not part of XPG4, nor is it present in SVr4.
 See the \fBwresize\fP(3X) manual page for details.
 .bP
-The WINDOW structure's internal details can be hidden from application
+The \fI\%WINDOW\fP structure's internal details can be hidden from application
 programs.
 See \fBcurs_opaque\fP(3X) for the discussion of \fBis_scrollok\fP, etc.
 .bP
diff --git a/man/scr_dump.5 b/man/scr_dump.5
index 73cbebb40..dd66be645 100644
--- a/man/scr_dump.5
+++ b/man/scr_dump.5
@@ -119,14 +119,14 @@ .SS "ncurses5 (Legacy)"
 While there were fixes and improvements in succeeding years,
 the basic scheme was unchanged:
 .bP
-The \fBWINDOW\fP structure was written in binary form.
+The \fI\%WINDOW\fP structure was written in binary form.
 .bP
-The \fBWINDOW\fP structure refers to lines of data,
-which were written as an array of binary data following the \fBWINDOW\fP.
+The \fI\%WINDOW\fP structure refers to lines of data,
+which were written as an array of binary data following the \fI\%WINDOW\fP.
 .bP
 When \fBgetwin\fP restored the window,
 it would keep track of offsets into the array of line-data
-and adjust the \fBWINDOW\fP structure which was read back into memory.
+and adjust the \fI\%WINDOW\fP structure which was read back into memory.
 .PP
 This is similar to Unix System\ V,
 but does not write a \*(``magic number\*('' to identify the file format.
@@ -173,7 +173,7 @@ .SS "X/Open Curses"
 .SS "Unix System V"
 Unix System\ V curses identified the file format by writing a
 \*(``magic number\*('' at the beginning of the dump.
-The \fBWINDOW\fP data and the lines of text follow, all in binary form.
+The \fI\%WINDOW\fP data and the lines of text follow, all in binary form.
 .PP
 The Solaris curses source has these definitions:
 .PP
@@ -211,7 +211,7 @@ .SS "Unix System V"
 .EE
 .RE
 .PP
-After the magic number, the \fBWINDOW\fP structure and line-data are
+After the magic number, the \fI\%WINDOW\fP structure and line-data are
 written in binary format.
 While the magic number used by the Unix systems can be seen using \fBod\fP(1),
 none of the Unix systems documents the format used for screen-dumps.
@@ -251,7 +251,7 @@ .SS Solaris
 .SS PDCurses
 PDCurses added support for screen dumps in version 2.7 (2005).
 Like Unix System\ V and ncurses5,
-it writes the \fBWINDOW\fP structure in binary,
+it writes the \fI\%WINDOW\fP structure in binary,
 but begins the file with its three-byte identifier \*(``PDC\*('',
 followed by a one-byte version,
 e.g.,
@@ -274,9 +274,9 @@ .SS NetBSD
 the curses shared library major and minor versions
 as the first two bytes (e.g., 7 and 1),
 .bP
-followed by a binary dump of the \fBWINDOW\fP,
+followed by a binary dump of the \fI\%WINDOW\fP,
 .bP
-some data for wide-characters referenced by the \fBWINDOW\fP structure, and
+some data for wide-characters referenced by the \fI\%WINDOW\fP structure, and
 .bP
 finally, lines as done by other implementations.
 .SH EXAMPLES
-- 
2.30.2

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]