Displaying 20 results from an estimated 500 matches similar to: "problem with multiple figure postscript file"
2006 Oct 03
2
pdf/ convert/ font problem
Background:
OS: Linux Ubuntu Dapper
R : Version 2.3.1 (2006-06-01)
Emacs 21.4.1
ESS
Colleagues
This is neither a bug report, nor a complaint, so I think this is the
appropriate list.
I am getting an odd font problem with a pdf generated using
pdf(file =
"../figures/PCNM.models.larvae.fluor.zoo.stability.2001.and.2002.pdf",
title="", family="serif",
2001 Feb 19
1
ghostscript errors
gday R friends,
Since I had random errors with ghostscript 6.01 I thought I'd upgrade.
After upgrading to gs6.5 I've had problems. Originally, gs failed
complaining about lack of "__sysconf" in glibc2.2 so I upgraded glibc. Now I
get this. Note that it used to work with gs6.01.
I realise this is probably a ghostscript problem but you never know...
thanks,
John Strumila
>
2003 Apr 24
1
Invalid font in bitmap()
Dear all,
A few weeks ago I asked about X11() availability using CGI-perl. The
general advice was to use bitmap which requires ghostscript (Xvnc and
Xvbf were the other alternatives). My system administrator got around to
installing Aladin Ghostscript 6.0 and the setting the R_GSCMD
environment variable. Other system specification is given below.
But now I have a new problem that says that font
2006 Apr 29
1
Error in ghostscript ?
Just tried to run a perl script to do some ripping and converting of a
postscript file, and ghostscript bombed out with the error message
below. Can someone tell me is this really a ghostscript error, or is
there more to it than this? If need be, I can attach the perl script
that caused the error, but I think it is OK. Don't have another machine
to test it on. Oh yeah, FWIW, this is an
2001 May 07
2
postscript problem
hello all,
when trying to produce a plot with the following code
postscript("g6-5000-0705-b.ps")
par(mfrow=c(4,1))
for (i in 1:4) {
somc<-cumsum(betaC[,i])/c(1:N)
plot(somc,ylim=c(min(somc),max(somc)));
}
dev.off()
I get a postscript file g6-5000-0705-b.ps, but if I try to open it
with ghostscript, or to convert it to pdf, I get the following error :
Error: /invalidfont in
2005 Aug 22
1
Example in pdf() help file (PR#8083)
The example in the help file for pdf() plots the characters outside
the plotting area in this for loop:
for(i in c(32:255)) {
x <- i
y <- i
points(x, y, pch=i)
}
The following loop seems to be working as intended
for(i in c(32:255)) {
x <- (i-31)%%16
y <- (i-31)%/%16
points(x, y, pch=i)
}
As an extra
1999 Sep 08
1
PostScript output error
Hello,
I'm currently using R-0.65.0 with --gnome option in
configure on IRIX64 and Debian GNU/Linux.
I found a problem in generated postscript file which
has following sequence:
x <- 1:30
postscript("output.ps")
par(mfg=c(1,1,2,2))
plot(x,sin(x))
plot(x,sin(x))
plot(x,sin(x))
plot(x,sin(x))
dev.off()
The generated postscript file "output.ps" can't
2010 Feb 22
2
(Somewhat) broken EPS files produced
Hello.
I'm writing some simple text using sweave, and faced a strange problem
with eps files produced for my plots (one example attached).
Individual eps files are interpreted by ghostscript just fine, and
show up without errors. But once I try to include them into main
LaTeX/Sweave document (using regular \includegraphics, produced by
Sweave),
ghostscript gives me this error on those files:
2001 Feb 01
1
postscript and lty
To the plot experts:
when creating a plot containing different lines, each with a special line
type, it may happen that the result of 'postscript()' is not readable by
ghostview (which may not be an R error, thus not bug report ;-).
This is the case when mixing lty as 0:6 and character or even when
using lty as character only.
Example:
postscript("test.ps")
plot(1:10,
2006 May 10
0
Making pdf with HTMLDOC
Hello,
I''m having a problem with HTMLdoc and rails.
I''ve set it up as per
http://wiki.rubyonrails.com/rails/pages/HowtoGeneratePDFs and I''m using
windows and version 1.8.24.
I can make ps files without a problem and I can make pdfs using the
stand alone app, however I can''t get the pdf created in RoR to work.
Loading it into gsviewer I get the error
2009 Jul 15
1
ghostscript 8.64 errors.
Hello,
To fix some issues in working with gs 8.63 I had to upgrade to 8.64. I build the rpm from ghostscript-8.64-9.fc11.src.rpm. I get the following error when running
gs -q -dSAFER -dNOPAUSE -dBATCH -dUseCropBox -dFirstPage=1 -dLastPage=1 -sOutputFile=/tmp/TIFF-%d.tif -r300 -sDEVICE=tiff12nc foobar.pdf
#
Error: /invalidfont in /findfont
#
Operand stack:
#
2000 Feb 20
1
split.screen + postscript Problem (PR#454)
Dear R-helpers,
with R-0.99a, Linux, Red-Hat 6.1 derivat (Halloween Linux) I have
the following Problem with this code:
graphics.off()
close.screen(all=T)
temp <- matrix(c(0 , 1 , .4 , 1,
0 , 1 , 0 ,.4),
ncol= 4,
byrow=T )
split.screen(temp)
plot(1:100)
2005 May 17
1
spandsp + HFC poor fax quality?
I've been trying to set up incoming faxes using spandsp with a HFC card.
Unfortunately, incoming faxes are of very poor quality, the pages are
not transferred wholly (sometimes only a bit of a page is transferred etc.).
From what I've read, I may have troubles with correct "timing" (and
need to set up ztdummy etc.).
On the other hand, it is impossible to set ztdummy if one
2005 Jan 24
1
R 'postscript' plot - not a valid postscript (PR#7559)
Full_Name: Mr. Daniel Murray Bolser
Version: R 2.0.0 (2004-10-04)
OS: Linux beagle 2.4.20-31.9 #1 Tue Apr 13 17:38:16 EDT 2004 i686 athlon i386 GNU/Linux
Submission from: (NULL) (193.60.81.207)
Trying to execute the following code produces a 'not a valid postscript' error
from various postscript readers (gv, ggv, ghostscript). A very similar code
works fine.
<CODE>
postscript()
1999 Jul 17
0
Use of lwd = 0, lty = 2 in segments. (PR#230)
This may not be considered a bug but it is an incompatibility with S.
There was a convention in S that the graphics parameter setting
lwd = 0
is supposed to use the minimum possible line width on the device. It
is not clear what that means on modern graphics devices but there is
still code (like mine) that assumes something sensible happens with
lwd = 0
It seems that R's postscript
2012 Apr 27
0
imagemagick convert/display eps file no decode delegate
I am finding on all my CentOS 5.8 systems (all fully updated but a variety of package mixes) that the display or convert commands from ImageMagick are unable to handle eps files. I get error output as follows, curious if anyone else sees this
$ convert rna.eps rna.epi
convert rna.eps rna.epi
Error: /undefinedfilename in (72x72)
Operand stack:
Execution stack:
%interp_exit .runexec2
2009 May 06
2
Ghostscript in 5.3
Ever since I updated to 5.3, I have been unable to convert any ps
files to pdfs using the ps2pdf command. I usually get errors like
this:
[mhr at mhrichter forms]$ ps2pdf doe81008
ERROR: /undefinedfilename in (doe81008)
Operand stack:
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval--
--nostringval-- 2 %stopped_push --nostringval--
--nostringval--
2007 Sep 20
1
Sweave vignettes and bitmap on windows
During vignette generation on Windows, Sweave seems to clean up before
all graphics files are completely processed. For instance, if tmp.Rnw
is:
\documentclass[12pt]{article}
\begin{document}
<<>>=
bitmap("afile.png")
plot(1:100)
dev.off()
@
\end{document}
Then:
C:\R\tmp>R CMD Sweave tmp.Rnw
Writing to file tmp.tex
Processing code chunks ...
1 : echo term verbatim
2012 Feb 07
1
pdfmerge and ghostscript-8.70-6.el5_7.6.x86_64
Everyone,
It looks like pdfmerge is broken after the recent upgrade of gs to
ghostscript-8.70-6.el5_7.6.x86_64. Has anyone else had this problem. I
have just started trying to debug it. If any of you already have
solutions please let me know.
Thanks,
Greg Ennis
2005 Oct 11
1
MiKTeX/yap/Ghostcript issues with R-generated postscript
Hello,
I wonder if anybody has encountered this problem?
While MiKTeX/yap/Ghostscript seems to work fine on most TeX files that I
have
tested (including a great deal of postscript graphics), there is one
file where the
graphics works ok for all postscript files except one, the only one that
is generated
by R. I get an error "Some postscript specials could not be rendered",
and the