Re: [docbook-apps] callouts don't work in various settings

[Bob Stayton <bobs@sco.com>]

On Wed, Nov 26, 2003 at 11:34:08AM +0100, Krueger, Carsten wrote:
> > This seems to be a bug in the callout extension when shade.verbatim
> > is turned on.  It definitely messes up the table that is used to provide
> the
> > background color for programlisting.  Norm Walsh needs
> > to look at this, so I will file a bug report on it.
> Thanks !
> 
> 
> >> When setting callout.graphics to 0 and callout.unicode to 1 a '#'
> character
> >> is shown where I would expect the callout to appear. I guess the FO
> output
> >> should be corrected from (_X_ represents a Unicode character):
> >>     ...
> >>     <ELEMENT configDef ( property+ )> _X_
> >>     ...
> >> to
> >>     &lt;ELEMENT configDef ( property+ )&gt; <fo:inline
> >> font-family="ZapfDingbats">_X_</fo:inline>
> 
> > Actually, callout.unicode works for me with version 1.62.4
> > of the stylesheets and FOP 0.20.5.  Did you try those versions?

> That's exactly what I tried too. As said before a '#' character is shown
> where I would expect the callout to appear (inside the programlisting).

Are you using Xalan to generate the FO?
The Saxon version of the callout extensions does output
<fo:inline font-family="ZapfDingbats">, but Xalan
just outputs the character.  Try using Saxon, if you
can.

-- 

Bob Stayton                                 400 Encinal Street
Publications Architect                      Santa Cruz, CA  95060
Technical Publications                      voice: (831) 427-7796
The SCO Group                               fax:   (831) 429-1887
                                            email: bobs@sco.com