[sylpheed:33103] Re: Sylpheed documentation (was: Sylpheed 2.7.0 released)

Petr Kovar pknbe at volny.cz
Sun Jul 26 04:40:56 JST 2009


Ricardo Mones <mones at debian.org>, Sat, 25 Jul 2009 20:35:05 +0200:

> El Sat, 25 Jul 2009 19:57:56 +0200
> Petr Kovar <pknbe at volny.cz> escribió:
> /.../ 
> > > If the answer is something else then we figure it out. Just keep it
> > > simple. The simpler it is the more likely it will get done and be
> > > maintained.  I say start easy/simple.  
> > 
> > That's definitely true, and we should try to search for tools and
> > work flow processes that would suit needs of that not-so-big Sylpheed
> > documentation best. Perhaps have the not-so-skilled contributors work
> > with plain text or simple HTML, and then have the maintainer convert
> > it to valid DocBook? Not sure.
>   DocBook is already nearly plain text, don't need to be a guru to
> write content for it. Have a look at Claws Mail documentation, it's
> already using it and may even serve as starting point (maybe not the
> content, of course).

Yes, it seems to be a good idea to look at what Claws Mail uses and think
about whether and how could we adapt Sylpheed docs. However, I'm definitely
not a docs build expert, so I'd really appreciate if somebody could give me
a hand here.

> > That being said, I'm playing with some fancy XML editors more or less
> > suitable for DocBook, like XXE, epcEdit or Vex, and hopefully find
> > something that is usable enough.
>   Sure, but luckily you only need vim to edit it ;-)

Or Emacs, eh? Yes, I know it. :-)

Petr Kovar

More information about the Sylpheed mailing list