2009-01-06 17:53:25 |
Dan |
description |
Binary package hint: ghostscript
Some postscript files, such as those generated by the Windows PS driver output messages to stdout while executing. For example, the attached file, generated from a Word document, displays the following when ps2pdf is invoked on it:
%%[ ProductName: GPL Ghostscript ]%%
%%[Page: 1]%%
%%[LastPage]%%
When scripts such as ps2pdf are used with the output file set to "-" (i.e., stdout), these messages get included in the output file. Occasionally, this causes corruption of the output file. This is particularly problematic for the new PDF-based rendering path in CUPS.
The attached debdiffs add the flag -sstdout=%stderr to invocations of gs to redirect these messages to stderr. |
Binary package hint: ghostscript
Some postscript files, such as those generated by the Windows PS driver output messages to stdout while executing. For example, the attached file, generated from a Word document, displays the following when ps2pdf is invoked on it:
%%[ ProductName: GPL Ghostscript ]%%
%%[Page: 1]%%
%%[LastPage]%%
When scripts such as ps2pdf are used with the output file set to "-" (i.e., stdout), these messages get included in the output file. Occasionally, this causes corruption of the output file.
The attached debdiffs add the flag -sstdout=%stderr to invocations of gs to redirect these messages to stderr. |
|