groff-commit
[Top][All Lists]
Advanced

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

[groff] 19/28: groff_char(7): Revise glyph table description.


From: G. Branden Robinson
Subject: [groff] 19/28: groff_char(7): Revise glyph table description.
Date: Tue, 1 Sep 2020 07:43:09 -0400 (EDT)

gbranden pushed a commit to branch master
in repository groff.

commit 11c44eebe20b9b46f9e32d972531503c56cbb284
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Tue Sep 1 20:44:20 2020 +1000

    groff_char(7): Revise glyph table description.
---
 man/groff_char.7.man | 59 ++++++++++++++++++++++++++++------------------------
 1 file changed, 32 insertions(+), 27 deletions(-)

diff --git a/man/groff_char.7.man b/man/groff_char.7.man
index 63d7c41..3a49218 100644
--- a/man/groff_char.7.man
+++ b/man/groff_char.7.man
@@ -749,8 +749,8 @@ glyph name repertoire is presented in tabular form.
 The meanings of the columns are as follows.
 .
 .
-.TP
-.I Output
+.TP 8n
+.B Output
 shows the glyph as it appears on the device used to render this
 document;
 although it can have a notably different shape on other devices
@@ -760,7 +760,7 @@ attempts reasonable equivalency on all output devices.
 .
 .
 .TP
-.I Input
+.B Input
 shows the
 .I groff
 character
@@ -773,33 +773,34 @@ Some code points have multiple glyph names.
 .
 .
 .TP
-.I AGL
+.B AGL
 gives the name of the glyph from the Adobe Glyph List (AGL).
 .
 .
 .TP
-.I Unicode
-is the glyph name used in Unicode special character escapes.
+.B Unicode
+is the code point notation for the glyph or combining glyph sequence as
+described in subsection \[lq]Special character escape forms\[rq] above.
 .
-The names in the Unicode column look like
-.B u0021
-or
-.BR u0041_0300 .
+It corresponds to the standard notation for Unicode short identifiers
+such that
+.IR groff 's
+.BI u nnnn
+is equivalent to Unicode's
+.RI U+ nnnn.
+.\" And thereby hangs a tale...
+.\" https://unicode.org/mail-arch/unicode-ml/y2005-m11/0060.html
 .
-In
-.IR groff ,
-the corresponding Unicode characters can be constructed by adding a
-backslash and a pair of square brackets,
-for example
-.B \[rs][u0021]
-or
-.BR \[rs][u0041_0300] .
 .
+.TP
+.B Notes
+describes the glyph,
+elucidating the mnemonic value of the glyph name where possible.
 .
-.P
-In the following,
-a plus sign \[lq]+\[rq] in the \[lq]Notes\[rq] column indicates that
-the glyph name appears in the AT&T
+.
+.IP
+A plus sign \[lq]+\[rq] indicates that the glyph name appears in the
+AT&T
 .I troff
 user's manual,
 CSTR\~#54
@@ -807,23 +808,27 @@ CSTR\~#54
 .
 When using the AT&T special character syntax
 .BI \[rs]( xx\c
-, portability can be expected from such names.
+, widespread portability can be expected from such names.
 .
 .
 .P
 Entries marked with \[lq]***\[rq] denote glyphs used for mathematical
 purposes.
 .
-Historically,
-such glyphs were typically drawn from a different font,
-the \[lq]special\[rq] font.
+On typesetter devices,
+such glyphs are typically drawn from a
+.I special
+font
+(see
+.I groff_font (@MAN5EXT@)).
+.
 .
 Often,
 such glyphs have metrics which look incongruous in normal text.
 .
 A few which are not uncommon in running prose have \[lq]text
 variants\[rq],
-and should work well in such contexts.
+which should work better in that context.
 .
 Conversely,
 a handful of glyphs that are normally drawn from a regular font are



reply via email to

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