What sets FINAL_CONTENT_TYPE?

[Paul Conklin]

Johannes,
thanks so much for the link.  I think this portion:

Adding Additional Filter Stages to the Default CUPS Filter System

will allow me to do exactly what I want.  I'm still perplexed as to why the filter chain seems to keep changing (more so it seems the FINAL_CONTENT_TYPE keeps changing from application/<printer name> to application/vnd.cups.postscript)  but if this works, i'll be a happy camper.  Thanks much.

> i need to use the ppd as i need to be able to set it via the WI and i have user configurable options.  Whats odd is it works reliably 100% of the time on 1.4.x,  when i go to 1.5.3 it gets flakey.  I acutally have my logging set to debug2.  I never see it call my custom filter, which it should under all circumstances do to the cupsFilter strings i have added.
> >
> > Hello,
> >
> > On May 29 07:15 Paul Conklin wrote (excerpt):
> > > *cupsFilter:    "application/vnd.cups-postscript 0 coffee"
> > ....
> > > call my custom filter w/o calling any other filters.
> >
> > If only your filter and not any other filter should run, don't use
> > a PPD ("overkill" for this case) but set up the print queue with a
> > so called "System V style interface script", see "man  lpadmin" and
> > http://en.opensuse.org/SDB:Using_Your_Own_Filters_to_Print_with_CUPS
> >
> >
> > > it completely bypasses my filter
> >
> > Usually /var/log/cups/error_log shows what the file type is and which
> > filters (and backend) are run, for a first check you may use e.g.:
> > -------------------------------------------------------------------------
> > $ egrep 'File of type|Started' /var/log/cups/error_log
> >
> > I ... File of type text/plain queued by "...".
> > I ... Started filter /usr/lib/cups/filter/texttops (PID 1150)
> > I ... Started filter /usr/lib/cups/filter/pstops (PID 1151)
> > I ... Started filter /usr/lib/cups/filter/gstoraster (PID 1152)
> > I ... Started filter /usr/lib/cups/filter/rastertogutenprint (PID 1153)
> > I ... Started backend /usr/lib/cups/backend/hp (PID 1154)
> > -------------------------------------------------------------------------
> >
> > For details and debugging you need to inspect /var/log/cups/error_log
> > directly preferably with "LogLevel debug" in /etc/cups/cupsd.conf.
> >
> >
> > Kind Regards
> > Johannes Meixner
> > --
> > SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany
> > HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
> >
>