[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Using Wiki for KDE (User/Devel) Documentation
From:       Derrick Wippler <derrick () logicalsi ! com>
Date:       2005-02-28 18:34:21
Message-ID: 200502281334.21899.derrick () logicalsi ! com
[Download RAW message or body]

<sarcasm>
 I didn't know you could embed images in a text file?
</sarcasm>

So let me get this straight, I'll write a big text file worth of 
documentation. With function definitions, Example code, Screen shots, Tables 
of example data and smash it all into a text file. And someone will in 
*their* spare time take my mess and format it into docbook?

So, I submit my text documentation several times. ( because I found some 
spelling errors, and I added some new features so I document them also ) 
meanwhile "middle man" begins formating by first doc, but now has too other 
updated copies, with which to merge with the first partly formated copy. 

Nice, but wouldn't it be nicer to eliminate the middle man, with a few extra 
key strokes format my own documentation with *simple* Wiki markup? 
Simplification is rarely ever a bad thing. 

That is all we are saying. ( It doesn't mean it has to happen, it's just a 
thought ), 

<exaggeration>
Text file submit date 2006 - Document enters CVS 2007.
</exaggeration>

*Derrick Wipes Lauri's bleeding eyes* "It's OK, sometimes change is good"

Cheers, Derrick

On Monday 28 February 2005 12:48 pm, Lauri Watts wrote:
> On Monday 28 February 2005 15.13, Derrick Wippler wrote:
> > I agree, Wiki syntax is not only much easier to write than Docbook, it's
> > sexier.
> >
> > ===
> >  This is '''important''' never stick the tines of a fork
> > in an electrical outlet.
> > ===
> >
> > Is much easier than docBook
>
> I think my head is going to explode.
>
> *YOU DO NOT HAVE TO WRITE DOCBOOK!*
>
> Send plain text to kde-doc-english@ mailing list.  We will mark it up for
> you.
>
> Do it in a wiki first, if that floats your boat, we don't care.  Whatever.
> Send us the link when you think it is publishable.
>
> It's going to be docbook when it gets into CVS, because that is what we
> have the processing toolchain, the technological investment, and the
> translation toolchain.  That doesn't mean *you* have to ever touch it to
> contribute, and using it as the primary excuse to not, is getting old.
>
> Regards,
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]