[R-pkg-devel] checking PDF version of manual

[Patrick Giraudoux]

Le 31/01/2016 15:22, Patrick Giraudoux a écrit :
> Le 31/01/2016 14:36, Uwe Ligges a écrit :
>> Eitehr the file is no longer there or corrupted, or the database that 
>> know about the file got corrupted.
>>
>> For the former, re-instal the package, fr the latter, just go to 
>> MikTeX settings and run "refresh FNDB" and "Update Formats".
>>
>> You can also upload the package to the winbuilder service to verify - 
>> it also uses MikTeX 2.9 ...
>>
>>
>> Best,
>> Uwe Ligges
>>
>
> Thanks. Meanwhile I have already reinstalled MikTEX 2.9,  run "refresh 
> FNDB" and "Update Formats", and still get a similar error.... There 
> should be something with MikTEX since the package was submitted to 
> CRAN and went through successfully (Kurt Hornik).
>
> A bit beyond my understanding...
>
>
> U:\Users\pgiraudo2\Documents\R\pgir_arch\pgirmess_arch\On work>rcmd 
> Rd2pdf pgirmess
> Hmm ... looks like a package
> Converting Rd files to LaTeX .....
> Creating pdf output from LaTeX ...
> Warning: running command 
> '"C:\PROGRA~2\MIKTEX~1.9\miktex\bin\texify.exe"  --pdf
> "Rd2.tex" --max-iterations=20 -I 
> "C:/PROGRA~1/R/R-32~1.3/share/texmf/tex/latex"
> -I "C:/PROGRA~1/R/R-32~1.3/share/texmf/bibtex/bst"' had status 1
> Error : running 'texi2dvi' on 'Rd2.tex' failed
>
> LaTeX errors:
> !pdfTeX error: pdflatex.EXE (file ts1-zi4r): Font ts1-zi4r at 540 not 
> found
>  ==> Fatal error occurred, no output PDF file produced!
>
> Warning: running command 
> '"C:\PROGRA~2\MIKTEX~1.9\miktex\bin\texify.exe"  --pdf
> "Rd2.tex" --max-iterations=20 -I 
> "C:/PROGRA~1/R/R-32~1.3/share/texmf/tex/latex"
> -I "C:/PROGRA~1/R/R-32~1.3/share/texmf/bibtex/bst"' had status 1
> Error : running 'texi2dvi' on 'Rd2.tex' failed
>
> LaTeX errors:
> !pdfTeX error: pdflatex.EXE (file ts1-zi4r): Font ts1-zi4r at 540 not 
> found
>  ==> Fatal error occurred, no output PDF file produced!
>
> Error in running tools::texi2pdf()
>

I am closer to the solution. Rd2pdf (and MikTeX) works fine when I am 
running it as administrator. Does not work (with subsequent errors) when 
I run it on my usual user account (with limited rights). Now I remember 
that 2 weeks ago our computer manager has created a new user account on 
my labtop... Suspect some access rights may have been modified by him... 
Will see him tomorow...

Best,

Patrick