Comment # 19 on bug 961864 from Johannes Meixner

Regarding comment#17 "redirect the output for the printer to a local file"
see comment#10.

Obviously one cannot redirect the output for the printer to a local file
without changing the existing printer configuration because redirect the
output means changing the existing printer configuration.

But one can set up a separated print queue where the CUPS filtering
is the same by using the exact same PPD as used for the existing
printer configuration but where the output is sent to a file.

How to do that is described in comment#10.

To verify that the output in the file causes the same error in the
PostScript printer as the existing printer configuration
you need to send the content of the file as is without any changes
to the PostScript printer.

This is done by using the "-o raw" printing option:

  lp -d queue_name -o raw file_name

This is vaguely described at
https://bugs.freedesktop.org/show_bug.cgi?id=44501#c1
but what is described there is not really exact.
In particular therein the "2. Print it to a PDF file."
could result a different PDF compared to when printing
from the application, for more information see in particular
"Background Information regarding Print as PDF versus Save as PDF" in
https://en.opensuse.org/SDB:Printing_to_PDF

Therefore when analyzing printing output from applications
the exact way is "Get what the application submits to CUPS" in
https://en.opensuse.org/SDB:How_to_Report_a_Printing_Issue

In contrast when analyzing what is sent to the printer
the best way (as far as I know) to get what is sent to the printer
is to set up a separated print queue with the exact same PPD as used
for the existing printer configuration but where the output is sent
to a file as described in comment#10.