[Xcb] Padding in the XML protocol descriptions

[Barton C Massey]

Nice suggestion!

I don't think this is very hard to hack up the XCB code
generator to honor?  I'd be all for any patches anyone
wanted to do for this.

	Bart

In message <694519c50901021208q54b424d2vdf1175928ae5ef35 at mail.gmail.com> you wrote:
> > Should we have a deprecation mechanism for retaining
> > protocol descriptions like xevie and xprint but marking them
> > such that they aren't built by default and generate
> > appropriate warnings?  If so, how should this look exactly?
> 
> We could have more optional attributes in the "xcb" element:
> 
> >>>>>
> diff --git a/src/xcb.xsd b/src/xcb.xsd
> index ba334d1..38984c4 100644
> --- a/src/xcb.xsd
> +++ b/src/xcb.xsd
> @@ -36,6 +36,8 @@ authorization from the authors.
>        <xsd:attribute name="extension-multiword" type="xsd:boolean"
> use="optional" default="false" />
>        <xsd:attribute name="major-version"   type="xsd:integer"
> use="optional" />
>        <xsd:attribute name="minor-version"   type="xsd:integer"
> use="optional" />
> +      <xsd:attribute name="deprecated" type="xsd:boolean"
> use="optional" default="false" />
> +      <xsd:attribute name="reference-only" type="xsd:boolean"
> use="optional" default="false" />
>      </xsd:complexType>
>    </xsd:element>
> <<<<<
> 
> This adds a "deprecated" attribute, which indicates that warnings
> should be generated, as well as a "reference-only" attribute which
> indicates that the XML is informational only, and nothing useful
> should happen because of it.
> 
> I've not a clue how to make the XSL processing make this work for XCB,
> but it could be immediately useful for my Haskell work.