programlistingco doesn't add the callouts on programlisting
Questions about XML that are not covered by the other forums should go here.
-
- Posts: 41
- Joined: Fri Dec 15, 2006 8:09 pm
- Location: Madrid
- Contact:
programlistingco doesn't add the callouts on programlisting
Dear member,
I have copy and pasted on my document the sample for programlistingco from:
Docbook 5.0: Definitive Guide:
Using Docbook HTML v8.0 transformation scenario I get on generated output the itmeized list with the callouts number in front, but I don't get the reference on the specified lines on programlisting source code. I don't see any of such images.
Is it a bug or it is a configuration problem?
Thanks,
David
I have copy and pasted on my document the sample for programlistingco from:
Docbook 5.0: Definitive Guide:
Code: Select all
<programlistingco>
<areaspec>
<areaset xml:id="ex.plco.const">
<area coords="4" xml:id="ex.plco.c1"/>
<area coords="8" xml:id="ex.plco.c2"/>
</areaset>
<area coords="12" xml:id="ex.plco.ret"/>
<area coords="12" xml:id="ex.plco.dest"/>
</areaspec>
<programlisting>
sub do_nothing_useful {
my($a, $b, $c);
$a = new A;
$a->does_nothing_either();
$b = new B;
$c = "frog";
return ($a, $c);
}
</programlisting>
<calloutlist>
<callout arearefs="ex.plco.const">
<para>These are calls to the constructor <function>new</function> in the
object classes. </para>
</callout>
<callout arearefs="ex.plco.ret">
<para>This function returns a two-element list. </para>
</callout>
<callout arearefs="ex.plco.dest">
<para>The <emphasis>destructor</emphasis> (<function>DESTROY</function>) for
the object <literal>$b</literal> will be called automatically for this
object since there can be no other references to it outside this
function. </para>
</callout>
</calloutlist>
</programlistingco>
Is it a bug or it is a configuration problem?
Thanks,
David
-
- Posts: 4141
- Joined: Fri Mar 28, 2003 2:12 pm
Post by sorin_ristache »
Hello,
You did not set correctly all the Docbook stylesheet parameters for adding image references in the programlisting source code. You have to set use.extensions to 1, callouts.extension to 1 and callout.graphics.path to [oXygen-install-folder]/frameworks/docbook/xsl/images/callouts/. Also you have to add [oXygen-install-folder]/frameworks/docbooc/xsl/extensions/saxon653.jar as XSLT extension in the transformation scenario using the Extensions button of the scenario edit dialog. If the XSLT processor set in the scenario is Xalan instead of Saxon you must set xalan25.jar located in the same folder as XSLT extension in the scenario.
Regards,
Sorin
You did not set correctly all the Docbook stylesheet parameters for adding image references in the programlisting source code. You have to set use.extensions to 1, callouts.extension to 1 and callout.graphics.path to [oXygen-install-folder]/frameworks/docbook/xsl/images/callouts/. Also you have to add [oXygen-install-folder]/frameworks/docbooc/xsl/extensions/saxon653.jar as XSLT extension in the transformation scenario using the Extensions button of the scenario edit dialog. If the XSLT processor set in the scenario is Xalan instead of Saxon you must set xalan25.jar located in the same folder as XSLT extension in the scenario.
Regards,
Sorin
Return to “General XML Questions”
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service