To whom it may concern,
We have a solution in place, where we have customized the PPD file to add a watermark, or document classification stamp to each document printed.
This is already working, with all PostScript enabled printers.
If I print a test page from within CUPS, the watermark, and all of the extra logging that I scripted, all work as intended.
But, my primary application is sending raw PCL code to the printers, and with one particular print job, there is something inside of the PCL code that is causing CUPS to not print the watermark.
Actually, it appears as if the watermark routine is not even being called.
I know that using the "-l" option as an argument to the LPR command, will suppress all extra CUPS formatting. But, there is no "-l" option included with the LPR command in this case.
So, I must assume that the PCL code is sending something, to suppress the custom watermark solution.
When I print from this application routine, the print job prints just fine, but it suppresses the watermark routine.
The only way I can see this happening, is if the PPD file isn't even being read in.
The CUPS log files do not show any errors... They all show that the printed jobs are going through successfully. Which is true... They are just not adding the watermark...
If the watermark routine is called, it actually creates a temporary directory, where I dump the output to a postscript.in file, a conversion file to both PDF and plain text, and additional logging... All for debugging purposes...
In this case, the watermark routine is NOT being called. No temporary directory is created, and no files are being created.
Here is my question:
Is there some way to add EXTRA logging, to see whether the PPD file is being read, or whether the PCL code is causing the PPD file to be overlooked?
Maybe an extra option to the LPR command, to cause verbose output to a separate log file?
Thanks in advance, and have a great day...
JCF
We have a solution in place, where we have customized the PPD file to add a watermark, or document classification stamp to each document printed.
This is already working, with all PostScript enabled printers.
If I print a test page from within CUPS, the watermark, and all of the extra logging that I scripted, all work as intended.
But, my primary application is sending raw PCL code to the printers, and with one particular print job, there is something inside of the PCL code that is causing CUPS to not print the watermark.
Actually, it appears as if the watermark routine is not even being called.
I know that using the "-l" option as an argument to the LPR command, will suppress all extra CUPS formatting. But, there is no "-l" option included with the LPR command in this case.
So, I must assume that the PCL code is sending something, to suppress the custom watermark solution.
When I print from this application routine, the print job prints just fine, but it suppresses the watermark routine.
The only way I can see this happening, is if the PPD file isn't even being read in.
The CUPS log files do not show any errors... They all show that the printed jobs are going through successfully. Which is true... They are just not adding the watermark...
If the watermark routine is called, it actually creates a temporary directory, where I dump the output to a postscript.in file, a conversion file to both PDF and plain text, and additional logging... All for debugging purposes...
In this case, the watermark routine is NOT being called. No temporary directory is created, and no files are being created.
Here is my question:
Is there some way to add EXTRA logging, to see whether the PPD file is being read, or whether the PCL code is causing the PPD file to be overlooked?
Maybe an extra option to the LPR command, to cause verbose output to a separate log file?
Thanks in advance, and have a great day...
JCF