On 10/13/2014 04:09 PM, [email protected] wrote:
We see that in 5.1 version |fo:external-graphic|element references a
graphic file having *no file extension *is fixed. But we observed that
the mimetype image/jpg(without e) is not working for the jpg image
graphic file having *no file extension *and image/jpeg(with e) is
working. This is like the same issue which has got fixed in version *4.5
*for a graphic file having file extension.
I'm not sure to understand.
The change in v5.1 is described as below:
---
When a fo:external-graphic element references a graphic file having no
file extension and when attribute content-type is not specified, XFC now
uses the Content-Type header returned by the HTTP server to determine
the format of the graphic file. Example of such fo:external-graphic:
<fo:external-graphic
src="url(http://acme.com/logo-generator?w=100&h=200)"/>
---
The change involves a *server*, typically an HTTP server, returning
images to the client.
The changes does not involve fo:external-graphic referencing local
files, for which content-type="image/jpg" is supported.
Do you mean
---
When the *server* we use returns a Content-Type header containing
"image/jpg", it does not work, but when this server returns a
Content-Type header containing "image/jpeg", it works.
---
Well, if the issue you have is described by the above sentence, we'll
fix it in the next release of XFC.
Otherwise, do not hesitate to send us another email explaining your
problem. Please attach to your email a sample ".fo" file (no ".xsl" or
".xslt" files please) showing the problem.
--
XMLmind FO Converter Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xfc-support
