forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [issues] New comment: (FOR-187) Redefine project documentation dirs
Date Thu, 01 Jan 1970 00:00:00 GMT
The following comment has been added to this issue:

     Author: Dave Brondsema
    Created: Fri, 11 Jun 2004 4:33 PM
document2fo.xsl is currently very inflexible with regard to including images in the PDF. 
If we can use a cocoon pipeline here, that would be great.  If not, we might want to consider
a single directory for content, and differentiate the files using site.xml (this approach
was discussed earlier, but I don't remember the advantages/disadvantages right now).  This
would let the XSL find the images in most if not all cases.

Other (future) output formats may have similar problems inlining images.

fyi, here's how it works now.  Relative references to images will break if the image is in
the raw directory because the relative reference is only correct in the build/site/ dir not
in the src/ dir which we need.
      <xsl:variable name="imgpath">
        <!-- resources image dir -->
        <xsl:when test="starts-with(string(@src),'images/')">
          <xsl:value-of select="concat($imagesdir,substring-after(@src,'images'))"/>
        <!-- already absolute -->
        <xsl:when test="contains(string(@src),':') or starts-with(string(@src),'/')">
          <xsl:value-of select="@src"/>
        <!-- relative to document -->
        <xsl:otherwise><xsl:value-of select="concat($xmlbasedir,@src)"/></xsl:otherwise>

View the issue:

Here is an overview of the issue:
        Key: FOR-187
    Summary: Redefine project documentation dirs
       Type: Improvement

     Status: Assigned
   Priority: Major

    Project: Forrest
  Component: Core operations
    Fix For: 0.7

   Assignee: Steven Noels
   Reporter: Nicola Ken Barozzi

    Created: Thu, 10 Jun 2004 4:53 PM
    Updated: Thu, 10 Jun 2004 4:53 PM

We should finalize all discussions about where to put sources and extensions in the projects.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message