Hi,
I am preparing a package where I would like to use UTF characters in .Rd
files. When the LaTeX comes to play, I got well known errors e.g.:
! Package inputenc Error: Unicode character ∂ (U+2202)
(inputenc) not set up for use with LaTeX.
It is coherent with what is said on th
utf8x is deprecated
https://tex.stackexchange.com/questions/13067/utf8x-vs-utf8-inputenc#13070
On Tue, 18 Jun 2019 at 7:52 pm, Serguei Sokol
wrote:
> Hi,
>
> I am preparing a package where I would like to use UTF characters in .Rd
> files. When the LaTeX comes to play, I got well known errors
> Hugh Parsonage
> on Tue, 18 Jun 2019 20:03:41 +1000 writes:
> utf8x is deprecated
> https://tex.stackexchange.com/questions/13067/utf8x-vs-utf8-inputenc#13070
Hmm... interestingly, I've tried quite a few versions of the
above which started in 2011, but had been updated in A
Hello,
I'm having a really strange problem that I cannot reproduce locally (Ubuntu
bionic) or on Rhub. I've run into an issue where the R package manual is
failing only on this platform with ancient LaTeX runes that I struggle to
decipher [0]
> * checking PDF version of manual ... WARNING
> LaTeX
You can build the PDF manual locally with
R CMD Rd2pdf --no-clean .
and then look at line 186 in the poppr-manual.tex file to see where
there error is coming from.
You can also try R-hub's windows builder, to see if you can reproduce it there.
Gabor
On Tue, Jun 18, 2019 at 3:37 PM Zhian Kamvar
Unfortunately this error is caused by a hyperlink straddling a page, so
it’s difficult to solve uniformly.
The LaTeX error message provides a clue as to where the hyperlink might be
(near an \item near a \code) but no exact location.
My advice would be to look where you have hyperlinks (including
Since April 2018 'utf8' is the default input encoding in LaTeX, see
http://anorien.csc.warwick.ac.uk/mirrors/CTAN/macros/latex/doc/ltnews.pdf and
they added some symbols in December.
Georgi Boshnakov
-Original Message-
From: R-package-devel [mailto:r-package-devel-boun...@r-projec
Thank you for the the insights, Gabor and Hugh! Line 186 happens to be a
\begin{itemize} in the package documentation section (which is chock-full
of links), I didn't change that, but I did expand the DESCRIPTION, so I
guess it makes sense that one of those links have slid down and gotten
stuck bet
For the curious, an update from Uwe Ligges:
Kurt Hornik found:
>
> <
> https://tex.stackexchange.com/questions/1522/pdfendlink-ended-up-in-different-nesting-level-than-pdfstartlink
> >
>
> and you shoudl be able to reproduce via
>
>R_PAPERSIZE=a4 R CMD Rd2pdf /path/to/poppr
>
> Suggestion:
>
>
