[bug #60061] [long-term] narrow the scope of the groff Texinfo manual

Dave <[email protected]> Fri, 10 Jul 2026 10:21:34 -0400 (EDT)

Newsgroups	gmane.comp.printing.groff.bugs
Message-ID	<[email protected]>

Follow-up Comment #19, bug #60061 (group groff):

Branden wrote this to me in bug #68500 but it's more pertinent here:
----
As the record elsewhere records, you don't like our Texinfo manual elevati
_ms_(7) above other full-service macro packages by presenting it, and only it,
in detail.  (And, to be fair, I tire of maintaining _three_ copies of its
documentation: "doc/groff.texi.in", "doc/ms.ms.in", and
"tmac/groff_ms_7.man").  But I've been reluctant to remove it because I've
lacked any other example of full-service package usage concrete enough to suit
the needs of learners who have a harder time reasoning from the abstractions
presented in the preceding "Tutorial for Macro Package Users" chapter.

So my idea was, well, why not take a sample document, like a basic business
letter, and show how to compose it in _each_ of our full-service macro
packages _me_, _mm_, _mom_, and _ms_.  _groff_ input goes on the verso page,
and a rasterized image of the full page rendering on the facing recto page.

Then illustrate a basic man page in _man_ and _mdoc_ the same way.

Thus, our new Chapter 4.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?60061>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

signature.asc (application/pgp-signature, 228 B)