[Top][All Lists]

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

[groff] 03/24: groff_man*(7): Clarify `\(` identifier coverage.

From: G. Branden Robinson
Subject: [groff] 03/24: groff_man*(7): Clarify `\(` identifier coverage.
Date: Tue, 27 Dec 2022 04:22:43 -0500 (EST)

gbranden pushed a commit to branch master
in repository groff.

commit 2bd5ac16fd685a43723e2a52e1615dbb4a451d81
Author: G. Branden Robinson <>
AuthorDate: Wed Dec 21 15:03:15 2022 -0600

    groff_man*(7): Clarify `\(` identifier coverage.
 tmac/ | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/tmac/ b/tmac/
index d6082663b..92952bc17 100644
--- a/tmac/
+++ b/tmac/
@@ -2671,15 +2671,20 @@ escape sequences do.
 Several special characters are also widely portable.
+.\" meaning: groff, Heirloom Doctools troff, neatroff, mandoc
 .I troff
-did not `define' the reverse solidus or quotation characters listed
-but any of its descendants,
+did not consistently `define' the characters listed below,
+.\" Only \-, \(em, and \(ga were documented in CSTR #54 (1976).  CSTR
+.\" #54 (1992) offers no _comprehensive_ list but shows \(en in its
+.\" PostScript DESC file example.  In DWB 3.3, \(aq was supported by the
+.\" "post" device, and \(dq by "pcl" and "Latin1".
+but its descendants,
 like Plan\~9 or Solaris
 .IR troff , \" Plan 9, Solaris
-can support them by defining their glyphs in font description files;
+can be made to support them by defining them in font description files,
+making them aliases of existing glyphs if necessary;
 .MR groff_font @MAN5EXT@ .

reply via email to

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