similar to: missing permissions in reference manual copyright page (PR#3528)

Brian, Thanks for doing this. As the primary author, could I have a desk copy, please? Bill Venables. Bill Venables, CMIS, CSIRO Marine Laboratories, PO Box 120, Cleveland, Qld. 4163 AUSTRALIA Phone: +61 7 3826 7251 Fax: +61 7 3826 7304 Mobile: +61 419 634 642 <mailto: Bill.Venables at csiro.au> http://www.cmis.csiro.au/bill.venables/ -----Original Message----- From: Brian

Hi, Below I've flagged some sentences in the R documentation (from cvs) which are garbled in some way. If anyone can clarify what these sentences should say I'd be grateful. The problems were picked up as part of the proof-reading of the R manuals by Ciaran O'Riordan. After looking at the text neither of us could figure out what the documentation was meant to say. -- Brian Gough

Hi, This message is to let the R developers know that the pdfs for the first two volumes of the printed edition of R reference manual are available at, http://www.network-theory.co.uk/R/base/vol1.pdf http://www.network-theory.co.uk/R/base/vol2.pdf I've divided the manual into "core commands" of the base package (control flow, and related programming commands, etc) in Volume 1

The patch below attempts to correct some unclear sentences in the R documentation. In the case of coplot.Rd it wasn't clear whether "shingle" bar had a special meaning or was a typo for "single". I've just put a comment in that case. regards -- Brian Gough Network Theory Ltd -- Publishing Free Software Manuals 15 Royal Park Bristol BS8 3AL United Kingdom Tel: +44

Here are some patches to expand some of the examples in R-intro.texi. -- Brian Gough Network Theory Ltd, Publishing the R Reference Manuals --- http://www.network-theory.co.uk/R/ --- R-intro.texi~ Tue Aug 24 11:21:37 2004 +++ R-intro.texi Tue Aug 24 11:21:37 2004 @@ -6288,6 +6288,21 @@ use @example +> help(package = "@var{name}") +@end example + +A complete list of the

Hello, This message is to announce that the "R Reference Manual" is now available in book form. There are two volumes, which cover all the commands in the base package. They are available for order from all major bookstores. "The R Reference Manual - Base Package" (2 volumes) Hardback (6"x9"), 1440 pages total Retail Price $69.95 per volume

Hello, This message is to announce that the "R Reference Manual" is now available in book form. There are two volumes, which cover all the commands in the base package. They are available for order from all major bookstores. "The R Reference Manual - Base Package" (2 volumes) Hardback (6"x9"), 1440 pages total Retail Price $69.95 per volume

the problem is a little hard to explain; the .Rnw files (below) probably do a better job, but here goes ... Sweave doesn't like it when i size a graphical device in a code chunk using either, e.g.: windows(width=20, height=5) in Windows, or, e.g. x11(width=20, height=5) under X, when i then plot something in said device and try to include this graphical output in the resulting

Dear useRs, I'm writing regular survey reports using Sweave. Each report has several sections along the lines of: \section*{Disease X} <<MapX,fig=TRUE,echo=FALSE>>= image(vectorx,vectory,matrixz) @ Notes with or without Sexpr{a}. \vfill \pagebreak \section*{Disease Y} <<MapY,fig=TRUE,echo=FALSE>>= ...etc. Often one or more of the diseases is not observed (all

Hello, Here are some patches for R-intro.texi, to correct various typos, missing words, and minor inconsistencies in formatting. Each patch is preceeded by its corresponding 'wdiff' output to make it easier to see which words have changed. -- Brian Gough Network Theory Ltd, Publishing the R Reference Manuals --- http://www.network-theory.co.uk/R/

I think there are some missing words in "R Internals"'s description of the P_ macro. It currently has "A macro as a wrapper for ngettext", which I think ought to be something like "The macro P_ may be used as a wrapper for ngettext". The following patch also makes the 2 alternate definitions of P_ have the same argument names, StringS and StringP. Expanding the

I have constructed the function mml2 (below) based on the likelihood function described in the minimal latex I have pasted below for anyone who wants to look at it. This function finds parameter estimates for a basic Rasch (IRT) model. Using the function without the gradient, using either nlminb or optim returns the correct parameter estimates and, in the case of optim, the correct standard

Attached is a patch for R-exts.texi against r72880. Here are some of the changes I made: - Fix a broken link: https://developer.apple.com/library/mac/#documentation/DeveloperTools/Conceptual/InstrumentsUserGuide/Introduction/Introduction.html -> https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/InstrumentsUserGuide/index.html - Changed a few http

Dear expeRts, What's a 'good' (nice-looking, easy-to-read) setup for the LaTeX package 'listings' to display R code? The two versions below are partly inspired by the settings of the package SweaveListingUtils and http://r.789695.n4.nabble.com/R-How-to-format-R-code-in-LaTex-documents-td816055.html Any suggestions, comments, or improvements are welcome. Cheers, Marius ###

Dear R-help, Can some one tell me what could be the problem? I downloaded the R-1.7.1 source and try to compile it on WinXP. "make", "make bitmapdll", "make tcl", "make recommended" all ran w/o problem. However, when I ran "make docs", it failed at creating refman.pdf, with no apparent error that I could see. I have attached the log file

Dear List: I am working to understand some differences between the results of the svymean() function in the survey package and from code I have written myself. The results from svymean() also agree with results I get from SAS proc surveymeans, so, this suggests I am misunderstanding something. I am never comfortable with "I did what the software" does mentality, so I am working to

After configure, make and make check on a linux Suse 7.3 box, I run make dvi and make info with no problems but get a lot of garbage to my screen during make pdf. Is this normal? Is there a bug in this part of the installation? This is part of what I get on the screen: humboldt:/usr/local/R-patched # make pdf make[1]: Entering directory `/usr/local/R-patched/doc' make[2]: Entering

Hello. I am in a habit of compiling daily snapshots of R-devel and R-patched on my Windows XP workstation. I have cygwin environment with up-to-date RTools and MiKTeX. I run cygwin and MiKTeX upadaters pretty often (every couple of days) so both of them are reasonably current. Recently I noticed a small annoyance when compiling R-dvel. It started happening right after I updated to the new

Hello there, I have a habit of compiling R-patched and R-devel every few days. Recently, I noticed the following problem: I downloaded both versions with Revision: 40421, Last Changed Date: 2007-01-09. R-patched compiles with no problem. R-devel compiles fine but when it starts to make PDF documentation it generates the following (tail of the "make distribution" output): ! pdfTeX

Just one minor point about building bitmap.dll on Windows in doc/manual/R-admin.texi: In lines 601-605: @item You need @code{libpng} and @code{jpeg} sources (available, e.g., from @url{http://www.libpng.org}, @url{ftp://ftp.uu.net/graphics/}[png,jpeg]. You will need files @file{libpng-1.2.8.tar.gz} and @file{jpegsrc.v6b.tar.gz} or later. and lines 699-707: The file