gbranden pushed a commit to branch master
in repository groff.

commit 44bff8db1b0b54a93bb193d8d6560561cf2676b6
Author: G. Branden Robinson <[email protected]>
AuthorDate: Mon Oct 6 04:56:36 2025 -0500

    groff_man_style(7): Update portability advice.
    
    Man pages don't need to be stored on disk in Basic Latin only,
    especially if the system's man(1) formatter runs groff(1) with the `-k`
    option (or `-K utf8`, or whatever encoding the environment needs, or
    otherwise arranges for troff(1) to see only Basic Latin).
    
    We fib a little here; GNU troff actually accepts not just ISO Basic
    Latin (ISO 646) but its superset ISO Latin-1 (ISO 8859-1).  However
    someday I hope to make that fact false and support UTF-8 input; see
    Savannah #40720.
    
    Also fix section suffix on preconv(1) cross reference to correctly
    reflect the build configuration.
---
 tmac/groff_man.7.man.in | 16 ++++++++++++----
 1 file changed, 12 insertions(+), 4 deletions(-)

diff --git a/tmac/groff_man.7.man.in b/tmac/groff_man.7.man.in
index 81149a413..519759e15 100644
--- a/tmac/groff_man.7.man.in
+++ b/tmac/groff_man.7.man.in
@@ -2548,16 +2548,24 @@ just as you would test code.
 .SS Portability
 .\" ====================================================================
 .
-An installed man page should contain Unicode basic Latin code points
+GNU
+.I troff \" GNU
+expects its input to contain Unicode basic Latin code points
 exclusively.
 .
 One can
 .I maintain
 it in a more convenient encoding,
 using
-.MR preconv 1
-to produce a basic Latin version that employs special character escape
-sequences to access code points necessary in non-English text.
+.MR preconv @MAN1EXT@ ,
+as with
+.MR groff @MAN1EXT@ 's
+.B \-k
+option,
+to generate a basic Latin version
+that employs special character escape sequences
+to access other glyphs.
+.
 .
 .
 .P

_______________________________________________
groff-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/groff-commit

Reply via email to