Negative offesets in mime.types

[Anonymous]

Fair enough.  I tried using a 'contains' directive with a zero offset and a (very) large range value to see if that would work, but it doesn't seem to.  I'm not too upset about it, since that wasn't a very elegent solution anyway.  Maybe I can do this a different way.  I'm using Linux, and it appears that the file extension doesn't survive long enough into the print process to be used as a MIME cue.  The files have the .tga extension, and I've put that into the mime.types file, but it never seems to make the match.  Am I just doing something wrong here?

 Thanks again,
    Rob

Michael Sweet wrote:
> Anonymous wrote:
> > I'm trying to implement a filter for the Targa (tga) image type, and
> > it turns out that the identifying information is at the end of the
> > file.  I would like to perform a string match to identify the file,
> > but I can't predict the offset from the beginning of the file to do
> > this.  Does CUPS support the use of negative offsets in the
> > mime.types file to make this happen?
>
> No, but I'm not sure if we could implement it - gzipped files don't
> allow efficient random access...
>
> --
> ______________________________________________________________________
> Michael Sweet, Easy Software Products           mike at easysw dot com
> Printing Software for UNIX                       http://www.easysw.com