[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[groff] 01/02: groff_char(7): Fix font problems.
G. Branden Robinson
[groff] 01/02: groff_char(7): Fix font problems.
Fri, 28 Aug 2020 07:34:29 -0400 (EDT)
gbranden pushed a commit to branch master
in repository groff.
Author: G. Branden Robinson <firstname.lastname@example.org>
AuthorDate: Wed Aug 26 21:26:25 2020 +1000
groff_char(7): Fix font problems.
...noted by Ingo Schwarze.
My removal of "low-level request flinging"
(d1847d1b1b3e4b7128c5f7ced6fda5723a60784d, 26 July) left behind some
font style switching damage. Repair it, replacing long sequences of
font and italic correction escapes with macro calls. Thanks, Ingo!
Also make editorial changes to subsections "8-bit character codes 160 to
255" and "Named glyphs" (the latter up to the first subsequent table).
I intend greater violence to this material later.
* Adapt font style choices and quotation conventions to those I've
been applying to other groff man pages.
* Use hyphens instead of underscores in metasyntactic parameter names.
* Use en-dashes in numeric ranges instead hyphen-minuses.
* Use the term "glyph name" (and abbreviations thereof for metasyntactic
parameters). Our documentation is elsewhere at some pains to
distinguish between characters and glyphs.
* Provide example: \[a] means \a, not "a".
* ISO does not put hyphens between their name and their standard
numbers. Say "ISO 8859" instead of "ISO-8859".
* Say "Latin-1", as that is the name of the character set in the ISO
8859 standard, instead of "\%latin1", which is the name of a groff
output device, and also doesn't need to be protected from hyphenation.
Solecisms like this make me question the writer's judgment of context.
* Recast non-idiomatic English.
man/groff_char.7.man | 167 +++++++++++++++++++++++++++++++++------------------
1 file changed, 108 insertions(+), 59 deletions(-)
diff --git a/man/groff_char.7.man b/man/groff_char.7.man
index 2074948..ab9027c 100644
@@ -396,43 +396,50 @@ _
.SS "8-bit character codes 160 to 255"
-They are interpreted as printable characters according to the
-.RI ( ISO-8859-1 )
-code set, being identical to the Unicode range
-.IR "Latin-1 Supplement" .
+Code points in the range 160\[en]255 are for the most part interpreted
+as characters according to the Latin-1 (ISO 8859-1) standard,
+and correspond to those in the same range of the Unicode \[lq]C1
+Controls and Latin-1 Supplement\[rq] code chart.
-Input characters in range 128\-159 (on non-EBCDIC hosts) are not
+Input characters in range 128\[en]159
+(the C1 controls on non-EBCDIC hosts)
+are defined as control characters and not printable;
+nor are two characters in the Latin-1 supplement.
-the ISO \%latin1
-.I no-break space
-is mapped to \[oq]\e\(ti\[cq], the stretchable space
+encodes the no-break space,
+and is mapped to
+.BR \[rs]\[ti] ,
+the adjustable non-breaking space escape.
-the soft hyphen control character.
+encodes the soft hyphen character.
-never uses this character for output (thus it is omitted in the table
-below); the input character\ 173 is mapped onto \[oq]\e%\[cq].
+never uses this character for output
+(thus it is omitted in the table below);
+on input it is mapped to the hyphenation control escape,
+.BR \[rs]% .
-The remaining ranges (\%161\-172, \%174\-255)
-are printable characters that print as themselves.
+The remaining characters in the Latin-1 supplement print as themselves.
Although they can be specified directly with the keyboard on systems
-with a \%latin1 code page, it is better to use their glyph names;
+configured to use Latin-1 as the character encoding,
+it is more portable,
+both to other
+systems and to UTF-8 environments,
+to use their glyph names;
see the next section.
@@ -544,7 +551,7 @@ _
Glyph names can be embedded into the document text by using escape
-.BR groff (@MAN7EXT@)
+.IR groff (@MAN7EXT@)
describes how these escape sequences look.
Glyph names can consist of quite arbitrary characters from the
@@ -553,52 +560,80 @@ ASCII or \%latin1 code set, not only alphanumeric
Here some examples:
-A glyph having the 2-character name
-.IR ch .
+.BI \[rs]( gl
+is a special character escape for the glyph with the 2-character name
+.IR gl .
-A glyph having the name
-(having length 1, 2, 3, \&.\|.\|.).
-Note that \[oq]\fIc\fP\[cq] is not the same as
-\[oq]\e[\fP\,\fIc\/\fP]\[cq] (\,\fIc\ a single
-character): The latter is internally mapped to glyph name
+.BI \[rs][ glyph-name ]
+is a special character escape for
+.IR glyph-name ,
+which can be of arbitrary length.
+Note that an ordinary input character
+.RI \[lq] c \[rq]
+is not the same as
+.BI \[rs][ c ]\c
+the latter is internally mapped to glyph name
+.RB \[lq] \[rs] \c
+.IR c \[rq].
+In other words,
+.RB \[lq] \[rs][a] \[rq]
+is not \[lq]a\[rq],
+.BR \[rs]a ,
+the uninterpreted leader escape sequence.
+defines a single glyph name of length one,
+namely the hyphen-minus,
+which can be accessed as either
+.BR \[rs][\-] .
-By default, groff defines a single glyph name starting with a
-backslash, namely \%\[oq]\e-\[cq], which can be either accessed as
-\[oq]\e\-\[cq] or \[oq]\e[-]\[cq].
-\e[\fP\,\fIbase_glyph composite_1 composite_2 \&.\|.\|.\/\
-A composite glyph; see below for a more detailed description.
+.BI \[rs][ "base-glyph composite-1 composite-2"\~\c
+.IB composite-n ]
+is a composite glyph;
+see below for a more detailed description.
-In groff, each \%8-bit input character can also referred to by the
-is the decimal code of the character, a number between 0 and\ 255
-without leading zeros (those entities are
+.IR groff ,
+each eight-bit input character can also be referred to by the construct
+.BI \[rs][char NNN ]\c
+is the decimal code of the character,
+a number between 0 and\~255
+without leading zeroes.
+These entities are
-They are normally mapped onto glyphs using the .trin request.
+They are normally mapped onto glyphs using the
Another special convention is the handling of glyphs with names directly
derived from a Unicode code point; this is shown in the
-\[oq]Unicode\[cq] column of the table below.
+\[lq]Unicode\[rq] column of the table below.
-In general, all glyphs not having a name as listed in this manual page
-can be accessed with the
+all glyphs not having a name as listed in this manual page can be
+accessed with the
+.BI \[rs][u XXXX ]
Refer to section \[lq]Using Symbols\[rq] in
@@ -612,21 +647,35 @@ glyph names are constructed.
-Moreover, new glyph names can be created by the .char request;
+new glyph names can be created by the
-.BR groff (@MAN7EXT@).
+.IR groff (@MAN7EXT@).
-In the following, a plus sign \[oq]+\[cq] in the \[oq]Notes\[cq] column
-indicates that this particular glyph name appears in the PS version of
-the original troff documentation, CSTR\ 54.
+In the following,
+a plus sign \[lq]+\[rq] in the \[lq]Notes\[rq] column indicates that
+the glyph name appears in the AT&T
+When using the AT&T special character syntax
+.BI \[rs]( xx\c
+, portability can be expected from such names.
-Entries marked with \[oq]***\[cq] denote glyphs for mathematical
-purposes (mainly used for DVI output).
+Entries marked with \[lq]***\[rq] denote glyphs used for mathematical
+such glyphs have metrics which look incongruous in normal text.
-Normally, such glyphs have metrics which make them unusable in normal
+A few which are not uncommon in running prose have \[lq]text
+and should work well in such contexts.
@@ -1403,7 +1452,7 @@ a short reference of the groff formatting language
-.IR "An extension to the troff character set for Europe" ,
+\[lq]An extension to the troff character set for Europe\[rq],
E.G.\& Keizer, K.J.\& Simonsen, J.\& Akkerhuis; EUUG Newsletter,
Volume 9, No.\& 2, Summer 1989
|[Prev in Thread]
||[Next in Thread]|
- [groff] 01/02: groff_char(7): Fix font problems.,
G. Branden Robinson <=