forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dick Hollenbeck (JIRA)" <>
Subject [jira] Commented: (FOR-363) <figure>-elements within aggregated pdf-pages are not displayed
Date Thu, 16 Jun 2005 17:39:47 GMT
    [ ] 

Dick Hollenbeck commented on FOR-363:

I applied the Jun/05 5:03 PM patch to current 0.7 (snap shotted via svn update as of yesterday),
and it does not seem to fix this issue.

I still do not see a PNG image in the wholesite.pdf file, yet is is displayed in the HTML
output.   I suggest you enable wholesite.pdf in the forrest seed example, and try it yourself.

> <figure>-elements within aggregated pdf-pages are not displayed
> ---------------------------------------------------------------
>          Key: FOR-363
>          URL:
>      Project: Forrest
>         Type: Bug
>   Components: Plugin: pdf-output
>     Versions: 0.6
>  Environment: Linux
>     Reporter: Stephan E. Schlierf
>     Priority: Minor
>  Attachments: for-363.patch
> With Forrest 0.6 I encountered a problem during the creation of a pdf-file that is aggregated
from a group of documents:
> All my graphics are in project-dir]/src/documentation/resources/images (and its subdiretories).
Now if I use <figure>-elements in these documents the graphics are not displayed in
the aggregated pdf-file. If I use <img>-elements everything's ok.
> As far as I can see this problem is located in
> src/core/context/resources/stylesheets/aggregates/doc2doc-uniqueids.xsl:
> Around line 45 the follwoing template is defined:
> <xsl:template match="section/document//figure|img[starts-with(@src, 
> 'my-images')]">
>     <!-- fix my-images/** links, which break as they are not relative to the 
> site root -->
> ...
> </xsl:template>
> If you change the match condition to
> match="section/document//figure[starts-with(@src, 'my-images')]|
> img[starts-with(@src, 'my-images')]">
> even the <figure>-elements are displayed.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message