I don't usually post to this list but I have a couple of ideas to keep in mind. I know XML is really low on the totem pole but if you bear with me for a moment I have some ideas that will retain both functionalities. I'm not sure how familiar many of you are with XSLT (and XML Formatting Objects) but it allows you to take an XML document and transform it into just about anything you want. I have an O'Reilly book that has some interesting examples of where they turn XML text into images, 3D OpenGL/VRML, etc. Sorry I don't have the title with me. Anyway, the way I see it there could be three pieces to this puzzle. First you would need an XML Schema for defining the format of all new documentation. Then, two XSLT transform templates. One XSLT would convert from XML to HTML as used in the below mentioned html doc files, and another could convert to a text file which could be cat'd to be viewed similarly to a man command. In fact, you could probably use a shell script or very small application to apply the XSLT whenever you type man. Just some ideas to kick around, Nick -----Original Message----- From: openbeos-bounce@xxxxxxxxxxxxx [mailto:openbeos-bounce@xxxxxxxxxxxxx] On Behalf Of Axel Dörfler Sent: Wednesday, March 03, 2004 1:53 PM To: openbeos@xxxxxxxxxxxxx Subject: [openbeos] Re: Checkins Michael Phipps <mphipps1@xxxxxxxxxxxxxxxx> wrote: > Yeah, now that you mention it, it did exist. I do vaguely remember > that. I > guess, then, the right thing to do is for us to code our own > documentation in > html and check it in, along with the new documentation for the GNU > utils. > > Then I think that we need to include lynx or something so that we > have > "man"-like capability from the commandline. :-D Oh no, please no lynx. I like "man" but only for its informations not for its usability. I think we should have a "man" command that just opens the HTML page with the standard web browser. It would even be more convenient as it wouldn't block the terminal. Bye, Axel.