[Rd] fonts in postscript device
I humbly suggest adding the fonts argument to the list of arguments recognized and processed by ps.options. Here is my argument: Currently, in Sweave it seems to be impossible to use multiple font families in <> code chunks without additional moderately inconvenient coding. The problem is that it is possible to use par(family="xxx") in postscript and pdf devices (which are the devices used by Sweave), but the fonts used in par statements also have to be included in the fonts argument of the postscript or pdf device when the device is opened. In normal mode, Sweave opens the device all by itself, therefore in this mode it seems not possible to change the fonts used by the postscript or pdf device. Instead, one has to explicitly open the device in one's own code chunk. That is possible, but then one has to manually take care of including the generated postscript and/or pdf files also. The easiest solution would be that ps.options accepts the fonts parameter, which it currently does not. That way, one could set the fonts available by default when Sweave uses the postscript device. -- Erich Neuwirth, Didactic Center for Computer Science University of Vienna Visit our SunSITE at http://sunsite.univie.ac.at Phone: +43-1-4277-39464 Fax: +43-1-4277-9394 __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] proposal for lower.tri and upper.tri value argument
I propose that a 'value' argument be added to
'lower.tri' and 'upper.tri'. This is analogous to
the 'value' argument of 'grep'.
Something like the following should work:
> upper.tri
function (x, diag = FALSE, value = FALSE)
{
x <- as.matrix(x)
if (diag)
ans <- row(x) <= col(x)
else ans <- row(x) < col(x)
if(value) x[ans] else ans
}
Patrick Burns
[EMAIL PROTECTED]
+44 (0)20 8525 0696
http://www.burns-stat.com
(home of S Poetry and "A Guide for the Unwilling S User")
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] dev.copy()
Hello, anybody knows dev.copy() usage? I'm developing a GUI for R, and at some time when I have a plot, I want to save it as a pdf. dev.copy() is , I think, what I need as well as open a pdf() device. I have read lot of times help(dev.dopy) but It's a little difficult to understand :S Any idea? -- Victor Llorens Vilella [[alternative HTML version deleted]] __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] read.table produces extra rows when file contains extra columns on (PR#9128)
Reading the following delimited file with read.csv() or read.table()
file1:
X,Y
1,2
2,4
3,6
4,8
5,10,,
6,12
produces a data.frame with 7 rows instead of 6 because the two extra values on
line 6 of the file
are pushed into a new row of the data.frame. In other words, the extra columns
on line 6 are
interpreted as a second case on the same line. This contradicts the help
?read.table which states
that cases correspond to lines.
A desirable behaviour might be to ignore the extra columns with a warning. It
would be nice
though to be consistent with the behaviour reading the shorter file
file2:
X,Y
1,2
2,4,,
3,6
which currently produces an error.
Gordon
> read.csv("file1.csv")
X Y
1 1 2
2 2 4
3 3 6
4 4 8
5 5 10
6 NA NA
7 6 12
> read.csv("file2.csv")
Error in read.table(file = file, header = header, sep = sep, quote = quote, :
more columns than column names
> sessionInfo()
Version 2.3.1 (2006-06-01)
i386-pc-mingw32
attached base packages:
[1] "methods" "stats" "graphics" "grDevices" "utils" "datasets"
"base"
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
