Re: [Groff] Manpages, groff, and the browser.

2014-03-17 Thread Eric S. Raymond
Pierre-Jean : > > Actively supporting is empty verbiage unless you have a mechanical > > translator from man(7) markup to semantically enriched mdoc(7). You > > don't, and I know exactly why you don't, because I wrote the pattern > > analyzer you would need and don't have. > > Eric is wright: if d

Re: [Groff] Manpages, groff, and the browser.

2014-03-17 Thread Pierre-Jean
Hello alls, Kristaps Dzonsons wrote: > Even if groff(1) could do as above, and somehow carry over the original > macro language's "meaning", it'd be only as good as its input language. > To wit, Eric proposed extending man(7) with semantics to address > exactly that. And that would give u

Re: [Groff] Manpages, groff, and the browser.

2014-03-16 Thread Eric S. Raymond
Kristaps Dzonsons : > Browsers are confusing because HTML doesn't play with > character-driven media. And roff(7), into which groff(1) translates > man(7) and mdoc(7), is (significantly?) character-driven. We hack > around this by converting -Tascii output into -wrapped > documents. But that's n

[Groff] Manpages, groff, and the browser.

2014-03-16 Thread Kristaps Dzonsons
Hi folks, In the last few weeks, there's been some confusing mention of manpages on this list. Confusing because some of the issues raised, in my eyes, aren't really issues at all. So I thought I'd pipe up in the hopeful interests of clarity. To begin on familiar ground, by manpages I mean