groff-commit
[Top][All Lists]
Advanced

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

[groff] 06/18: doc/groff.texi (Input Encodings): Recast.


From: G. Branden Robinson
Subject: [groff] 06/18: doc/groff.texi (Input Encodings): Recast.
Date: Thu, 3 Jun 2021 11:03:21 -0400 (EDT)

gbranden pushed a commit to branch master
in repository groff.

commit db017a79021e72a2d71c5dae7ed6fd6c68ffe687
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Wed Jun 2 21:23:50 2021 +1000

    doc/groff.texi (Input Encodings): Recast.
---
 doc/groff.texi | 32 +++++++++++++++++---------------
 1 file changed, 17 insertions(+), 15 deletions(-)

diff --git a/doc/groff.texi b/doc/groff.texi
index bb9471a..fac5519 100644
--- a/doc/groff.texi
+++ b/doc/groff.texi
@@ -5104,27 +5104,29 @@ of your document or use @samp{-mlatin9} as a 
command-line argument to
 @code{groff}.
 @end table
 
-Some input encoding characters may not be available for a particular
-output driver.  For terminal devices, fallbacks are defined, like
+Some characters from an input encoding may not be available with a
+particular output driver, or their glyphs may not have representation in
+the font used.  For terminal devices, fallbacks are defined, like
 @samp{EUR} for the Euro sign and @samp{(C)} for the copyright sign.  For
-typesetter devices it usually suffices to install fonts that have
-compatible metrics with other fonts used in the document and which
-contain the necessary glyphs.
+typesetter devices, it usually suffices to install fonts that contain
+the necessary glyphs and have compatible metrics with other fonts used
+in the document.
 
 @pindex freeeuro.pfa
 @pindex ec.tmac
 Due to the importance of the Euro glyph in Europe, @code{groff} is
 distributed with a PostScript font called @file{freeeuro.pfa}, which
-provides various glyph shapes for the Euro.  In other words, @w{Latin-9}
-encoding is supported for the @option{ps} driver out of the box
-(@w{Latin-2} isn't).
-
-The @option{utf8} driver supports characters from all other input
-encodings.  The @option{dvi} driver has support for both @w{Latin-2} and
-@w{Latin-9} if the command-line option @option{-mec} is used also to
-load the file @file{ec.tmac}.@footnote{This macro file uses the EC fonts
-instead of the Computer Modern (CM) fonts (the DVI output driver
-default).}
+provides various glyph shapes for the Euro.  Thus, the
+@w{Latin-9} encoding is supported for the @option{ps} and @option{pdf}
+drivers out of the box, while @w{Latin-2} is is not.
+
+Unicode supports characters from all other input encodings; the
+@option{utf8} output driver for terminals therefore does as well.  The
+DVI output driver supports both the @w{Latin-2} and @w{Latin-9}
+encodings if the command-line option @option{-mec} is used as well.
+@footnote{The DVI output device defaults to using the Computer Modern
+(CM) fonts; @file{ec.tmac} loads the EC fonts instead, which have
+greater code point coverage.}
 
 @c ---------------------------------------------------------------------
 



reply via email to

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