<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0">
</HEAD>
<BODY>
On Sun, 2010-10-10 at 10:50 -0700, Dan Nicholson wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
<TT><FONT COLOR="#737373">> Should we be distributing the doc output in the tarball then?</FONT></TT><BR>
<TT><FONT COLOR="#737373">> Currently, we're not, but that would be a simple update to</FONT></TT><BR>
<TT><FONT COLOR="#737373">> spec/xmlrules.in in libX11.</FONT></TT><BR>
<BR>
<TT><FONT COLOR="#1a1a1a">Oh, I thought they were, but I didn't actually check. IMO, I'd either</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">leave the compose key charts out or distribute just the html versions.</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">Either way, I'd default fop to off. People that really want the pdf or</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">ps versions of the docs can build them on their own.</FONT></TT><BR>
<BR>
<BR>
</BLOCKQUOTE>
I am just catching up with all the posts. Are we talking about solving a libX11<BR>
problem only, or are we talking about *all* of DocBook XML documentation?<BR>
<BR>
I can understand turning off doc build in some cases due to build time. This can be done with<BR>
XORG_ENABLE_DOCS(no) or XORG_ENABLE_SPECS(no).<BR>
<BR>
The conversion to DocBook/XML implies that the xmlto tooling was adequate and available on<BR>
a reasonable number platforms. Including generated docs (of any kind) in the tarball is a nightmare<BR>
which still has unresolved problems.<BR>
<BR>
<BR>
<BR>
<BR>
</BODY>
</HTML>