[cups] debugging file auto-typing

Helge Blischke helgeblischke at web.de
Sat Feb 16 11:41:34 PST 2019

> Am 14.02.2019 um 21:23 schrieb Tim Mooney <Tim.Mooney at ndsu.edu>:
> I've considered that (although by replicating the rule to local.types),
> and I've also considered replicating the application/vnd.cups-raw rule
> to local.types with a priority(150), but doing either of them before
> I understand why auto-typing is treating some files differently strikes
> me as the wrong approach.  I might be able to accidentally solve this
> problem, but I won't actually know what the problem was.
> I'm pretty sure I'm going to end up doing something with local.types, but
> ideally I would first understand the problem, rather than randomly trying
> things.
> Tim

Without going too much into the details of how cups determined the type of the print data,
the main principle of this algorithm is to check the rules increasing from the lowest to 
the highest complexity (roughly with respect to computational effort).
So, the checking the file name extension is by far the simplest thing and is
tested first.
So, eliminating the pdf file name extension from the rules is certainly one of the
first methods I’d try in your case.


More information about the cups mailing list