similar to: Rd2dvi problem.

Hi, I run into a problem with "R CMD Rd2dvi" command: it gives me "File `Rd.sty' not found" error (See the output message on the bottom). I get the same error when running "RCMD check". My system is: Windows 2000, R version 2.0.1, MiKTeX version 2.4. I do have a Rd.sty file in R_HOME/share/texm directory. I looked through newsgroups for any related discussions

Is there any way of getting just the LaTex output which R CMD Rd2dvi generates on the way to produces a .dvi file, which could then be incoorporated into another document? Thanks, Jonathan -- Dr. Jonathan Myles e-mail:jonathan.myles at mrc-bsu.cam.ac.uk MRC Biostatistics Unit Tel. 01223 330372 Institute of Public Health FAX 01223 330388 University Forvie Site

Hi, I run R 2.5.1 on Mac OS 10.4.10 and fail to build a package manual. Below is the transcript. The problem is a "pdflatex: command not found" error but I think that I have a fully working latex install (installed with iInstaller) as I use TeXShop with no problem. Could someone help? Jean-Pierre -----------------------------------------------------------------------------

I'm trying to use R CMD Rd2dvi and I end up at a Latex (I think) command prompt. What's missing or what am I suppose to do? Paul Gilbert _______ paul at breman:/apps/dse-versions/2000.6/dse#R CMD Rd2dvi syskern This is TeX, Version 3.14159 (Web2C 7.3) (Rd2.tex LaTeX2e <1998/12/01> Babel <v3.6k> and hyphenation patterns for american, french, german, ngerman, nohyphenation,

Is this a bug-- ------------------------------------------------------------------------------- <234>% R CMD Rd2dvi base.Rd Converting Rd files to LaTeX ... base.Rd Can't use an undefined value as filehandle reference at /opt/R-2.5.1/lib/R/share/perl/R/Rdconv.pm line 78. ENCS is Creating dvi output from LaTeX ... Saving output to 'base.dvi' ... cp: cannot access

Hello everybody I'm am trying to build a pdf out of the Rd files that i wrote for a package, so that I can attach it to my thesis. if i Run Rd2pdf (or Rd2dvi) I get this error massage: Hmm ... looks like a package Converting Rd files to LaTeX . Creating pdf output from LaTeX ... Error in texi2dvi("Rd2.tex", pdf = (out_ext == "pdf"), quiet = FALSE, : Running

Hi all, I'm writing a vignette for my package, and I would like to include some of the package help files in there as well. Is there an easy way of doing so? I tried using R CMD Rdconv to generate latex files from .Rd files but I am not sure how to include these into a .Rnw file (ie the vignette source). The resulting file from Rdconv do not readily compile using latex ... The other option I

When I create a manual for a package that I create and use locally, e.g. via R CMD Rd2dvi --pdf foo where ``foo'' is the name of the directory containing the source for the package (also named ``foo'') the resulting manual does not appear to have an index. The package.pdf files appearing on CRAN all seem to have indices. What must I do to get an index appended to the

hi, can anyone confirm the following problem? when i do dos> rcmd rd2dvi --pdf my-package-name i get dos> Can't open perl script "c:\PROGRA~1\r\rw1091/bin/rd2dvi": No such file or directory might the problem be in (double back slashes rather than forward slashes) R-1.9.1\src\gnuwin32\front-ends\rcmdfn.c(251): strcat(cmd, RHome); strcat(cmd, "/bin/Rd2dvi.sh");

Dear all, I writing my first package and everything seems to work (at least up to now) However when I try to build documentation (.dvi or .pdf), using Rcmd Rd2dvi.sh --pdf mypack.Rd I get a mypack.pdf whose title is "R documentation of mypack.Rd" instead of "The mypack package" as it should be, is it right? Also Version, Title, ....License, namely info from the DESCRIPTION

> The command Rd2pdf was rather useful for opening a package's manual > when you don't have access to the Internet (by using latex to pdf > conversion). However the way the function seems to operate changed at > version 2.14 of R. The noted changes listed on CRAN for this function > are as follows (which doesn't seem like it would affect my usage as > below): >

Hi I'm having difficulty following the advice in section 2.7 of R-exts. In one of my packages, there is a function called mobius(). I want to refer to it in the Rd file as the M??bius function, and to illustrate the M??bius inversion formula (just to be explicit: this is "Mobius" but with two dots over the second letter). R-exts section 2.7 gives \enc{J??reskog}{Joreskog}

Full_Name: Ole Christensen Version: 1.3.0 OS: Solaris Submission from: (NULL) (130.225.48.2) I have discovered a problem with script Rd2dvi for R-1.3.0 on our Solaris machines. When writing R CMD Rd2dvi Name_of_Package, then things go wrong with the conversion to Latex of the DESCRIPTION file in the package. Having discussed the problem with our system administrator, he constructed a script

I am trying to compose some documentation for a package I hope to release soon. However when I do the following: R CMD Rd2dvi --pdf mypackage.Rd I get two mainly blank pages prepended to the top of the document - the only text on either (at the top of the first page) is as follows: hyperindex,colorlinks,pagebackref,linktocpage,plainpages=false,linkcolor=Blue

Hi.... I am assembling an R package (under Windows XP, R v.2.3) and have a very basic question. Running R CMD build does not generate a pdf. R CMD check generates a .dvi, but I cannot figure out how to automatically create the pdf. I thought from reading the "writing r extensions' manual that R CMD build was supposed to generate the pdf. I am having no success using various

I construct a pdf package manual in Windows 7 using R CMD Rd2dvi --pdf --no-preview [packagename] Page numbers are listed correctly under 'R topics documented' at the front, but incorrectly (offset by -2 pages) in the Index at the back. Following the hyperlinked page numbers in the Index takes you to the wrong page. 2 pages happens to be the length of the package overview man page inserted

Hi R-devels, would it be possible to enhance either promptPackage() or the default indexing mechanism for packages so that -- if it exists -- (the contents of) file <pkgname>-package.Rd is sorted first in * the .dvi / .pdf documentation file * the .chm documentation file * the package 00index.html documentation file ? So far I found the following "hand-made" solution

First of all, thanks to those who've set up R to work so smoothly with Miktex-- even a total Latex bunny like me got it to work instantly, so that for the first time I'm able to run my Rd files through the Latex side of RCMD CHECK. Now the question/buglet. One of my Rd files contains the following: \code{mlazy( <<objname1>>, <<objname2>>, <<etc>>)}

Dear list, R CMD check on my updated package now generated the following error: "LaTeX errors when creating DVI version. This typically indicates Rd problems." But the Rd files (and everything else) were checked as "OK" (I removed the problem about which I asked the list some hours ago, but answers are still appreciated because I rather created a rough workaround than

I have noted that the later versions of Rcmd check cleans out the directory pkg.Rcheck so that only package-manual.log and package-manual.pdf are left. Formerly the package-manual.tex was around too --- very handy for various purposes. Is there a way to generate the .tex - version of the manual for a package? br. Bendix ______________________________________________ Bendix Carstensen Senior