[Top][All Lists]

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

[groff] 03/08: groff_char(7): Fix style nit.

From: G. Branden Robinson
Subject: [groff] 03/08: groff_char(7): Fix style nit.
Date: Thu, 8 Oct 2020 11:19:25 -0400 (EDT)

gbranden pushed a commit to branch master
in repository groff.

commit e5eb39075afa1b9c85a303581c963309f7f903fe
Author: G. Branden Robinson <>
AuthorDate: Fri Oct 9 01:21:37 2020 +1100

    groff_char(7): Fix style nit.
    Stop manually suppressing hyphenation of "Latin-1" and "UTF-8"; it is
    unnecessary because numerals do not have hyphenation codes by default,
    so these words will not hyphenate even with the explicit hyphen present.
    Thanks to Dave Kemper for catching this.
    Fixes item #2 in Savannah #57618.
 man/ | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/man/ b/man/
index 0dd62b2..f1a27e4 100644
--- a/man/
+++ b/man/
@@ -43,12 +43,12 @@ and mathematical documents.
 its input character set is restricted to that 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,
 .\" Yes, a subset, albeit a permutation as well in the cp1047 case.
@@ -180,7 +180,7 @@ and those employing IBM code page 1047 as \[lq]EBCDIC\[rq] 
 That said,
 EBCDIC systems that support
 .I groff
-are known to also support \%UTF-8.
+are known to also support UTF-8.
@@ -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.
 .\" ====================================================================
@@ -471,7 +471,7 @@ falling back to basic Latin glyphs only when necessary.
 .\" ====================================================================
-.SS "Eight-bit encodings and \%Latin-1 supplement"
+.SS "Eight-bit encodings and Latin-1 supplement"
 .\" ====================================================================
 ISO 646 is a seven-bit code encoding 128 code points;
@@ -480,7 +480,7 @@ eight-bit codes are twice the size.
 ISO 8859-1 and code page 1047 allocated the additional space to what
 Unicode calls \[lq]C1 controls\[rq]
 (control characters)
-and the \[lq]\%Latin-1 supplement\[rq].
+and the \[lq]Latin-1 supplement\[rq].
 The C1 controls are neither printable nor usable as
 .I groff
@@ -488,7 +488,7 @@ input.
-Two non-printing characters in the \%Latin-1 supplement are handled
+Two non-printing characters in the Latin-1 supplement are handled
@@ -511,15 +511,15 @@ on input it is mapped to the hyphenation control escape,
-The remaining characters in the \%Latin-1 supplement represent
+The remaining characters in the Latin-1 supplement represent
 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,
 shown below.

reply via email to

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