You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by "Johan Persson (JIRA)" <ji...@apache.org> on 2015/09/10 12:07:45 UTC
[jira] [Created] (FOP-2523) Behavior change in include path
handling breaks existing 1.1 docs
Johan Persson created FOP-2523:
----------------------------------
Summary: Behavior change in include path handling breaks existing 1.1 docs
Key: FOP-2523
URL: https://issues.apache.org/jira/browse/FOP-2523
Project: FOP
Issue Type: Bug
Components: image/jpeg, image/png
Affects Versions: 2.0
Environment: OS X , Linux
Reporter: Johan Persson
Priority: Minor
When transforming a document with included files (images) there is a different behavior between 1.1 and 2.x.
Transformation that works with fop 1.1 no longer works with 2.0
I suspect that this is not so much a bug as a change that breaks existing build schemas due to fop making different assumption on relative paths in 1.1 compared with 2.x. but I have to yet figure out what the assumption is.
If the generated .fo includes say,
{{<fo:external-graphics src="url(myimage.jpg) width="100%" height="auto">}}
If all files (both images and .fo) are in a flat directory this works well with 1.1. Running the same source through 2.0 will generate an error saying that FOP cannot find the referred file (myimage.jpg)
I suspect this is a common enough pattern to warrant some notice on how to handle this situation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)