I am not a big fan of the areaspec element, either, but the version of the transforms we are currently using (not particularly recent) does not depend on the areaspec. We use co elements embedded in the programlisting itself, and just dummy up the areaspec. I would, of course, prefer that we not have to dummy up an areaspec, but, as the great philosopher once said "You don't always get what you want ..."
I should have been more complete in my response. Larry Rowland -----Original Message----- From: Bob Stayton [mailto:[email protected]] Sent: Wednesday, January 28, 2009 2:53 PM To: Rowland, Larry; Remko Tronçon; [email protected] Subject: Re: [docbook] Callout lists in figures Yes, that works too, but because it requires an areaspec element to specify the callout bug placement, I generally only use programlistingco when the programlisting is an imported text file. I've never enjoyed using areaspecs. 8^) Bob Stayton Sagehill Enterprises [email protected] ----- Original Message ----- From: "Rowland, Larry" <[email protected]> To: "Remko Tronçon" <[email protected]>; <[email protected]> Sent: Wednesday, January 28, 2009 1:40 PM Subject: RE: [docbook] Callout lists in figures If you use a programlistingco, you can include a calloutlist inside it. It is a wrapper for the programlisting element. See: http://www.docbook.org/tdg/en/html/programlistingco.html Regards, Larry Rowland -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Remko Tronçon Sent: Wednesday, January 28, 2009 2:31 PM To: [email protected] Subject: [docbook] Callout lists in figures Hi, I have a <figure> with a <programlisting> in it, which contains callout bugs. I would have liked to add the corresponding calloutlist to the <figure> as well, but as far as I can tell, this isn't possible with docbook 4 (although I'm under the impression it is with DocBook 5). Is there a way of doing this (or achieving the same result)? thanks, Remko --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
