[Top][All Lists]

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

[groff] 10/48: doc/groff.texi (Input Encodings): Tighten wording.

From: G. Branden Robinson
Subject: [groff] 10/48: doc/groff.texi (Input Encodings): Tighten wording.
Date: Fri, 31 Mar 2023 08:33:07 -0400 (EDT)

gbranden pushed a commit to branch branden-2023-03-31
in repository groff.

commit fdb69f81473eb9df093dc17814047f2def9455a1
Author: G. Branden Robinson <>
AuthorDate: Wed Mar 22 17:37:04 2023 -0500

    doc/groff.texi (Input Encodings): Tighten wording.
    Also annotate a future direction for development of this document.
 doc/groff.texi | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/doc/groff.texi b/doc/groff.texi
index ac045b0da..70f0481e0 100644
--- a/doc/groff.texi
+++ b/doc/groff.texi
@@ -5452,6 +5452,11 @@ load it with the @code{mso} (``macro source'') request.
 @c ---------------------------------------------------------------------
+@c TODO: Move a lot of this node to the "Invoking groff" chapter.  Some
+@c of the discussion is better placed in discussion of output drivers
+@c (e.g., what character encodings _they_ support for output and their
+@c responsibility for converting to them) as well.
 @node Input Encodings, Input Conventions, Macro Packages, Text
 @subsection Input Encodings
@@ -5495,8 +5500,7 @@ are interchangeable in their first 128 code 
 with the successive standards, a cause of some frustration among man
 page writers; see the @cite{groff_char@r{(7)}} man page.}
-The remaining encodings require support that is not built-in to the GNU
-@code{troff} executable; instead, they use macro packages.
+Other encodings are supported by means of macro packages.
 @table @code
 @item latin2

reply via email to

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