RE: linux-kernel-documentation, proposal

[Stephen Torri]

Agreed. Unless we are agree on a set tool and procedure we will be mix
matching various filetypes (lyx, tetex, etc.). This would not be
productive. The point of this I believe should not be what text editor is
better because of preference but what is easy to use for all involved.

Stephen

On Thu, 29 Jun 2000, Garst R. Reese wrote:

>  	
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> 
> "Copeland, Matthew" <[e-mail]>
> 
> Summarizing...
> 
> [snip]
> >Possible Tasks:
> 
>         1.      Beef up documentation in linux/Documentation making 
>         it more clear and verbose. (Plain text) (using possibly
>         using Garst's du &> kerneldu as an outline)
>         2.      Create an Linux Device Driver manual that can be 
>         easily updateable.  (SGML/Docbook)
> 
> >Did I miss anything and is anything incorrect?
> 
> I would just like to restate that I think it extremely important that we
> choose an outline and format. My personal preference would be to use
> LyX, but this could be because I find the documentation of DocBook and
> sgml-lite so inscrutable :) 
>  Most of the details can be sorted out when we have a list, but we will
> have a basic dependancy on the code writers to supply the basics, and
> our success will depend on them percieving it as a valuable service,
> rather than just something else eating away their time.
>  Garst
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [e-mail]
> Please read the FAQ at http://www.tux.org/lkml/
>