|
Apparently this is due to png images with an unusual dpi setting (72.009 dpi).
Please see the attached png image and pdf. thanks, Andrew,
we have tested a single page pdf export with the image you attached to this issue and it was no problem to open the resulting pdf in Acrobat Reader 6.0 on Windows XP. Have you tried a single page export to see if the page with the image included is failing to be opened in Acrobat? Would you be able to provide a space backup so we could try to reproduce the problem locally? Where did you get the idea that the image is the root of the problem? Cheers, Hi,
I must admit to not being able to find the button to export a single page - where should it be? But I've done an 'export space', restricting the export to that single page, and it won't load when exported. If I load the image into an editor and resave with a different DPI, then upload to confluence and export exactly the same page, then the pdf works fine. cheers, Hi Andrew,
You can find a little pdf icon at the top right of every page underneath the search button. This allows you to export the page to pdf with one click. Can you attach the created pdf document so I can try to open it over here? Cheers, This is an excerpt from catalina.out:
[INFO] JAI support was not installed (read: not present at build time). Trying to use Jimi instead Thanks for the excerpt of your logs.
Some of our users have found that finding the file confluence/WEB-INF/lib/JimiProClasses.zip, renaming it to JimiProClasses.jar and then restarting Confluence actually makes the export work successfully. However I'm quite sure JimiProClasses.zip was renamed to .jar in 1.4.1 and therefore this shouldn't be the problem. Please check it anyway whether there is a zip file or a jar. I couldn't find any bug report regarding PNG images with a specific resolution, but the problem might well be related to Jimi since it seems to have problems loading the image. Alternatively you could install JAI [1] to see if this specific PNG format is supported by the Java Advanced Imaging API. Hope that helps, Cheers, [1] Java Advanced Imaging API (http://java.sun.com/products/java-media/jai/forDevelopers/jaifaq.html Installing JAI helped. I had to restart Confluence, though.
It is worth to mention dependency on JAI in Confluence documentation, since FOP information message is confusing. Version 0.20.5 does have JAI support, according to their website. Andrew: this will be available on our main site tomorrow LA time Since it only seems to fail with specific png files, it is not really a dependency. However, we will add it to our documentation to make customers aware of the fact that the JAI library might be required.
Thanks for letting us know. Cheers, 2.2.8 is generating corrupt PDF exports for pages containing PNG images. No log errors are thrown by Confluence but the PDF file generates error 109 when opened in Acrobat Reader. An example PDF and problem PNG is attached (71 DPI with 32 bit colour). This error is blocking the CAC User Guide PDF.
This issue appears only to occur on instances with JIMI library, so apparently is related to either JIMI library bug in PNG support, or lack of support for certain PNGs. Error has been encountered on CAC, which uses JIMI library but not JAI. Further testing is needed.
If encountered, the current workaround is to install the JAI from http://java.sun.com/products/java-media/jai/ David Soul Example problem PNG attached
Could not replicate with:
May need to replicate as completely as possible. Possible ideas
Dave Soul |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
It sounds like there is some content being converted into PDF that is not valid on acrobat 6 or 7. It would be great if you could help us investigate this issue a little bit by,
a) generate the pdf that failing, and rather than opening it from within your browser, save it to disk and then open it. I have seen reports that mention this error in the same sentence as problems with the IE pdf plugin.
b) can you try to isolate the page/pages that are causing the problem. ie, when you find a PDF file that is generating this error, remove some of the pages until you have narrowed down the offending page(s). If possible, can you send us the wiki text of those pages. This will allow us to isolate wiki markup that is responsible for causing the invalid PDF content. Alternatively, if you dont have time for this, is it possible to send us the space backup for a space that is consistently generating this error?
Regards,
-Daniel