Bug 706481

Summary: FOP: Problem with Image Width?
Product: [openSUSE] openSUSE 11.4 Reporter: Tanja Roth <taroth>
Component: DocumentationAssignee: Thomas Schraitle <thomas.schraitle>
Status: VERIFIED INVALID QA Contact: Karl Eichwalder <ke>
Severity: Normal    
Priority: P5 - None    
Version: Factory   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Documentation Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on:    
Bug Blocks: 702276    

Description Tanja Roth 2011-07-18 15:07:16 UTC 
XEP and FOP seem to handle the image width attributes slightly different:

For example, Figure 1.5 is not shown completely when building a PDF with FOP, with XEP, it is complete.

See https://bugzilla.novell.com/attachment.cgi?id=438018, p. 13.

(I'm not sure if this is in fact an FOP issue. It might also be an effect of the new image handling processes introduced by the the DocBook Publishing and Authoring Suite (daps), the successor of susedoc).
Comment 1 Thomas Schraitle 2012-04-13 14:25:48 UTC 
I've built the openSUSE Startup and compared the PDF. Well, I cannot see any difference in regard to image width between XEP and FOP. However, the linebreaks and pagebreaks are different (but that was to be expected).

Maybe we can look into this issue next week? :)
Comment 2 Tanja Roth 2012-04-19 13:02:45 UTC 
Sorry, cited wrong attachment in the bug description, see https://bugzilla.novell.com/attachment.cgi?id=437718
Comment 3 Thomas Schraitle 2012-04-19 13:55:06 UTC 
No problem. :)

Together we found out that the respective graphic contained a typo in its width attribute (140% instead of less than 100%). Therefore, FOP used this value and override its margins. It seems to me, this is the correct behavior.

For some reasons, XEP doesn't do the same as FOP and overprint the margins. It stays below 100%.

It may be an implementation detail, but for the time being, it is not really a bug itself. Therefore, closing it as INVALID.

Thanks anyway for the report and figuring it out with me! :-)