[FOP-2523] Behavior change in include path handling breaks existing 1.1 docs

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Invalid
• Affects Version/s: 2.0
• Component/s: image/jpeg, image/png
• Labels: path
• Environment: OS X , Linux
• Assignee: Unassigned
• Reporter: Johan Persson
• Created: 10/Sep/15 10:07
• Updated: 12/Feb/17 19:36
• Resolved: 12/Feb/17 19:36

Description

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.