|
It appears that this problem goes away so long as the first image that appears is of reasonable size.
Hence another workaround is to:
You could also try customizing pdf's with a bigger width http://confluence.atlassian.com/display/DOC/Customise+Adobe+PDF+Exports
I think if a page contains an image that is too large, it should either be able to resize it to fit on page or cut it in pieces. But it should not end with error. For a user, that has no idea what is going on, this is unacceptable.
This issue occurs only if the image is too high for the page. FOP uses the width of the image to calculate the scaling and if its wide enough, you wont see this issue.
This issue similar to what happens with Apache Forrest (which uses FOP internally).
Adding a smaller image before the large image did not work as a workaround for me. I tried setting a smaller height parameter for the image so I would not have to scale the image, but that didn't help either.
Adding "align=center" parameter to the image worked however. Agree we should be able to handle this error more gracefully. A warning to the user which includes the page affected would be suitable.
Fixed in 2.6.0.
We have verified that the images provided by customers that previously caused errors, no longer do when performing PDF exports in the latest 2.7.3. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
If you are exporting a page you will have to narrow down which page it is by doing a binary search. That is, if your space had 200 pages, attempt to export the space with only the first 100 pages and then again on the 100 pages that produced an error and so forth until you narrow it down.
Removing or resizing the table should generally fix the problem.
Closing this issue with this workaround.