[groff] 08/28: groff_char(7): Prevent hyphenation of identifiers.

[G. Branden Robinson]

gbranden pushed a commit to branch master
in repository groff.

commit 7f1d9a01c213adc6167369ad9c9361b62c25d3f6
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Sun Aug 30 09:15:56 2020 +1000

    groff_char(7): Prevent hyphenation of identifiers.
    
    ...namely, "Latin-1", "8859-1", "UTF-8", and "US-ASCII".
    
    None of these should be broken and they should have minimal impact on
    adjustment.  The worst offender, "US-ASCII", only occurs once.  The
    others cost only a figure width.
---
 man/groff_char.7.man | 27 ++++++++++++++-------------
 1 file changed, 14 insertions(+), 13 deletions(-)

diff --git a/man/groff_char.7.man b/man/groff_char.7.man
index 596de22..e67bd40 100644
--- a/man/groff_char.7.man
+++ b/man/groff_char.7.man
@@ -43,14 +43,14 @@ and mathematical documents.
 .
 However,
 its input encoding is restricted to those defined by the standards
-ISO Latin-1
-(ISO 8859-1)
+ISO \%Latin-1
+(ISO \%8859-1)
 and IBM code page 1047
 (an arrangement of EBCDIC).
 .
-For ease of document maintenance in UTF-8 environments,
+For ease of document maintenance in \%UTF-8 environments,
 it is advisable to use only the Unicode basic Latin code points,
-a subset of all of the foregoing historically referred to as US-ASCII,
+a subset of all of the foregoing historically referred to as \%US-ASCII,
 .\" Yes, a subset, albeit a permutation as well in the cp1047 case.
 which has only 94 visible,
 printable code points.
@@ -180,7 +180,7 @@ and those employing IBM code page 1047 as \[lq]EBCDIC\[rq] 
systems.
 That said,
 EBCDIC systems that support
 .I groff
-are known to also support UTF-8.
+are known to also support \%UTF-8.
 .
 .
 .P
@@ -218,7 +218,7 @@ are invalid.
 Some of these code points are used by
 .I groff
 for internal purposes,
-which is one reason it does not support UTF-8 natively.
+which is one reason it does not support \%UTF-8 natively.
 .
 .
 .\" ====================================================================
@@ -228,7 +228,7 @@ which is one reason it does not support UTF-8 natively.
 These are the basic glyphs having 7-bit ASCII code values assigned.
 .
 They are identical to the printable characters of the
-character standards \%ISO-8859-1 (\%latin1) and Unicode (range
+character standards ISO \%8859-1 (\%latin1) and Unicode (range
 .IR "Basic Latin" ).
 .
 The glyph names used in composite glyph names are \[oq]u0020\[cq] up
@@ -362,16 +362,16 @@ _
 .\" ====================================================================
 .
 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,
+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.
+Controls and \%Latin-1 Supplement\[rq] code chart.
 .
 .
 .P
 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.
+nor are two characters in the \%Latin-1 supplement.
 .
 .
 .TP
@@ -396,14 +396,15 @@ on input it is mapped to the hyphenation control escape,
 .
 .
 .P
-The remaining characters in the Latin-1 supplement 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
-configured to use Latin-1 as the character encoding,
+configured to use \%Latin-1 as the character encoding,
 it is more portable,
 both to other
 .I roff
-systems and to UTF-8 environments,
+systems and to \%UTF-8 environments,
 to use their glyph names;
 see the next section.
 .