Re: Starting work on gedit - Some pointer req.

I personally don't think that we need a howto on docbook ( 1 simple
google gives more hits than you'l ever need, add to that the fact that
we get plenty of examples from looking at xml's from our cvs tree and we
REALLY have enough to get started on ).

What we should have though are examples of how one might get started
documenting, and creating patches.

i.e. have a howto running through a regular patching of an xml file,
leaving the details of docbook syntax out.

I think a real life example of, for example, adding a revision header
will be really useful.  Things like that.

~Alessandro Ferrucci

On Fri, 2006-01-13 at 10:21 +0000, Joachim Noreiko wrote:
> --- Manish Chakravarty <manishchakravarty yahoo co in>
> wrote:
> > I am going to start work on the gedit docs from
> > today. If somebody else
> > is already working on it, then please tell me so
> > that i can work on
> > something else.
> Add yourself to the team page so we can keep track of
> who is working on what:
> > Do i HAVE to submit its manual as DocBook, or can i
> > submit it as text (i
> > am comfortable with HTML).
> Have a go with DocBook. If you're ok with HTML, then
> DocBook should be fairly easy to pick up.
> I've been wondering whether to create a page on the
> wiki on DocBook essentials -- just enough to get by to
> write docs. Does anyone think that would be useful?
> > Also, once i have completed it, how do i submit it?
> > Since i dont have
> > CVS access, what is then normal procedure for
> > submitting it?
> See
> ___________________________________________________________ 
> Win a BlackBerry device from O2 with Yahoo!. Enter now.
> _______________________________________________
> gnome-doc-list mailing list
> gnome-doc-list gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]