From owner-freebsd-hackers Mon Jan 13 10:48:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA28571 for hackers-outgoing; Mon, 13 Jan 1997 10:48:04 -0800 (PST) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA28556 for ; Mon, 13 Jan 1997 10:47:56 -0800 (PST) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.4/8.8.4) with SMTP id NAA00591; Mon, 13 Jan 1997 13:32:30 -0500 (EST) Date: Mon, 13 Jan 1997 13:32:29 -0500 (EST) From: John Fieber To: hoek@freenet.hamilton.on.ca cc: eivind@dimaga.com, FreeBSD hackers , Joerg Wunsch Subject: Re: new texinfo is busted! In-Reply-To: <199701121544.KAA18539@james.freenet.hamilton.on.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 12 Jan 1997 hoek@freenet.hamilton.on.ca wrote: > In Email, Eivind Eklund wrote: > > > > I'm in favour. I haven't yet seen a good browser for info, and it is pain > > to get the ones that exist to even open the files. While we're at it, it > > would even be nice to have the man-pages as HTML - not as a replacement > > format, but as an alternative. > > Rewrite them all in docbook, and you'd probably be just about set. I've > seen a docbook->man thingy somewhere and I'm sure docbook->html exists, > too. The docbook->html exists in freebsd-current actually. :) TeXinfo->docbook + mdoc->docbook and the system is complete. Well, I still don't have docbook->groff, but that is just a matter of when, not if. For man pages, docbook to HTML is faster than mdoc to ascii. Docbook to ascii or postscript will be slower since it goes through groff, plus docbook to groff conversion. For our linuxdoc legacy documents (handful of tutorials, FAQ and handbook), my linuxdoc->docbook converter is working quite well considering the bogosities of the linuxdoc DTD and the subsequent bogous markup practices found in the handbook/FAQ and the many linuxdoc HOWTO's I've been testing it on. It isn't 100% automatic--some documents need manual tweaks before conversion, and all need work after to take full advantage of the much richer docbook DTD. If we are talking about an alternate format from which other formats can be derived, HTML is ***not*** appropriate. Docbook was designed specifically for software documentation and it works quite well in my experience. -john