On Thu, May 13, 2010 at 15:00, Richard Quadling <rquadl...@googlemail.com> wrote: > So, I would like to use a role on the methodsynopsis to indicate OOP > or PROC use. This will allow me to include only the OOP methodsynopsis > via the xinclude in the event of method overloading. > > Changing > > <xi:include xpointer="xmlns(db=http://docbook.org/ns/docbook) > xpointer(id('class.xyz')/db:refentry/db:refsec...@role='description']/descendant::db:methodsynopsis[1])" > /> > > to > > <xi:include xpointer="xmlns(db=http://docbook.org/ns/docbook) > xpointer(id('class.xyz')/db:refentry/db:refsec...@role='description']/descendant::db:constructorsynopsis)" > /> > <xi:include xpointer="xmlns(db=http://docbook.org/ns/docbook) > xpointer(id('class.xyz')/db:refentry/db:refsec...@role='description']/descendant::db:destructorsynopsis)" > /> > <xi:include xpointer="xmlns(db=http://docbook.org/ns/docbook) > xpointer(id('class.xyz')/db:refentry/db:refsec...@role='description']/descendant::db:methodsynops...@role='oop'])" > /> >
I like it. It has always bothered me that functions use <methodsynopsis>. In the beginning it was <funcsynopsis>, but I can't find any discussion on why it was changed. The <funcdef> model does fit well for us.. But like you said, that would be a major change. -Hannes
