Re: [SLUG] Tools for documentation.

[Rodos <rodos@nospam.haywood.org>]

On Mon, 26 Jun 2000, Jeff Waugh wrote:

> > So we need to find out what Rodos wants to document (then can we have a
> > DocBook/LaTeX flame war?). 
> 
> Sure.
> 
> Rodos? Clarify please, Michael and I are up for a flame.

Don't let me hold you guys back. 

I am wanting to document a software project, but mainly the hardware and
configuration site. I need to incorporate some schematic diagrams
(xcircuit) and some pictures (jpeg). I need to be able to print the
documentation and place it into an Intranet. I do not need to be able to
colabourate with anyone else.

But lets add another senario. Lets pretend I am writing some open source
software and I am wanting to document it before I place it onto freshmeat.
I am going to need stuff that people obviously expect. These would be a
man(1) page, a README file and some details on how the software works,
some examples etc. Lets call the last on the user docs or manual. Can any
of these tools help me create these variety of documents. Not sure where
this is leading, just throwing it out and seeing what comes back. 

Rodos

P.S. As a lover of HTML I sometime get a little irked when everything 
for a package is in the HTML files (I know lynx index.html is easy).
Sometimes I really want a .ps file I can print and read, but other times I
quite like a terse readme file. 

-- 
rodos@nospam.haywood.org | The best programming problems are those solved by
Camion Technology | someone else.  Only marginally better than those
+61 2 9873 5105   | caused by someone else.          [J.Wraxall 1998]

--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to slug-request@nospam.slug.org.au with
unsubscribe in the text