[XeTeX] Problem with XeTeX 0.9999.2 and includegraphics

[David Carlisle]

On 18 April 2013 05:17, Wilfred van Rooijen <wvanrooijen at yahoo.com> wrote:

>
>  >Avoid file names with an unusual number of dots (unusual is
> > everything not equal to 0).
>
> I would say everything not equal to 1. In fact, I am surprised that
> graphicx processes the file name with two dots correctly. Normally graphicx
> uses the last dot to be the delimiter for the file extension. Anything that
> looks like .crop.pdf or so usually does not work. How does graphicx
> implement the routine to determine the file extension. Apparently it uses
> some tex-engine specific routines. I never knew that.
>
>
>
by default graphicx takes everything after the first . as the extension,
what happens after that is up to the back end driver code. On drivers where
different inclusion \special's are needed for different filetypes then
normally such filenames don't work by default however some drivers
basically treat all file types the same at this level in which case the
extension doesn't matter (This seems to be the case with xetex.def which
has a default rule for any extension)

You can disable the graphicx filename parsing and supply the extension
explicitly.

\includegraphics[type=QTm,ext=.foo.bar.1]{my.file}

should load my.file.foo.bar.1 and handle it via is QTM code. If you use the
ext key the graphicx code does not try to split up the filename given in
the second argument.

David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tug.org/pipermail/xetex/attachments/20130418/fa3cce05/attachment.html>