Re: [ jEdit-devel ] Using html vs. docbook for jEdit & plugin documentation

[Shlomy R. <sre...@gm...>]

To add to that - if the reason is the automatic PDF creation from
docbook - then there are open source tools for converting html to PDF,
which are (1) much simpler to install than docbook, and (2) only
needed for the actual release. Developers can work only with the html
files and at least see that they look okay.

Shlomy

On Sat, Jun 19, 2010 at 6:58 AM, Shlomy Reinstein <sre...@gm...> wrote:
> Hi,
>
> The documentation of jEdit and some plugins is in docbook format.
> Setting up a docbook environment on Windows is non-trivial. After
> having spent many hours on this, with advice from Eric and Alan, I
> still don't have a working docbook environment, and still unable to
> build the jEdit documentation.
> Due to this, I sometimes update the documentation without actually
> seeing the result.
>
> Is there a good reason for using docbook? If not, let's switch to
> plain html, so that every developer can easily update the
> documentation without requiring special tools. I can prepare some
> macros to insert docbook structures like 'author', e.g. using
> SuperAbbrevs, to make it easier to write.
>
> Thanks,
> Shlomy
>