[erlang-questions] FOP (was: Re: Trace-Driven Development)

Michael Turner michael.eugene.turner@REDACTED
Tue Jun 5 17:30:38 CEST 2012

Right you are, Tuncer. IIRC, I had to do some surgery on the build
scripts to circumvent FOP, since I was trying to build in a server
environment. I don't remember any obvious command-line option for
getting around it. Maybe things are better now. At the time, it seemed
a needless complication for those of us who have been (and perhaps
still could be) motivated to improve the documentation.

But really: just give me a wiki. Give everybody a wiki. Write scripts
to update the repo from the wiki diffs, if that's so important.
Generally, lower the bar for entry, for those who want to improve the
documentation, and the documentation *will* improve. (Yes, there's
such a thing as too low; I've policed wikis for spam, it can get
tedious. But there are well-known, easily implemented policies that
prevent 99.9% of that kind of thing.)

-michael turner

On Tue, Jun 5, 2012 at 11:09 PM, Tuncer Ayaz <tuncer.ayaz@REDACTED> wrote:
> On Tue, Jun 5, 2012 at 9:52 AM, Ulf Wiger wrote:
>> Having patched the docs myself, my own experience is that the
>> biggest frustration is dealing with FOP - it runs out of heap and
>> throws exceptions everytime I try to build the whole docs. That, and
> http://erlang.org/pipermail/erlang-questions/2010-September/053298.html
> xsltproc (from libxslt) - which you probably have installed - is
> enough to create man pages and HTML docs. Also, FOP - the last time I
> used it - made use of Apache Batik and therefore required X11. This
> makes it harder to run in a headless (server) environment. FOP is
> only required for generating PDF files.

More information about the erlang-questions mailing list