libXcomposite DocBook/man page draft for review

[Alan Coopersmith]

The only feedback I got was positive, so I went ahead and committed
earlier this week, as you may have seen.

Since then I got one bit on IRC:
  PauloZanoni: I was trying to compile libXcomposite, and it was giving me
               an error (no rule to process Xcomposite). it took me a while
               to find out that I didn't have the "xmlto" command. I saw that
               ./configure identified that I didn't have the package, but it
               didn't give me any error or warning message. maybe adding a
               message or an error when xmlto is not found would be good?

This should only affect those building from git, since the tarballs will
include the prebuilt man page, but for those people, I'll add in a warning
in configure.ac.

If I hear no other complaints of this breaking for anyone, I'll try to get
a release rolled out next week.

	-Alan Coopersmith-           alan.coopersmith at sun.com
	 Sun Microsystems, Inc. - X Window System Engineering


Alan Coopersmith wrote:
> I've taken the Composite Extension spec and the Xcomposite header,
> put them in a blender set to puree and then tried to figure out
> how to pour it into a DocBook/xml man page mold.
> 
> I've attached both the xml doc and a plain text version generated
> via "xmlto man ; nroff -man | col -b" - please review for both
> technical accuracy and my use or abuse of DocBook/xml refentry
> formatting.
> 
> For actual delivery, I'm thinking for now of making the "xmlto man"
> step a dist-hook so that only those releasing tarballs or working
> off git sources need to have a working xmlto install - does that
> sound reasonable to everyone?