Re: [Groff] Simplifying groff documentation

2006-12-24 Thread Gunnar Ritter
Werner LEMBERG <[EMAIL PROTECTED]> wrote: > > > I would claim it is. The groff manual pages also cannot be > > > displayed properly by other manual page viewers. There are > > > some glitches even with Heirloom troff; although it can handle > > > the language, some groff-specific macros do not exi

Re: [Groff] Simplifying groff documentation

2006-12-24 Thread Gunnar Ritter
M Bianchi <[EMAIL PROTECTED]> wrote: > +-+ ++ > | man pages |-+ +--->| HTML on browsers | > +-+ | / ++ > |

Re: Re: [Groff] Re: Simplifying groff documentation

2006-12-24 Thread M Bianchi
On Sat, Dec 23, 2006 at 10:26:43PM -0500, Larry Kollar wrote: > : > The problem with using XML for documentation is that it was > designed specifically for machine processing -- and *people* > write documents for *other* people. I agree and think this is _very_ important. groff -mm and -ms

Re: Re: [Groff] Re: Simplifying groff documentation

2006-12-24 Thread M Bianchi
On Sun, Dec 24, 2006 at 01:35:09AM -0500, Eric S. Raymond wrote: > : > This is a much richer ontology than HTML, so man -> DocBook -> HTML > produces best possible HTML. man -> HTML, on the other hand, ends up > translating man pages into a sort of least-common-denominator ontology > between

[Groff] Re: Simplifying groff documentation

2006-12-24 Thread Eric S. Raymond
Werner LEMBERG <[EMAIL PROTECTED]>: > > 1) It would address the issue by adding complexity to the markup and > >the interpretation path, rather than subtracting it. > > Not necessarily. Currently, you are applying doclifter's heuristic > engine to guess a high-level structure of a man page (c

Re: [Groff] Simplifying groff documentation

2006-12-24 Thread Eric S. Raymond
Gunnar Ritter <[EMAIL PROTECTED]>: > > Well, does this mean that I should refrain from using any GNU > > extensions in man pages? > > Yes, I recommend that. As you know, I like most of them and > have re-implemented them accordingly in Heirloom troff, so > this is not an argument against groff ext

Re: [Groff] Simplifying groff documentation

2006-12-24 Thread Eric S. Raymond
Gunnar Ritter <[EMAIL PROTECTED]>: > But I think the most important question for troff people is, > where is a complete, high-quality converter for > >+-+/ +===+ >| XML-DocBook |===>| troff | ? >+-+\ +

Re: Re: [Groff] Re: Simplifying groff documentation

2006-12-24 Thread Eric S. Raymond
M Bianchi <[EMAIL PROTECTED]>: > Since DocBook deduces _meaning_ from the presentation markup DocBook does nothing of the sort. It's doclifter that does that. > then I will claim > that the correct path needs to be something like ... > groff -man ->

[Groff] An attempt to make Werner happy :-)

2006-12-24 Thread Eric S. Raymond
Enclosed version of groff.1 uses only standard man macros and .de; I've inserted .in and .br macros to make the Synopis pretty again. -- http://www.catb.org/~esr/";>Eric S. Raymond fixed-groff.man Description: Unix manual page ___ Groff

Re: [Groff] An attempt to make Werner happy :-)

2006-12-24 Thread M Bianchi
On Sun, Dec 24, 2006 at 04:48:50PM -0500, Eric S. Raymond wrote: > Enclosed version of groff.1 uses only standard man macros and .de; > I've inserted .in and .br macros to make the Synopis pretty again. Woops! I apologize. I've been looking at _very_ old versions of the man page source. I think

Re: [Groff] Simplifying groff documentation

2006-12-24 Thread mhobgood
On Dec 24, 2006, at 12:01 PM, Eric S. Raymond wrote: Gunnar Ritter <[EMAIL PROTECTED]>: But I think the most important question for troff people is, where is a complete, high-quality converter for +-+/ +===+ | XML-DocBook |===>| troff |

Re: [Groff] Simplifying groff documentation

2006-12-24 Thread Eric S. Raymond
mhobgood <[EMAIL PROTECTED]>: > For those of us not up to speed on all the current jargon, would you > explain what XSL and FO are? http://www.w3.org/TR/2001/REC-xsl-20011015/ You can think of it as a sort of XML-world equivalent of TeX or PostScript. The idea is that XML applications needing