clone 443832 -1 reassign -1 transfig retitle -1 fig2dev generates Postscript that is not DSC 2.0 tags -1 + confirmed thanks
Hi Stephen! On Tue, 23 Oct 2007, Stephen Benoit (Linux) wrote: > I just hit a similar problem, test the following if it works for you. As far as I can see, that's a completely different problem (that's why I clone the bug report), but I hit it myself yesterday. > Printing from xfig (or fig2dev) to postscript generates postscript > that is not fully DSC 2.0, or at least, CUPS can't read the DSC > information and stops the resulting print job. That's true. But it doesn't cause trouble on all drawings, but only on some (didn't check out what exactly triggers the problem). > One fix to demonstrate the problem: > (Idea from: http://osdir.com/ml/printing.cups.general/2003-10/msg00023.html) > - Export to a postscript file > - change the leading "%!PS-Adobe-2.0" to just "%!PS" > - print the new file to your CUPS printer. > ... this worked for me. This work around helped me on my problem image, too. > So this is either a xfig/fig2dev bug or a CUPS (cupsys) bug in > pstops. I know that some old postscript files I generated from > fig2dev under Woody and Sarge no longer print on the Etch version of > cupsys, so I think pstops is more fussy/specific than it used to be. I think its a bug of both. - fig2dev should not tag not fully DSC 2.0 compliant code as %!PS-Adobe-2.0" - cups should be less restrictive on what it accepts, because it can handle the PS code, if you change the tag from "%!PS-Adobe-2.0" to "%!PS". Tschoeeee Roland -- * [EMAIL PROTECTED] * http://www.spinnaker.de/ * -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
