RE: [docbook-apps] Support for callout extensions in xsltproc

["Kenneth Johansson" <ke-joh at sectra dot se>]

Sorry, but I'm no programmer and probably wouldn't be able to make the customization required.

If the XSL stylesheets or tools doesn't support callout bugs in images the mediaobjectco is useless at this point, or am I wrong?

/Kenneth

> -----Original Message-----
> From: Jeff Beal [mailto:jeff.beal@ansys.com]
> Sent: Thursday, August 07, 2003 17:10
> To: 'Kenneth Johansson'
> Cc: DOCBOOK-APPS
> Subject: RE: [docbook-apps] Support for callout extensions in xsltproc
> 
> 
> There isn't any support for image callouts.  You'd probably have to use
> inline CSS in your document to handle this one.  The XSLT customization
> would probably be a little hairy, just because all of the mediaobject code
> is a little hairy.  I think what you would need, though, would be to put a
> style="position:relative" on an HTML <DIV> that contains the <IMG> and all
> of the callouts.  Your areas would probably have to output something like
> 
> <SPAN style="position: absolute; left: 12px; top:
> 147px">callout_graphic</SPAN>
> 
> You may also have to play with the z-index property to be sure 
> the callouts
> are rendered on top of the graphic.
> 
> Jeff
> > -----Original Message-----
> > From: Kenneth Johansson [mailto:ke-joh@sectra.se]
> > Sent: Thursday, August 07, 2003 11:06 AM
> > To: Kenneth Johansson; Jeff Beal; Bob Stayton
> > Cc: DOCBOOK-APPS
> > Subject: RE: [docbook-apps] Support for callout extensions in xsltproc
> > 
> > 
> > I managed to fix my problems with programlistingco. I'd made 
> > a bad customization.
> > 
> > Oh, forgot to say that Saxon didn't solve my problem of 
> > getting callout bugs in my image either. Here's what I tried:
> > 
> > <mediaobjectco>
> >   <imageobjectco>
> >     <areaspec id="options" units="calspair">
> >       <area coords="12 147" id="options1" />
> > 
> >       <area coords="197 140" id="options2" />
> > 
> >       <area coords="456 88" id="options3" />
> > 
> >       <area coords="260 290" id="options4" />
> > 
> >       <area coords="260 320" id="options5" />
> > 
> >       <area coords="12 392" id="options6" />
> >     </areaspec>
> > 
> >     <imageobject>
> >       <imagedata fileref="images/options_dialog.gif" format="GIF"
> >       scale="100" scalefit="" />
> >     </imageobject>
> > 
> >     <calloutlist>
> >       <callout arearefs="options1">
> >         <para>This list shows the current configuration and commands
> >         that are assigned to a shortcut.</para>
> >       </callout>
> > 
> >       <callout arearefs="options2">
> >         <para>Shows the current shortcut assigned to the 
> > command.</para>
> >       </callout>
> > 
> >       <callout arearefs="options3">
> >         <para>This list shows the the commands that are available but
> >         not used. </para>
> >       </callout>
> > 
> >       <callout arearefs="options4">
> >         <para>Define a shortcut for a command by typing in 
> > the shortcut
> >         combination in the edit box.</para>
> >       </callout>
> > 
> >       <callout arearefs="options5">
> >         <para>The entered shortcut is checked to see if it is already
> >         assigned to a command.</para>
> >       </callout>
> > 
> >       <callout arearefs="options6">
> >         <para>The path to the currently selected menu or window is
> >         displayed in the path box.</para>
> >       </callout>
> >     </calloutlist>
> >   </imageobjectco>
> > </mediaobjectco>
> > 
> > Have I missed anything? The image is 615x501 pixels.
> > 
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: Kenneth Johansson [mailto:ke-joh@sectra.se]
> > > Sent: Thursday, August 07, 2003 13:29
> > > To: Jeff Beal; Bob Stayton
> > > Cc: DOCBOOK-APPS
> > > Subject: RE: [docbook-apps] Support for callout extensions 
> > in xsltproc
> > > 
> > > 
> > > Hi,
> > > 
> > > I've moved to Saxon but I get some strange errors:
> > > 
> > > When using programlistingco (haven't tried any other elements 
> > > using callouts) the callouts are not put on the correct line, but 
> > > one below. It seems like the segments between the callouts are 
> > > their own tables which must be wrong?!
> > > 
> > > I also get errors like: "Chapter 1. Writing Documentation" 
> > > (should be Chapter 1. Writing Documentation).
> > > 
> > > My command line: 
> > > ke-joh:13> java com.icl.saxon.StyleSheet -o writing.html 
> > > writing-documentation.xml 
> > > ../../lib/docbook-xsl/custom_stylesheets/stylesheets/xhtml/customx
> > > html.xsl use.extensions=1
> > > 
> > > My param customizations:
> > > <xsl:param name="use.extensions" select="'1'"/>
> > > 
> > > <!-- Default file extension for HTML output -->
> > > <xsl:param name="html.ext" select="'.html'"/>
> > > 
> > > <!-- Base directory for HTML output -->
> > > <xsl:param name="base.dir" select="'html/'"/>
> > > 
> > > <!-- Should first section be chunked too? -->
> > > <xsl:param name="chunk.first.sections"/>
> > > 
> > > <!-- Include admonition graphics? -->
> > > <xsl:param name="admon.graphics" select="'1'"/>
> > > 
> > > <!-- Default admonitions graphics path -->
> > > <xsl:param name="admon.graphics.path" select="'../../images/'"/>
> > > 
> > > <!-- Admonition graphics extension format -->
> > > <xsl:param name="admon.graphics.extension" select="'.png'"/>
> > > 
> > > <!-- Callout graphics path -->
> > > <xsl:param name="callout.graphics.path" 
> > > select="'../../images/callouts/'"/>
> > > 
> > > <xsl:param name="callout.graphics" select="'1'"></xsl:param>
> > > 
> > > <xsl:param name="callouts.extension" select="'1'"></xsl:param>
> > > 
> > > <xsl:param name="callout.graphics.extension" 
> > select="'.png'"></xsl:param>
> > > 
> > > <xsl:param name="saxon.extensions" select="'1'"/>
> > > 
> > > Thanks,
> > > 
> > > /Kenneth
> > > 
> > > 
> > > 
> > > > -----Original Message-----
> > > > From: Jeff Beal [mailto:jeff.beal@ansys.com]
> > > > Sent: Wednesday, August 06, 2003 14:51
> > > > To: 'Kenneth Johansson'; Bob Stayton
> > > > Cc: DOCBOOK-APPS
> > > > Subject: RE: [docbook-apps] Support for callout 
> > extensions in xsltproc
> > > > 
> > > > 
> > > > It shouldn't be very difficult at all.  As for which is 
> > > preferable, Saxon
> > > > seems to have been more stable for longer, and its performance is 
> > > > comparable
> > > > to xsltproc's (for chunked HTML output) on my Windows 
> > 2000 machine.
> > > > 
> > > > Both programs are written in Java, so your first step is to 
> > > > install a recent
> > > > version of a Java Runtime Environment.  (I recommend version 1.4 
> > > > or greater
> > > > because some of the XML parsing is built into the JRE after 1.4.) 
> > > >  You may,
> > > > of course, already have one somewhere, so you would just need 
> > > to make sure
> > > > it's in your path.  (If you need any help with that, I 
> > can help you
> > > > off-line.  I've had to find and install JRE's on just about 
> > > every platform
> > > > except for Macintosh.)
> > > > 
> > > > Once your JRE is installed, go to saxon.sourceforge.net 
> > and download the
> > > > "recommended" version of Full saxon.  (Instant Saxon only works 
> > > > on Windows,
> > > > and doesn't perform as well or have as much functionality because 
> > > > it relies
> > > > on the Microsoft JVM.)  Once you've installed that, you'll want 
> > > to include
> > > > the paths to saxon.jar and saxon651.jar (from the DocBook XSL 
> > > > distribution)
> > > > in your CLASSPATH environment variable (e.g.
> > > > /some_path/saxon/saxon.jar:/some_path/docbook-xsl/extensions/saxon
> > > > 651.jar --
> > > > use a semi-colon instead of a colon on Windows platforms.)
> > > > 
> > > > To run Saxon, you just need to invoke the Java interpreter and 
> > > pass it the
> > > > name of the Saxon class (com.icl.saxon.StyleSheet) as an 
> > > > argument, followed
> > > > by Saxon's arguments as documented with the Saxon 
> > distribution: "java
> > > > com.icl.saxon.StyleSheet {args}"
> > > > 
> > > > Jeff
> > > > 
> > > > > -----Original Message-----
> > > > > From: Kenneth Johansson [mailto:ke-joh@sectra.se]
> > > > > Sent: Wednesday, August 06, 2003 3:28 AM
> > > > > To: Bob Stayton
> > > > > Cc: DOCBOOK-APPS
> > > > > Subject: RE: [docbook-apps] Support for callout 
> > extensions in xsltproc
> > > > > 
> > > > > 
> > > > > Hi,
> > > > > 
> > > > > That is unfortunate for me. Would it be difficult to change 
> > > > > my set up to Xalan or Saxon? Which is preferrable? I 
> > also use FOP. 
> > > > > 
> > > > > best regards,
> > > > > 
> > > > > /Kenneth
> > > > > 
> > > > > > -----Original Message-----
> > > > > > From: Bob Stayton [mailto:bobs@sco.com]
> > > > > > Sent: Tuesday, August 05, 2003 18:27
> > > > > > To: Kenneth Johansson
> > > > > > Cc: DOCBOOK-APPS
> > > > > > Subject: Re: [docbook-apps] Support for callout extensions 
> > > > > in xsltproc
> > > > > > 
> > > > > > 
> > > > > > On Tue, Aug 05, 2003 at 05:55:15PM +0200, Kenneth 
> > Johansson wrote:
> > > > > > > Hi,
> > > > > > > 
> > > > > > > I've run in to the problem where callouts are not showing
> > > > > > > up in the programlisting in a programlistingco. Browsing
> > > > > > > the mail archive I see that there is no support for callout
> > > > > > > extensions in libxslt. Is this still the case? Will there
> > > > > > > be any support included within a near future? I've just
> > > > > > > learned to use xsltproc and don't want to switch to a
> > > > > > > new processor.
> > > > > > 
> > > > > > I haven't seen any evidence of progress on implementing
> > > > > > Norm's extension functions for xsltproc.  I doubt you will
> > > > > > see it in the near future.  If you require such an extension,
> > > > > > you will need to use Saxon or Xalan.  
> > > > > > 
> > > > > > -- 
> > > > > > 
> > > > > > 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
> > > > > > 
> > > > > 
> > > > > 
> > > > > 
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: 
> > docbook-apps-unsubscribe@lists.oasis-open.org
> > > > > For additional commands, e-mail: 
> > > > > docbook-apps-help@lists.oasis-open.org
> > > > > 
> > > > > 
> > > > > 
> > > > 
> > > > 
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: 
> > docbook-apps-unsubscribe@lists.oasis-open.org
> > > > For additional commands, e-mail: 
> > docbook-apps-help@lists.oasis-open.org
> > > > 
> > > > 
> > > 
> > > 
> > > 
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: 
> > docbook-apps-unsubscribe@lists.oasis-open.org
> > > For additional commands, e-mail: 
> > docbook-apps-help@lists.oasis-open.org
> > > 
> > > 
> > 
> > 
> > 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org