[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#259390: graphics/3576 Includegraphics has strange filenamerestrictions



On Sun, Jan 23, 2005 at 11:39:28PM +0100, Hilmar Preusse wrote:

> On 05.01.05 David Carlisle (david@dcarlisle.demon.co.uk) wrote:
> > Hilmar Preusse wrote:
> > >On 16.07.04 Ajay Shah (ajayshah@mayin.org) wrote:
> 
> > >> I would respectfully like to say that from an end-user
> > >> perspective, this is a horrible and incompetent bug. I am a geek
> > >> and I'm perfectly okay with the workarounds (I just switched
> > >> from '.' to '_'). But to tell a lay user that
> > >> 
> > >>              \includegraphics{last.year.revenue.pdf}
> > >> 
> > >> will not work: it makes us look incompetent.

The code of my package grffile that contains a solution for this
problem is ready (this was already discussed in a newsgroup).
Unhappily the documentation and my dtx framework is not yes
finished.

> > \DeclareGraphicsRule{*}{pdf}{*}{}
> > 
> > would make pdflatex default to pdf inclusion rather than giving an
> > unknown type error.  Your example quoted above would then work.
> > 
> > Probably this should be in pdftex.def (dvips.def defaults to eps 
> > inclusion for similar reasons)  or it can be given in a document
> > preamble or graphics.cfg file.
> > 
> Thanks for the hint! What is the disadvantage of that solution? That
> pdftex after that knows only pdf files? That compressed files are not
> recognized any more?

Some people prefer to use the default rule for mps files, so that
they can use the files .1, .2, ... in a direct way without 
renaming to .mps.
  Also the problem for .jpg, .png remain.

> > > Heiko Oberdiek was so kind to write a workaround I attach here.
> > >
> > This would be interesting code to publish as a ctan package,
> > however I think that it is too extensive a change to the core latex
> > kernel filename handling. (for latex2e).
> > 
> Well I wouldn't agree on putting that code into the LaTeX2e kernel,
> as it is nearly untested (at least by me). How about trying to put
> that code into LaTeX3? That one has IIRC still the status
> experimental.

I will release a package, my hope is before EuroTeX.

Yours sincerely
  Heiko <oberdiek@uni-freiburg.de>



Reply to: