[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[groff] 01/19: groff_char(1): Clarify valid spec character names.
From: |
G. Branden Robinson |
Subject: |
[groff] 01/19: groff_char(1): Clarify valid spec character names. |
Date: |
Thu, 16 Sep 2021 08:58:58 -0400 (EDT) |
gbranden pushed a commit to branch master
in repository groff.
commit 8972736b2d53a398631239ad95cc7ddbc84ce344
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Mon Sep 13 10:33:08 2021 +1000
groff_char(1): Clarify valid spec character names.
Also tighten wording.
---
man/groff_char.7.man | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/man/groff_char.7.man b/man/groff_char.7.man
index 27e549f..6147a02 100644
--- a/man/groff_char.7.man
+++ b/man/groff_char.7.man
@@ -65,9 +65,7 @@ AT&T
in the 1970s faced a similar problem of typesetter devices with a glyph
repertoire differing from that of the computers that controlled them.
.
-The solution
-.I troff
-adopted was a form of escape sequence known as a
+Its solution was a form of escape sequence known as a
.I special character
to access several dozen additional glyphs available in the fonts
prepared for mounting in the phototypesetter.
@@ -613,8 +611,13 @@ whereas glyph names originated in AT&T
special character escape sequences.
.
Glyph names are not limited to alphanumeric characters;
-any of the printable characters from the Unicode basic Latin repertoire
-may be used.
+any character that is valid in a
+.I groff
+identifier may be used.
+.
+Predefined glyph names use only characters in the basic Latin
+repertoire,
+however.
.
.
.TP
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [groff] 01/19: groff_char(1): Clarify valid spec character names.,
G. Branden Robinson <=