Optimized postscript specification

Tks Helge,
i think i can handle it from here.

As for Xerox' DocuSP, form caching only takes place if the form is set up as a PostScript resource (via defineresource) and then loaded by findresource.

I necessary, I'll try to retrieve that paper again.

Helge

Better to say in advance that i'm not an postscript expert. I'm just a postcript newbee trying to fix the postscript generated by a tool

Tks Isaacs,
"Optimized postscript" his mencioned in some some VDP tools, like print shop mail. After your statment i guess it means only eficiente reuse of resources.

But still something is wrong that causes Xerox DocuSP Controller to process the same image several times.
Maybe is the way the image is called.

Here is a sample:

/@GP
{
save exch mark exch
execform
cleartomark restore
} bd

/@CForm {
10 dict begin
/EPSArray exch array def
/BBox exch def
/FormType 1 def
/AcquisitionProc {
EPSArray dup 0 get dup 0 get % array counter_array counter
dup 3 1 roll % array counter counter_array counter
1 add 0 exch put % increment counter
get % use old counter as index into array, placing
% next string on operand stack.
} bind def

/PaintProc {
begin
EPSArray 0 get 0 1 put
/AcquisitionProc load 0 () /SubFileDecode filter
cvx exec
end % form dict
} bind def

/Matrix [1 0 0 1 0 0] def
currentdict end def
} bind def

The EPS image:

/@G1 [0.00 0.00 522.72 233.04] 27 @CForm
/inputFile currentfile 0 (% EOD_Marker_002) /SubFileDecode filter def
@G1 /EPSArray get
@ReadData
@GB
%!PS-Adobe-2.0 EPSF-1.2
%%Creator: Transfrm JPG
%%Title: PORSCHE

Finaly calling the image:

gsave 28.35 -516.54 translate @G1 @GP grestore

On behalf of Adobe Systems Incorporated, let me advise that there is no such thing as an official "optimized PostScript specification." There are some vendors who have hacked around with various PostScript interpreter implementations to specially handle certain PostScript constructs in their own environment, but these protocols are certainly not universal!

- Dov

Seems to be the only way. Our primer Xerox contact says its public, but i can't find those guide lines anyware in the net.
Tanks

"Optimized PostScript" usually means guide lines for generating PostScript jobs that may speed up the RIPing process by various means which may be highly RIP-vendor dependent, such as:

- specifying images used repeatedly as PostScript forms,

- downloading images used repeatedly prior to the job and RIPing them
separately, then linking the pre-ripped images to the job

- using subsetted fonts

and many more such tricks.

I'd suggest to ask - in your case - the Xerox people for optimizing recommendations and/or software. Note that it depends on the controller software you are using for your iGEN.

Helge

There is no specification. This is not a formal term.

Aandi Inston