[Rd] postscript bug? (PR#9803)

[Simon Blomberg]

D'oh!

Simon.

On Mon, 2007-07-23 at 12:36 +0200, Peter Dalgaard wrote:
> s.blomberg1 at uq.edu.au wrote:
> > postscript() produces files that are not encoded as eps, according to
> > the standard. Hence, word processors such as OpenOffice and AbiWord do
> > not recognise the files as eps. See
> > http://www.postscript.org/FAQs/language/node80.html
> >
> > The problem is in the first line of the postscript file: The header is
> > wrong. It should be:
> >
> > %!PS-Adobe-3.0 EPSF-3.0
> >
> > whereas postscript() produces:
> >
> > %!PS-Adobe-3.0
> >
> > The following code replicates the problem:
> >
> > x <- rnorm(10)
> > y <- rnorm(10)
> > postscript("test.eps")
> > plot(x,y)
> > dev.off()
> >
> > # Now try importing test.eps into your favorite word processor.
> >
> > # Now edit test.eps and change the header to the correct header above, 
> > and try importing the file again. Works! (This took me a couple of hours
> > of hair-pulling to figure out. I sure hope it is a genuine bug. :-) )
> >   
> It isn't a bug. It is as it should be, because a plot file with multiple
> pages cannot be EPS.
> 
> Try reading the help page for postscript again, this time ( ;-) ) paying
> attention to the 'onefile' argument.
> 
-- 
Simon Blomberg, BSc (Hons), PhD, MAppStat. 
Lecturer and Consultant Statistician 
Faculty of Biological and Chemical Sciences 
The University of Queensland 
St. Lucia Queensland 4072 
Australia
Room 320 Goddard Building (8)
T: +61 7 3365 2506 
email: S.Blomberg1_at_uq.edu.au

Policies:
1.  I will NOT analyse your data for you.
2.  Your deadline is your problem.

The combination of some data and an aching desire for 
an answer does not ensure that a reasonable answer can 
be extracted from a given body of data. - John Tukey.