groff-commit
[Top][All Lists]
Advanced

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

[groff] 01/06: NEWS: Add item for \n[.cp].


From: G. Branden Robinson
Subject: [groff] 01/06: NEWS: Add item for \n[.cp].
Date: Sun, 19 Apr 2020 01:49:56 -0400 (EDT)

gbranden pushed a commit to branch master
in repository groff.

commit f25eba40278f5a6b8b370193755c2341722bc641
Author: G. Branden Robinson <address@hidden>
AuthorDate: Fri Apr 17 20:41:22 2020 +1000

    NEWS: Add item for \n[.cp].
    
    Also use more correct nomenclature for other *roffs.
    
    ChangeLog: Add summary of what \n[.cp] actually _is_.
---
 ChangeLog |  3 +++
 NEWS      | 10 +++++++---
 2 files changed, 10 insertions(+), 3 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 5566eea..f32b2f7 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -2,6 +2,9 @@
 
        Implement new read-only .cp register.
 
+       Within a .do request, \n[.cp] holds the saved value of
+       compatibility mode.
+
        The register \n[.cp] is specialized and may require a statement
        of rationale.  When writing macro packages or documents that use
        groff features and which may be mixed with other packages or
diff --git a/NEWS b/NEWS
index 5461678..dabc3c0 100644
--- a/NEWS
+++ b/NEWS
@@ -13,19 +13,23 @@ VERSION 1.22.5
 Troff
 -----
 
+o A new read-only register ".cp" is implemented.  Within a .do request,
+  "\n[.cp]" holds the saved value of compatibility mode.  See groff_diff(7)
+  or the Texinfo manual for rationale, use case, and example.
+
 o Point-size escapes of the form '\sNN', where NN is in the range 10-39, are
   now recognized only in compatibility mode (groff -C); when encountered an
   error diagnostic is emitted.  In normal mode, \sN is interpreted as
   setting the point size to the single digit value N, which ends the escape.
   This change eliminates a quirk in the language grammar that dates back to
   1976 (AT&T troff by Ossanna) but apparently was not documented until 1992
-  when Kernighan updated CSTR #54 for AT&T ditroff.
+  when Kernighan updated CSTR #54 for AT&T troff.
 
   The form '\s(NN' is accepted for two-digit point sizes in all known
   troffs.  The form '\s[NNN]' accepts a numeric expression of variable
   length; it has been supported by groff since version 1.02 (June 1991) at
-  the latest and is by current versions of Heirloom troff and neatroff.  The
-  form "\s'NNN'" is also widely supported.
+  the latest and is by current versions of Heirloom Doctools troff and
+  neatroff.  The form "\s'NNN'" is also widely supported.
 
   Short version: in your documents, rewrite escapes beginning with '\s1',
   '\s2', or '\s3' in an unambiguous and portable form.  For instance, '\s36'



reply via email to

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