On 6/29/20, Ingo Schwarze wrote:
> I like the idea of converting it to -ms somewhat less. I mean, we
> have groff documentation split out into info(1), man(1), and HTML
> (for mom) - do we really need a fourth format?
It's more than three currently. The pic(1) manual doc/pic.ms is
already in -m
On Mon, 29 Jun 2020 14:36:31 -0400,
> G. Branden Robinson wrote on Tue, Jun 30, 2020 at 03:08:04AM +1000:
> > [1] The only painful part of this is losing Larry Kollar's ms node,
> > which is the _only_ macro package that has ever documented well in
> > Texinfo as far as I can tell. I think it woul
Branden,
Excellent fixes. Thank you!
Doug
> I never saw the point of groff_diff(7).
It's an excellent summary of how groff differs to classical troff,
highlights potential portability issues (a.k.a., "groff-isms"), and also
documents known incompatibilities with legacy syntax.
If maintaining groff_diff(7) alongside another document with
Hi Branden,
G. Branden Robinson wrote on Tue, Jun 30, 2020 at 03:08:04AM +1000:
> == PROPOSAL ==
>
> Chapter 1 (Introduction): Retain.
> Chapter 2 (Invoking groff): Drop; direct users to groff(1).
> Chapter 3 (Tutorial for Macro Users): Retain.
> Chapter 4 (Macro Packages): Drop. (See [1] below.
> There is a place for a book-like work, I think.
I agree, but using a different typesetting system to prepare it is a wasted
opportunity, IMHO. Groff *can* generate high-quality manuals, it *can* generate
HTML output, and it *can* generate indexes — AFAIK, the only thing it
*can't* do that Texinf
At 2020-06-14T14:40:44+1000, John Gardner wrote:
> Why are we using Info, again? Was it because of GNU policy?
Yes. https://www.gnu.org/prep/standards/standards.html#GNU-Manuals
Aside from the mandate of the source document format, I find the advice
there fairly sound, as far as it goes. I do w
Hi Doug!
At 2020-06-13T15:42:00-0400, Doug McIlroy wrote:
> groff(7) doesn't tell what the hyphenation modes are.
It does, but you have to know to scroll down to the "Hyphenation"
section of the page. I've just now committed a fix for this and several
other issues.
> It directs you to info for
