[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-apps] annotating programlistings
Simon Kennedy wrote: > With regards to callouts... > This is what I have in one of my documents > > -------------------------------------------------------------------------- > > <programlistingco> > <programlisting> > #include Application.h > > main()<co id="simplemain.main"/> > { > <co id="simplemain.new"/>new > BApplication("application/x-vnd.your-app-sig")<co > id="simplemain.sig"/>; > /* Further initialization goes here -- read settings, set globals, > etc. */ > be_app-Run()<co id="simplemain.run"/>; > /* Clean up -- write settings, etc. */ > delete be_app; > } > </programlisting> > > <calloutlist> > <callout arearefs="simplemain.main"> > Callout text here... > </callout> > > <callout arearefs="simplemain.new"> > Callout text here... > </callout> > > <callout arearefs="simplemain.sig"> > Callout text here... > </callout> > > <callout arearefs="simplemain.run"> > Callout text here... > </callout> > </calloutlist> > </programlistingco> > > -------------------------------------------------------------------------- > > and it generates correct output with xsltproc with the following parameters > > <!-- Enable callout graphics and set extension to png --> > <xsl:param name="callout.graphics">1</xsl:param> > <xsl:param name="callout.graphics.path">./images/callouts/</xsl:param> > <xsl:param name="callout.graphics.extension">.png</xsl:param> Interesting ! The above seems to work well if I embedd the <co.../> elements into my program text. However, if I xinclude the program text and provide an <areaspec/> to generate the map it doesn't. That might be the part that's provided via those extensions that aren't provided by xsltproc. Thanks for the help ! Stefan
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]