Pidgin usability look on the web
caseyharkins at gmail.com
Thu Aug 21 11:59:33 EDT 2008
On Thu, 2008-08-21 at 16:15 +0200, Sascha Vogt wrote:
> It was also not decided where to keep the docs. If it should go to a
> monotone repository or somewhere in a DMS / CMS / Wiki system. I'm not
> yet familiar with docbook (only used LaTeX so far), but if no one else
> jumps up and starts with another format I think I'll take a look into
> docbook (to me, this seems to be most fitting).
Docbook seems ideal, as it is widely used for this purpose and
stylesheets exist for converting to gnome help, windows help, generic
html, pdf, etc. However, a wiki does have the advantage of lowering the
barrier for contributing.
Maybe we can do both with something like this:
I may install it on a trac instance here and play with it a bit to see
how well it works. I imagine we could automate the process of converting
the wiki page (periodically, or on each edit) and committing it to a
documentation branch in monotone. This branch could then be merged to
i.p.p manually before releases.
We'd need to update our autotools magic to optionally build the various
output formats. Packagers could then create an additional help package
for various backends. Our win32 build would generate the windows help
I do remember the previous thread, but don't think there was any
More information about the Devel