[xep-support] Re: Question about BROKENIMAGE parameter

From: Michael Sulyaev <msulyaev@renderx.com>
Date: Wed Nov 23 2011 - 11:18:51 PST

On 11/23/2011 09:07 PM, Collins, Anthony Torrero wrote:
> My document has a number of mixed png, gif, and jpg images. If I set
> BROKENIMAGE to 404.gif, it’s fine unless the missing image is a png or a
> jpg. Then XEP complains about the 404.gif not being a png or jpg. I
> exported the 404.gif to 404.png and 404.jpg, but it doesn’t solve my
> problem. If I set BROKENIMAGE to 404.jpg, XEP complains about missing
> gif’s and png’s as being corrupt jpg’s etc.
> Can I specify more than one type of broken image? And will xep know what
> to do with them?

Hello Anthony,

There is no way to specify alternative broken images of different types,
and there is no need.

I've made some tests, and my observations do not match what you report.
(However, I suspect we might have had that issue long ago).

The following FO test produces a PDF with all the three missing images
replaced by 404.gif. XEP error messages honor the explicit content-type,
but the result is always the 404.gif.

<?xml version="1.0" encoding="utf-8"?>
<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
     <fo:simple-page-master master-name="all-pages">
       <fo:region-body region-name="xsl-region-body" margin="0.7in"/>
   <fo:page-sequence master-reference="all-pages">
     <fo:flow flow-name="xsl-region-body">

         A missing NOTYPE image
         <fo:external-graphic src="url('./NOTYPE.notype')"/>

         A missing GIF image
         <fo:external-graphic src="url('./NOGIF.GIF')"

         A missing PNG image
         <fo:external-graphic src="url('./NOPNG.PNG')"


What behavior do you observe in this test?
Anyway, please try the most recent build of XEP, and post your sample to

Michael Sulyaev
(*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support
(*) By using the Service, you expressly agree to these Terms of Service http://w
Received on Wed Nov 23 11:19:02 2011

This archive was generated by hypermail 2.1.8 : Wed Nov 23 2011 - 11:19:03 PST