Now I understand. That rings a bell. I haven't verified it but I think I know what the problem is. If you first render your document to PDF the image is loaded in decoded format and is remembered as such in the image cache. When you then render the same document to an RTF the RTFHandler is given the cached image but that image is in a state that doesn't allow for returning the undecoded image, but that's exactly what the RTFHandler needs. It's what I feared would happen one day and shows me that we should really revisit the image library sooner or later. Probably sooner. :-(
Ok, work-around: you can try to use different URL/filenames depending on whether you render to PDF or RTF. You may need to copy each image and give it a different name. You can then choose the right image by supplying a parameter to the XSLT file. That allows you to work-around the image cache. Note to fop-devs and possible contributors: I've already started to document the problem and possible solutions half a year ago: http://wiki.apache.org/xmlgraphics-fop/ImageSupport On 27.01.2006 11:56:57 [EMAIL PROTECTED] wrote: > I 've still have problems with with fo:external-graphics and rtf.I have a web > application that create dynamic documents. > It's happen that if I create a pdf (using FOP 0.9) and after that I create an > RTF I can see tha image just in the PDF and not in the RTF. > If I close my web session and restart it and I try to create just the RTF the > image amazingly appears!!! > Could be a caching problem of my web server (tomcat 5.0.25) or a fop 0.9 bug? > please help !! Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
