LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous (more recent) messageNext (less recent) messagePrevious (more recent) in topicNext (less recent) in topicPrevious (more recent) by same authorNext (less recent) by same authorPrevious page (March 2001, week 1)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Thu, 1 Mar 2001 15:06:43 -0500
Reply-To:     "Fuchs, Tom" <Tom.Fuchs@LGEENERGY.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "Fuchs, Tom" <Tom.Fuchs@LGEENERGY.COM>
Subject:      Re: PSCOLOR graphics driver
Content-Type: multipart/alternative;

David,

The gprologue value you are using is %! (2521) with a carriage return (0d) and line feed (0a).

-----Original Message----- From: Bohl, David [mailto:DBohl@ACNIELSEN.COM] Sent: Thursday, March 01, 2001 14:45 To: SAS-L@LISTSERV.UGA.EDU Subject: PSCOLOR graphics driver

When I generate a PostScript GSF containing multiple graphs (1 per page) using the PSCOLOR driver (SAS/GRAPH) , I have trouble viewing the resulting PostScript image using either of two popular PostScript screen pre-viewers: "pageview" in Solaris and "GSview" in Windows.

When I load the PostScript file into "pageview", it only displays the last page in the file. Also, "pageview" issues a warning to the effect that the "PostScript structuring comments are not being used correctly ...", whatever that means -- not sure if it's related.

When I pre-view the same file using "GSview", it displays all the pages all right, but I can only scroll forward through the file (i.e., the only way to go back to a previous page is to re-load the file). When I try to scroll back, it complains about "incorrect page numbering". I don't have this problem with PostScript files generated by PS drivers from any other software packages. I suspect that the symptoms from the two pre-viewers arise from the same problem(s) in the PS file. SAS tech support is stumped and doesn't necessarily admit that PSCOLOR is the culprit.

Are these known problems with the PSCOLOR driver and are there any known work-arounds.

Thanx,

Dave

PS here's an example of how I'm using PSCOLOR to generate a PostScript GSF from Solaris (don't remember where I found that gprolog value, but it doesn't work w/out it):

filename PSFILE 'graph.ps'; goptions nodisplay gunit=pct device=pscolor rotate=landscape gsfmode=replace gsfname=PSFILE gprolog='25210D0a'X; proc greplay nofs igout=SASDATA.PLOTS; replay _ALL_; quit;


[text/html]


Back to: Top of message | Previous page | Main SAS-L page