Re: [cups-devel] When to use -dNOMEDIAATTRS when calling Ghostscript

Till,

NOMEDIAATTRS is intended to disable the default Adobe media matching algorithm, otherwise you'll end up with the wrong paper size, etc. from the embedded setpagedevice commands that get used.  I don't know whether it should only be used with the "cups" device or for all of the filtering needs - just do some testing with different media sizes to see what happens... :/

> On Aug 15, 2016, at 5:09 PM, Till Kamppeter <[email protected]> wrote:
> 
> Hi,
> 
> what is the original intention of -dNOMEDIAATTRS on Ghostscript calls for CUPS filters or drivers?
> 
> Do I have to call it from all Ghostscript calls out of the CUPS filter chain, independent which driver type (Raster, Ghostscript built-in, ...), because the pdftopdf filter is taking care of the page size and other media attributes? Or only for Ghostscript calls with "cups" output device (Ghostscript call in gstoraster filter)?
> 
> Especially there can be the following calls of Ghostscript:
> 
> - gstopdf: Call of Ghostscript with "pdfwrite" output device to turn PostScript input data to PDF to feed it into pdftopdf
> - gstoraster: Call of ghostscript with the "cups" device to turn PDF output from pdftopdf into Raster for rasterto... CUPS printer drivers or IPP Everywhere printers
> - gstopxl, foomatic-rip, ...: Call of Ghostscript with a built-in printer driver, like "pxlmono" for example, to turn PDF from pdftopdf into the printer's native language.
> 
> In which cases I have to supply -dNOMEDIAATTRS?
> 
>   Till
> _______________________________________________
> cups-devel mailing list
> [email protected]
> https://www.cups.org/mailman/listinfo/cups-devel

_________________________________________________________
Michael Sweet, Senior Printing System Engineer