Re: Future of groff Texinfo manual (was: documentation of hyphenation)

2020-06-30 Thread James K. Lowden
On Mon, 29 Jun 2020 20:36:31 +0200 Ingo Schwarze wrote: > I don't see any practical relevance to the question where exactly the > boundary between the "user manual" and the "reference manual" part > is. I'm not sure what you're saying. If you mean you don't know how you would divide the curre

Re: Future of groff Texinfo manual (was: documentation of hyphenation)

2020-06-30 Thread James K. Lowden
On Tue, 30 Jun 2020 03:08:04 +1000 "G. Branden Robinson" wrote: > 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 doc

Re: Future of groff Texinfo manual (was: documentation of hyphenation)

2020-06-30 Thread John Gardner
Well said, James. Fully agreed on all points. > A convenient GUI viewer -- with hyperlinks and proportional fonts -- > would "advertise" groff and cement its position as the best free > documenation system there is, bar none. I started work on such a thing. Basically, it's an Electron-based front

Re: Future of groff Texinfo manual (was: documentation of hyphenation)

2020-06-30 Thread G. Branden Robinson
At 2020-06-30T04:18:00+1000, John Gardner wrote: > 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 Texinfo can is compile binary `.info` files. But even > that could be achieved by adding a new po

Re: Future of groff Texinfo manual (was: documentation of hyphenation)

2020-06-30 Thread Ingo Schwarze
Hi James, James K. Lowden wrote on Tue, Jun 30, 2020 at 09:45:17AM -0400: > On Mon, 29 Jun 2020 20:36:31 +0200 Ingo Schwarze wrote: >> I don't see any practical relevance to the question where exactly the >> boundary between the "user manual" and the "reference manual" part >> is. > I'm not su