libX11 docs compilation failure

[Matt Dew]

On Fri, Oct 8, 2010 at 5:31 PM, Jeremy Huddleston <jeremyhu at apple.com> wrote:
>
> On Oct 8, 2010, at 16:22, James Cloos wrote:
>
>> Now that the docs are in the modules they document, building from git
>> has become fragile.

That's exactly opposite of the goal.  :)   With fewer tools required,
it should be less fragile.  Granted we're still in the process of
converting and updating all this so it's very possible that there are
problems.

>>
>> Today, libX11 failed to build because something called when building the
>> docs wanted a usable display.  For no good reason.
>
> My guess is that this was fop:
>
> http://trac.macports.org/ticket/26686
> https://issues.apache.org/bugzilla/show_bug.cgi?id=50062
>

>> Part of the problem is the use of xml for the docs, and the lack of any
>> reasonable stack to typeset xml.  Jade would produce reasonable output
>> were it usable.  Fop is also unreliable and produces /horrid/ ouput.

I disagree on this.
While none of the XMl docs in the tree look good at the moment, that's
because there is no formatting done to them.  I'm hoping your not
basing your opinion on those.  If you feel xml was the wrong choice,
I'm curious what you feel is the right choice?

I've seen fop generated stuff on the web that looks pretty good. It
just takes the right xsl and css stylesheets, which I'm just now
starting to figure out how to do.

Are you volunteering to work on the XSL and CSS stylesheets to get the
documentation looking good?


>>
>> Plus, make install re-gens all of the docs.  The dependencies are wrong.

While there's been a massive amount of work already done on the docs,
there is still a massive amount to do.   I'd be shocked if people
didn't find problems at this point.  Patches are welcome.

> http://lists.x.org/archives/xorg-devel/2010-October/013801.html
>
>> It should be possible to build everything w/o a display.
>
> Yes.
We agree on this.

Matt