similar to: minor oddity in pdf() help page

Hi, I am generating a large number of graphs with pdf() and incorporating them in pdf document using pdflatex. According to the pdf() help: 'pdf' writes uncompressed PDF. It is primarily intended for producing PDF graphics for inclusion in other documents, and PDF-includers such as 'pdftex' are usually able to handle .compression. But pdflatex incorporates the R

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

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'm having a problem rebuilding a package, new to me in R 2.15.0 (Linux) It hits all that contain the line \usepackage[pdftex]{graphics} and leads to the following when running R CMD check on the directory. (I do this often; a final run on the tar.gz file will happen before submission.) Since I float and resize my figures, removing the line is fatal in other ways.

I'd like to make MikTeX the default TeX package in 2.2.0, but we still need to let people use other packages. The problem is that MikTeX wants a command line option --include-directory $R_HOME/share/texmf, while other packages specify includes via environment variables, and barf when they see the unexpected option. The choice should be controlled by the user's settings in the MkRules

Dear Gurus, R 2.11.1 on Windows XP. This is a problem in interaction between R and pdftex. I need to generate a plot with both open and filled circles. It is simple enough, using pch=1 and pch=16. The R pdf graphics output is going into pdftex 1.40.10 (MikTeX 2.8). The R pdf is correct when viewed in other viewers. However, pdftex fills the open circles. I can work around this problem by

I am having trouble converting the output from Sweave into a valid PDF file. I have created a simple .Rnw file which will become a full vignette at some point, but during the intermediate testing, I got errors from texi2dvi. This is what I have done. 0) Using a Windows Xp system 1) Created a file called GeneSpring.Rnw 2) Convert this to Tex using Sweave("GeneSpring.Rnw") from within R

Dear all, I am trying to compile Ralpha on my computer (OS = Debian). SVN Revision is: Revision: 42843 Last Changed Date: 2007-09-14 ./configure returns : ---------------------------------------------------- stephane at pcdray:~/Rdev/R-alpha$ ./configure checking build system type... i686-pc-linux-gnulibc1 checking host system type... i686-pc-linux-gnulibc1 loading site script

Dear list, I am trying to produce a pdf manual using Rtools (version 3.1.0.1936) on Windows 8 (64-bit). I am also aware of the inconsolata issue posted in the forum (https://stat.ethz.ch/pipermail/r-devel/2013-June/066850.html), and then I have installed the patched version of R-3.0.1. However I still have some errors with the following message: R CMD Rd2pdf mypack Hmm ... looks like a package

Dear all, I am getting an R CMD check warning about the PDF manual. I am having a hard time finding out what is wrong, here is the log of the Rd2pdf call. The full check (and other) log is at https://api.travis-ci.org/jobs/46373922/log.txt?deansi=true if anybody is interested, and the package itself is here: https://github.com/metacran/r-builder/tree/bintex/rbuildertest Thanks, Best, Gabor

I am trying to compile the R-dev sources on WinXP using mingw 3.1.0-1 and fpTeX 0.7. In the past I have been able to build the sources fine but now I receive an error in the process that I havent seen reported on the list before. Everything works fine until I get to 'make docs'. I now get the message below while building the R-admin manual (refman.pdf builds fine) and the make process

Hello! I use R 2.8.1 under Debian GNU/Linux. I've run into a problem including R pdf figures into LaTeX document. To reproduce: 1) Execute the following minimal R script: pdf('fig.pdf', family = 'URWTimes', width = 5, height = 5) plot(rnorm(10), main = '????', xlab = '????????', ylab = '????????') dev.off() embedFonts('fig.pdf') 2) Open

Hi all I am trying to build an R package, which I have successfully done many times before, but have an error I cannot trace. I hope someone can help me. Here's is some edited output (full output below if it is useful): pdunn2 at PDunnUbuntu:~/DSdata$ R CMD build GLMsData * checking for file 'GLMsData/DESCRIPTION' ... OK * preparing 'GLMsData': * checking DESCRIPTION

Hello, I can't seem to save (or find the default location) when I use the Window Graphic Device's pull down menu. It does not seem to save to the directory I have set using "setwd(...)". How do I make the pull down menu's work? What is the best format to save R graphics for inclusion into a LaTeX documents? I will use PdfTex, or LaTeX -> PS -> PsToPdf to generate the

I ran "yum upgrade" early yesterday from a remote ssh login, but upon looking at the set of packages I decided to wait until I could sit at the console to reboot. So I declined to proceed with the upgrade when prompted. Later when I ran "yum ugrade" again, it found no packages to update. After some poking around checking the mirrors, running "yum clean headers",

Dear useRs-- I have been using Sweave with miktex for years, but on a new install on Windows XP, miktex seems to be hung up on single quotes. See example below. Digging through stackexchange, I found using \usepackage[noae]{Sweave} in the tex file solved the problem. My questions are: --Why would this happen? I have the ae package installed. --If inserting [noae] is the solution, how do I

Hi, Due to a change in Rd.sty a few days ago (https://github.com/wch/r-source/commit/620eb9a#diff-3bf3d821c6faae50cd6ec931f6f63296L272), the default installation of TeXLive 2009 or 2012 no longer works when building Rd to PDF. The error log is like this: =============== Converting Rd files to LaTeX ..... Creating pdf output from LaTeX ... Error in texi2dvi(file = file, pdf = TRUE, clean = clean,

On 05/29/2018 04:53 PM, Dirk Eddelbuettel wrote: > I noticed it with a local, not-public package -- but it appears to apply with > any source package. I replicated with pkgKitten straight off CRAN and after > checking that it has a six page manual there. I'm having trouble reproducing this one. In my fresh CentOS 7 VM, I can pull the pkgKitten source down, and run R CMD Rd2pdf

Tom, On 30 May 2018 at 11:34, Tom Callaway wrote: | On 05/29/2018 04:53 PM, Dirk Eddelbuettel wrote: | > I noticed it with a local, not-public package -- but it appears to apply with | > any source package. I replicated with pkgKitten straight off CRAN and after | > checking that it has a six page manual there. | | I'm having trouble reproducing this one. In my fresh CentOS 7 VM, I

dear R wizards--- I would like to do some book-on-demand printing at a popular printer named lulu, but lulu requires inclusion even of the basic postscript fonts. Interestingly, my book itself does not need the 14 base acrobat fonts, only the embedded R figures do. Of course, I really would like to get pdftex to embed the fonts, but how to do this is not obvious either. [This method seems