bug-ncurses
[Top][All Lists]
Advanced

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

[PATCH 153/177] man/curs_termcap.3x: Revise "PORTABILITY" section.


From: G. Branden Robinson
Subject: [PATCH 153/177] man/curs_termcap.3x: Revise "PORTABILITY" section.
Date: Mon, 13 Jan 2025 11:41:31 -0600

Content:
* Drop history of X/Open Curses revisions, to be resurrected in the
  "HISTORY" section in a forthcoming commit.  Provide forward reference
  to that section.

Style:
* Set macro names and other C symbols in italics, not bold, when
  referring to them generically in this section, as opposed to the
  ncurses topic/implementation.

Markup:
* Italicized words in subsection headings can render in the wrong font
  family when using contemporary groff.  Switch to regular italics, not
  bold italics, to set the word "TERM" in a subsection heading.  This
  way it stops presuming that the weight of the font used to render the
  heading is heavy (bold).  A sufficiently intelligent `SS` macro can
  remap the italic face to one that is bold-italic if the weight of the
  heading font is bold, as groff 1.23 does (groff 1.23 also permits the
  heading font to be customized at rendering time).

  It might be worth noting that the original AT&T man(7) package of
  Seventh Edition Unix (1979) offered no provision for the use of
  bold italics; such a face was not available on the four-font Graphical
  Systems, Inc. C/A/T phototypesetter.  (The four faces were "RIBS":
  roman, italic, bold, and "special"; see the 1976 edition of the
  NROFF/TROFF User's Manual by J. Ossanna, CSTR #54.  The roff(7) man
  page as of groff 1.23.0 also summarizes the Bell Labs CSRC situation.)
---
 man/curs_termcap.3x | 28 +++++++---------------------
 1 file changed, 7 insertions(+), 21 deletions(-)

diff --git a/man/curs_termcap.3x b/man/curs_termcap.3x
index 14b0a9d5d..66e082e81 100644
--- a/man/curs_termcap.3x
+++ b/man/curs_termcap.3x
@@ -376,24 +376,10 @@ .SH NOTES
 .SH PORTABILITY
 These functions are no longer standardized
 (and the variables never were);
+see section \*(``HISTORY\*('' below.
 .I \%ncurses
-provides them to support legacy applications.
-They should not be used in new programs.
-.SS Standards
-.bP
-X/Open Curses Issue\ 4 Version\ 2 (1996),
-describes these functions,
-marking them as
-\*(``TO BE WITHDRAWN\*(''.
-.bP
-X/Open Curses Issue\ 7 (2009) withdrew the
-.I termcap
-interface
-(along with the
-.I \%vwprintw
-and
-.I \%vwscanw
-functions).
+provides them to support legacy applications;
+they should not be used in new programs.
 .PP
 Neither X/Open Curses nor the SVr4 man pages documented the return
 values of
@@ -405,9 +391,9 @@ .SS Standards
 to mean that
 .I \%tgetent
 returns
-.B OK
+.I OK
 or
-.BR ERR "."
+.IR ERR "."
 Because the purpose of these functions is to provide compatibility with
 the
 .I termcap
@@ -415,7 +401,7 @@ .SS Standards
 that is a defect in X/Open Curses Issue\ 4 Version\ 2
 rather than in
 .IR \%ncurses "."
-.SS "Compatibility with BSD \f(BItermcap\fP"
+.SS "Compatibility with BSD \fItermcap\fP"
 .I \%ncurses
 provides externally visible variables to support certain
 .I termcap
@@ -426,7 +412,7 @@ .SS "Compatibility with BSD \f(BItermcap\fP"
 it is unclear when reading and writing them is meaningful.
 In particular,
 some applications are reported to declare and/or modify
-.BR \%ospeed "."
+.IR \%ospeed "."
 .PP
 The constraint that only the first two characters of the
 .I id
-- 
2.30.2

Attachment: signature.asc
Description: PGP signature


reply via email to

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