From: seidl@next1.lbl.gov (Peter Seidl)
Newsgroups: comp.sys.next.software
Subject: postscript formats, previewer
Date: 25 Aug 1992 21:07:27 GMT
Organization: Lawrence Berkeley Laboratory, Berkeley CA
Distribution: world
  i
Reply-To: seidl@next1.lbl.gov
NNTP-Posting-Host: next1.lbl.gov
Keywords: postscript, preview

I have not been able to display in color a Postscript file that was translated  
from cgm format on a MacIntosh using the Preview utility (release 2.0 v22).  
however, the same file shows colors nicely on a Silicon Graphics computer. This  
is what the beginning of the file looks like:

%!PS
save
/w {setlinewidth} def
/l {lineto} def
/n {newpath} def
/m {moveto} def
/s {scale} def
/c {setlinecap} def
/j {setlinejoin} def
/r {restore} def
/h {showpage} def
/t {stroke} def
/f {eofill} def
/ct 256 array def
/o {ct exch get aload pop setrgbcolor} def
125 .125 s
1 c
1 j
n
 ct 0 [1.000 1.000 1.000] put
 ct 1 [0.000 0.000 0.000] put
 ct 2 [1.000 0.000 0.000] put
 
 
 

Now, I realize that this does not have the recommended file header (the  
Previewer warns that "the file is missing the proper PostScript header  
information.  If you attempt to open it anyway, you will only be able to page  
through the file's pages sequentially.)  But I haven't had much success with  
modifying the header, as per my next puzzle:

I have files that were generated on a Digital Vax computer, and get the same  
message as above.  Here is what the beginning of the Vax generated Postscript  
files look like:

%!PSAdobe-1.0                                                                   
%%Creator: SEIDL                                                                
%%Title:                                                                        
%%CreationDate: 08/20/1992 13:49:12                                             
%%Pages: (atend)                                                                
%%DocumentFonts: (atend)                                                        
%%BoundingBox: (atend)                                                          
%%EndComments                                                                   
/saveobj save def                                                               
/center {/yarea exch def /xarea exch def newpath clippath pathbbox              
 /ury exch def /urx exch def /lly exch def /llx exch def                        
 /xoff urx llx sub xarea sub 2 div llx add def                                  
 /yoff ury lly sub yarea sub 2 div lly add def                                  
 xoff yoff translate} def                                                       
/draw {lineto currentpoint stroke newpath moveto} def                           
/move {newpath moveto} def                                                      
/font {exch findfont exch scalefont setfont} def                                
/background {/yarea exch def /xarea exch def gsave newpath 0 0 moveto           
 0 yarea lineto xarea yarea lineto xarea 0 lineto closepath                     
 eofill grestore} def                                                           
/defaults {setlinewidth setlinecap setlinejoin setmiterlimit                    
 0 array 0 setdash newpath 0 0 moveto} def                                      
%%EndProlog                                                                     
%%Page: 1 1                                                                     
575.28 744.48 center 0 0 0 setrgbcolor 10 0 0 0.1008 defaults 476.547 67.68     
move 467.039 67.68 move 476.547 67.68 move 467.039 67.68 draw 467.039 67.68     
move 457.531 67.68 move 467.039 67.68 move 457.531 67.68 draw 457.531 67.68     
move 448.024 67.68 move 457.531 67.68 move 448.024 67.68 draw 448.024 67.68     
 
 
 
This file does not have any color in it.  However, what I would like to do, if  
possible, is to somehow convert this file to be compatible with eps format so  
that I may import it into Framemaker documents.  Presently, I make bitmaps into  
tiff files, but this seems clumsy.  I have tried a few things like changing the  
file extension from .ps to .eps, and also modifying the comment header to  
conform with what I read in Supplemental documentation: Encapsulated PostScript  
File Specification, Version 2.0, pp. 4-5.  That didn't help.

Suggestions? 


--
Peter Seidl
Heavy Ion Fusion Accelerator Research 
Lawrence Berkeley Laboratory
Berkeley, CA 94720

seidl@next1.lbl.gov

--
Peter Seidl
Heavy Ion Fusion Accelerator Research 
Lawrence Berkeley Laboratory
Berkeley, CA 94720

seidl@next1.lbl.gov
Newsgroups: comp.sys.next.software