[kde-doc-english] Re: Helping with Documentation

[Raphael Langerhorst]

Hi Marc,

sounds great! I also like to give KSpread a hand, both in documentation and 
source code. Currently I'm updating the command reference. I should be done 
by tonight with that and will send a patch to the doc-english ML.

Just for you to know that no duplicate work is done. Also I have corrected a 
couple of spelling mistakes all over the KSpread manual, that is allready in 
CVS. If you like to help here it would be great if you have a CVS HEAD 
version around. ... but, you're on the koffice lists anyway :) so I guess 
you're familiar with that.

Besides, I'm also trying to get a feeling about the source code, KSpread 
specific - that will be the first part I'll include in the KOffice 
Development Guide (the last update on koffice-devel included a plain text 
version, UTF8, UNIX line break, you can open that with MS Word). When you 
feel like you can correct or improve one or the other part, that would help. 
And when you're actually about to write an extensive guide about KSpread (for 
users) I'll help you - I'm also interested in that.

Sorry for others if they feel like I'm referencing to a few things not covered 
on this list: it's all just about improving documentation for KSpread.

Regards,
Raphael

PS: copy goes to kde-doc-english, since Marc posted the same message there.

On Friday 05 March 2004 13:27, Marc Heyvaert wrote:
> Hi Philip and all,
>
> As this is my first msg on this list, a brief
> introduction.
>
> I'm 46, living in Belgium and I have been a user of
> spreadsheets since 1984, mostly for stuff that was
> investment related. I'm really fascinated by the
> progress that KDE has made in the past few years, I
> tried it 2 years ago, and since I bought a second
> computer I use KDE for most of the work that I do on a
> PC (at home that is, here at work it is all Windows).
>
> I really want to do something for KSpread. I am
> currently doing some janitor work (correcting
> copyright messages) and I have had one patch accepted
> by Ariya, but I'm too much of a newbie in C++ and Qt
> to do a lot of coding yet, but it remains my ambition
> to become one :)
>
> Now I'v read the wishes you posted on the KDE bug
> tracking system, and I would like to help with
> 1. KSpread documentation.
> 2. Screenshots (I feel there should be a lot more).
> 3. New and better templates.
>
> I also would like to make a 'real' manual for KSpread.
> Don't look for results soon, because what I have in
> mind will be quite long. But I will come back on this,
> because as English is not my mother tongue I will need
> an editor for my manual, somewhere down the line.
>
> Also I want to become involved in testing patches,
> etc. Discovering new bugs, categorizing existing bugs
> and wishes, etc.
>
> I have already told Ariya about my intentions. I will
> also post a message on the kde-doc-english at kde.org
> mailing list.
>
> Regards
>
> Marc
>
>
> --- Philip Rodrigues
>
> <philip.rodrigues at christ-church.oxford.ac.uk> wrote:
> > For
> > KOffice, you can work
> > from the 1.3 release, since the documentation is
> > quite out-of-date. There are
> > probably other things, too. If you would like to
> > help, but running CVS HEAD
> > is a problem, email this list or
> > kde-doc-english at kde.org, and we'll try to
> > find something suitable.
> >
> > Regards,
> > Philip
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Search - Find what you’re looking for faster
> http://search.yahoo.com
> _______________________________________________
> kde-quality mailing list
> kde-quality at kde.org
> https://mail.kde.org/mailman/listinfo/kde-quality