Bug 798849 - max_image_width: 660 ignored for PDF builds
Summary: max_image_width: 660 ignored for PDF builds
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: 3.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
Assignee: Jeff Fearn 🐞
QA Contact: Ruediger Landmann
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-01 04:57 UTC by Kate Grainger
Modified: 2012-03-11 23:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-11 23:47:55 UTC

Attachments (Terms of Use)
Page overrun 1 (135.81 KB, image/png)
2012-03-01 04:57 UTC, Kate Grainger 		no flags Details
Page overrun 2 (75.15 KB, image/png)
2012-03-01 04:59 UTC, Kate Grainger 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Kate Grainger 2012-03-01 04:57:48 UTC 
Created attachment 566743 [details]
Page overrun 1

Description of problem:
Very large (wide) images are not being scaled to fit within the page width of PDFs, even when max_image_width: 660 is set in publican.cfg.

How reproducible:
Twenty figures in the RHEV suite of books have overrun in the PDF format.

Steps to Reproduce:
1. Create a very large (wide) image and include it in your xml.
2. Generate a PDF.
3. Your page runneth over.
4. Weep, gnash teeth.

Actual results:
Figures overrun page width.

Expected results:
Figures are constrained to the max_image_width of 660px.

Additional info:
See screen shots for examples.
Comment 1 Kate Grainger 2012-03-01 04:59:12 UTC 
Created attachment 566744 [details]
Page overrun 2
Comment 2 Jeff Fearn 🐞 2012-03-11 23:47:55 UTC 
Image sizes above 440px are not supported when using FOP because you have to use external tools to change the image DPI or it doesn't work properly. We do not have the person power to support this kind of thing and people choosing to use it must support themselves.
Note You need to log in before you can comment on or make changes to this bug.