[cups.bugs] [MOD] STR #2626: pstops

H. Blischke h.blischke at srz-berlin.de
Thu Dec 13 10:11:28 PST 2007


DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR New]

A first approach would be to do the modifications as indicated by the
following diff:

diff -c paps.ps paps-mod.ps
*** paps.ps     Thu Dec 13 17:07:08 2007
--- paps-mod.ps Thu Dec 13 18:51:36 2007
***************
*** 7,12 ****
--- 7,13 ----
  %%Pages: (atend)
  %%BoundingBox: 0 0 612 792
  %%EndComments
+ %%BeginProlog
  /papsdict 1 dict def
  papsdict begin

***************
*** 51,56 ****
--- 52,59 ----
    90 rotate
    0 pageheight neg translate
  } def
+ %%EndProlog
+ %%BeginSetup
  % User settings
  /pagewidth 612 def
  /pageheight 792 def
***************
*** 100,106 ****
  /paps_eop {  % End of page cleanups
      grestore
  } def
! %%BeginProlog
  /papsdict 1 dict def
  papsdict begin

--- 103,109 ----
  /paps_eop {  % End of page cleanups
      grestore
  } def
!
  /papsdict 1 dict def
  papsdict begin

***************
*** 276,282 ****
  end_ol
   } def
  end end
! %%EndProlog
  %%Page: 1 1
  paps_bop
  ()paps_exec
--- 279,285 ----
  end_ol
   } def
  end end
! %%EndSetup
  %%Page: 1 1
  paps_bop
  ()paps_exec


With these modifications, it should go through the pstops filter with your
options set.

Besides these formal deficiencies, the paps generated PS has a couple of
other flaws, e.g.:

The setduplexmode operator (and similar ones) in statusdict might not be 
implemented in level 2 or level 3 interpreters.

Procedure definitions and job specific settings are intermixed, the setup
section in the modified PS job contains a lot of stuff that ought to be in
the prolog.

Link: http://www.cups.org/str.php?L2626
Version: 1.3.4





More information about the cups-devel mailing list