Colin Watson :
> Right. I implemented Eric's $BROWSER spec in 2001, but I think that's
> the only idea of his in man-db at the moment. The change Eric's
> referring to is in the other Linux man package as of version 1.6; but as
> you say the BSDs use their own things, and as of earlier this year
On Fri, Feb 28, 2014 at 07:53:34PM +0100, Ingo Schwarze wrote:
> Eric S. Raymond wrote on Fri, Feb 28, 2014 at 12:15:35PM -0500:
> > 2. Some time ago I added to Linux man(1) the capability to recognize
> > HTML pages in the man hierachy and kick them over to the user's Web
> > browser. All Linux a
Tadziu Hoffmann wrote (Wed, 26 Feb 2014
23:06:17 +0100):
>
> > Three browsers, three layouts (surf uses webkit).
>
> Hmmm, well, I suspect if you used groff with -Tlatin1, -Tlj4,
> -Tdvi, and -Tps you might also get four different layouts...
> Simply consider different browsers like different d
Hi Federico,
Ralph Corderoy wrote on Sat, Mar 01, 2014 at 11:29:08AM +:
> Federico wrote:
>> While we are (slightly) digressing, may I ask the broader group, what
>> are the best current tutorials for Groff?
>>
>> Most of the material I know of is... rather dated. Not necessarily
>> bad, but
> Yes, HTML output from makeinfo does exist (I have contributed code to
> that mode of makeinfo myself). It's a kludge, though, and not much
> used. Tellingly, the various pieces of HTML you can produce from
> Texinfo sources are not even properly cross-linked to *each other*,
> let alone to t
Ralph Corderoy :
> Important though a lightweight input format is, a lightweight set of
> tools for rendering it in the comman output formats is also needed.
> From others' comments it appears asciidoc doesn't give that at the
> moment.
Nor does Texinfo, if the same standards were applied.
> This
On Sat 01 Mar 2014 11:29:08 Ralph Corderoy wrote:
> Then there's Dale Dougherty and Tim O'Reilly's _Unix Text Processing_.
> http://home.windstream.net/kollar/utp/ Given they were using troff to
> produce their books, and continued to use groff for a long time to do
> the production even when they
Hi Eric,
> Where we're probably going is that (a) info will die, to be replaced
> by HTML browsed from within Emacs, and (b) Texinfo will be replaced by
> a modern lightweight format that can render to both print and HTML;
> most likely asciidoc.
Important though a lightweight input format is, a
Hi Federico,
> While we are (slightly) digressing, may I ask the broader group, what
> are the best current tutorials for Groff?
>
> Most of the material I know of is... rather dated. Not necessarily
> bad, but not very recent either - and not very concise, either. What
> do you point to get new
