similar to: suggestion: postscript paper=user

Displaying 20 results from an estimated 3000 matches similar to: "suggestion: postscript paper=user"

1999 Sep 09
1
read.table bug
Suppose we have a data file containing: "Smith, John", 120, 90 "Thomson, Peter", 110, 85 there are 3 variables in it. If we use x <- read.table("tmp.txt", sep=",") to read the data to a data.frame, the result will be 4 columns. Splus 4.0 have no problem with this kind of data. Li Dongfeng
1999 Sep 09
1
read.table bug
Suppose we have a data file containing: "Smith, John", 120, 90 "Thomson, Peter", 110, 85 there are 3 variables in it. If we use x <- read.table("tmp.txt", sep=",") to read the data to a data.frame, the result will be 4 columns. Splus 4.0 have no problem with this kind of data. Li Dongfeng
2001 Apr 14
1
Postscript font bugs (and a suggestion) (PR#914)
Documentation and other bugs with postscript(): 1. This code crashes R (it asks for a font that isn't there): postscript() plot(0:1,0:1) text(0.5,0.5,'crash',font=6) The bug appears to be in the FixupFont routine in plot.c; on line 236, it checks that the font number is in the range 1..32. Later this crashes PostScriptStringWidth in devPS.c, because only fonts numbered 1..5
2000 Jun 09
1
Postscript device ignores title if it is too long. (PR#565)
Hi, This may just be an inconsistency between terminal drivers, rather than a proper bug. If the main title of a plot is too wide to all fit on the plot, the X11 driver prints as much of the title as it can, but the postscript driver totally ignores the title. Here's a simple example: % R > plot(runif(1000), main="a long xxxxxxxxxxxx title") >
2000 Jul 01
0
margins with postscript device
I've been having a problem when printing plots to a HP DeskJet 2500C printer. This printer, like most inkjet printers, has a large minimum bottom margin. For most HP inkjet printers, the bottom 1/2" (left 1/2" inch for landscape) of the page can't be printed too. The postscript device in R has a default of 1/4" margins between the paper edge and the plotting area. This
2004 Sep 13
1
bitmap() doesn't finish with file in Windows (PR#7224)
Full_Name: Tom Short Version: 1.9.0 OS: Win2000 Submission from: (NULL) (64.65.255.41) POSSIBLE WISHLIST, POSSIBLE BUG: The following code works on Debian, but fails on Windows 2000 with 'Error in file("test.png", "r") : unable to open connection': bitmap("test.png") plot(c(1,2,3)) dev.off() x = file("test.png","r") The problem is
2001 May 31
1
paper size in postscript driver
I have a non-PS printer setup to print under linux using ghostscript as a filter. This printer has two paper trays, one has letter paper, the other tabloid size paper. If I print from a program that uses a PPD file to configure the printer, like StarOffice or The Gimp, I can select the paper size from a nifty list. If I select letter size, the printer print with paper from the letter tray. If
2000 Aug 23
1
png device on Solaris
Hi, I compiled R 1.1.0 source on SUN Sparc solaric 2.5.1, using gcc 2.95.2. I need to use R to publish graphics to the web, the NEWS in this version said that there is a new png() device on X11(). But when I tried > png() I got this error. Error in png() : No png support in this version of R Can anyone tell me how to compile png support on solaris/unix? The new bitmap() device
1999 Mar 24
1
Problems with Postscript output
Hi, I have a problem with the Postscript mechanism of R: If I save figures in landscape format and try to insert them into a LaTeX document, I always have to swap the dimensions of the bounding box in line 9 of the Postscript file. Is there any reason why we can't simply swap left and bottom as well as right and top in line 435 of devPS.c? Thanks Arne
2008 Jul 01
1
Autoconf / Windows package building problem for device package
Dear list, Tadashi Kadowaki has developed a pdf device package that allows to add hyperlinks and popups to (currently) text, mtext and rect calls. The package passes R CMD check (minor warnings) and compiles on MacOS X and GNU/Linux, but we do not succeed in building the package for Windows. The current version of the package can be checked out as svn checkout
2001 Apr 14
0
Defining extra fonts in the postscript driver
I've been looking at the ellipse package I co-wrote with Ed Chow for S-Plus a few years ago, cleaning up the documentation now it's been ported to R (by Jesus Frias, thanks IOsu!) and I'm back as the maintainer. One of the things it did which we thought was kind of cute at the time was to use a few lines of Postscript code to define a font, where the glyphs were ellipses of various
2000 Jun 22
2
Postscript Legends (or not)
I discovered a little problem when using the Windows NT release of R 1.0.1, and it's still there in R 1.1.0. The boiled down version is this: I want to draw the following plot and put it into a Postscript file: x <- c(1,2,3,4); y1 <- c(1,2,3,4); y2 <- c(2,2,2,2) Fred <- c(1,2) postscript(file="d:/Bob/Papers/IFM/try2.ps") plot(x,y1, type="l")
2001 Jul 16
1
polyroot() (PR#751)
In a bug report from Nov.28 2000, Li Dongfeng writes: ----- I have found that the polyroot() function in R-1.1.1(both solaris and Win32 version) gives totally incorrect result. Here is the offending code: # Polyroot bug report: # from R-1.1.1 > sort(abs(polyroot(c(1,-2,1,0,0,0,0,0,0,0,0,0,-2,5,-2,0,0,0,0,0,0,0,0,0,1,-2)))) [1] 0.8758259 0.9486499 0.9731015 1.5419189 1.7466214 1.7535362
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
2004 Mar 16
1
Changing ComputerModern in postscript(...): A first attempt at contributing....
Hi First off, thanks to all the various R developers, your package is very impressive. I'm not sure what the protocols are for contributing, and I've not done this before, so please excuse nay obvious errors or oversights... Also I'm by no means an R,TeX/LaTeX, or typesetting expert, I have largely stumbled my way to this point. Objective: I'd like to get R postscript(...) to
2010 Jul 02
0
PDFfontNumber bugs in devPS.c (Re: plain text in Chinese can not be set)
On 2010-7-1 15:24, Jinsong Zhao wrote: > > Read the source again more carefully. I think I get the solution: > > Change the following line in PDFfontNumber function in devPS.c: > > num = 1000 + (cidfontIndex - 1)*5 + 1 + face; > to > num = 1000 + (cidfontIndex - 1)*5 + face; > > It appears two times in the function. > > However, I don't know how to compile
2010 Jul 04
0
PDFfontNumber bugs in devPS.c (Re: plain text in Chinese can not be set)
Hi Thanks very much for the report, diagnosis, and patch! I have implemented your fix in the development version of R. Paul Jinsong Zhao wrote: > On 2010-7-1 15:24, Jinsong Zhao wrote: >> Read the source again more carefully. I think I get the solution: >> >> Change the following line in PDFfontNumber function in devPS.c: >> >> num = 1000 + (cidfontIndex - 1)*5
2006 Nov 15
0
segfault in AIX
I'm trying to build R 2.4.0 on an IBM P5-570 that's running AIX 5.3. I'm using xlc 7.0, xlc++ 7.0 and xlf 9.1 in 32 bit mode (OBJECT_MODE is 32 in the build environment). The source is the patched version of 2.4.0, downloaded yesterday. Configure options were --prefix, --srcdir, --x-includes, --x-libraries, and --without-readline. Compiler flags were -O2. The make step fails with
2003 May 29
4
Postscript query: plotting long vectors
Hi, I have a query about the maximum length of vector that can be plotted in one go in a postscript driver. Try the following code (in 1.7.0; version details below): t <- seq(from=0, to=4*pi, length=200000) y <- sin(t) postscript(file="o.ps") plot(t, y, type="l") dev.off() If I view the postscript file o.ps in "gv", it takes many seconds before eventually
2001 Feb 17
4
Comments on R-1.2.1 builds (PR#851)
The R-1.2.1 builds have gone fairly smoothly on most of my UNIX architectures, but there were many warnings reported by the picky SGI compiler that could be eliminated in future releases. Generally, I have found the SGI compilers very helpful in ferreting out portability problems, unused and/or obsolete variables, unexpected datatype coercions, etc., and they compile faster than any other