I don't know of any remaining problem with JPEG support in FOP. Could you post an example JPEG so one of us can reproduce the problem?
On 24.07.2007 20:41:55 Stefan Fassel wrote: > Hello > > First of all, I want to apologize for all sorts of errors made while > submitting this request for help, since this is my first time submitting to a > mailing list. > First the core problem maybe someone did experience the similar problems: > > I am generating PDF Files containing JPEG images using FOP. > Those PDF-Files previously readable with Acrobat Reader 6 are causing an > Error since Acrobat Reader 7. > > Since we dont have influence on the Acrobat Reader Versions our customers > use and Adobe has not fixed the Problem in the new Acrobat Reader 8.1 I am > pretty desperate to find a solution or workaround for this Problem. > > The Error displayed by Acrobat Reader is something like: > Not enough data for an image > (Nicht genügend Daten für ein Bild) > After the error has surfaced the Reader stopps to render the Document > correctly. > At first only certain images are not displayed while moving around the > document afterwards the rendered content disappears. > > Those certain JPEG images derived from our database do not have DPI > information stored in them. > Since supplying those malfunctioning images with DPI information and > generating the PDF anew made the Document readable I strongly believe that > this is the cause for my problem. > > Sadly fixing the images is not an option for me, since the amount of images > is huge and the risk of migration is too great for my company. > > I have found out that when using JPEG images and removing DPI information > manually, the generated PDF will not necessarily cause the error in Acrobat > Reader. (maybe there is some other factor involved) > > While searching for a workaround I have tried the following: > > *I have tested this issue with FOP Versions 0.93, 0.92 and 0.20.5 resulting > in the same error as in the Struts (cx) integrated solution we use for our > customers. > > *I have tried to reduce the xsl:fo code to a bare minimum and reducing the > amount of images in the document which did not help either. > Normally there are up to 10 images on each page with 2 pages per document. > > Here is the corresponding code: > > <?xml version="1.0" encoding="ISO-8859-1" ?> > <fo:root xmlns:fox="http://xml.apache.org/fop/extensions"; > xmlns:xi="http://www.w3.org/2001/Xinclude"; > xmlns:fo="http://www.w3.org/1999/XSL/Format";> > <fo:layout-master-set> > <fo:page-sequence-master master-name="pagemaster1"> > <fo:repeatable-page-master-reference > master-name="first" > maximum-repeats="no-limit" > master-reference="first" /> > </fo:page-sequence-master> > <fo:simple-page-master > margin-right="1.0cm" > margin-left="1.0cm" > margin-bottom="0.5cm" > margin-top="0.5cm" > page-width="29.7cm" > page-height="21cm" > master-name="first"> > <fo:region-body > margin-top="1.0cm" > margin-bottom="1.0cm" /> > <fo:region-before > extent="1.0cm" /> > <fo:region-after > extent="1.0cm" /> > </fo:simple-page-master> > </fo:layout-master-set> > <fo:page-sequence master-reference="first" initial-page-number="1" > force-page-count="no-force"> > <fo:flow flow-name="xsl-region-body"> > <fo:block> > <fo:external-graphic scaling="uniform" > content-width="3.75cm" > content-height="5cm" > width="3.75cm" > height="5cm" > src="url('images/testimage.jpg')" /> > </fo:block> > </fo:flow> > </fo:page-sequence> > </fo:root> > > *I have tried to make contact with Adobe about this matter, but at the moment > it seems I am on my own thats why Im looking for help here > > *Ive searched the Acrobat Reader options for settings that could work around > this problem, but I have only found a way to stop display large images. This > replaces images on the document with a gray rectangle. The error is not > displayed using this setting, but our customers say that this is not > acceptable for them. > > Any help would be welcome to find a workaround for this problem. > > I would favour a way to handle this in xsl:fo, but I still have not found a > solution in the documentation available. > > If this is an issue of the PDF-rendering module of FOP it would be good to > know, but it would limit our options considerably. (maybe force us to use > different libraries) > > Yours > > Stefan Fassel (Germany) Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
