Displaying 20 results from an estimated 10000 matches similar to: "markdown vignette with the vignette command"
2014 Dec 09
2
UTF8 markdown vignette
Dear Duncan,
The UTF-8 characters aren't properly rendered in the pdf version of the vignette.
$?? ????? ?????? ?????? ????? ?? ?? is rendered as $????? ?????????? ???????????? ????? ?????? ? ???????? ????????
The same problem occurs when I use render("vignette.md", output_format = "mypackage::mystyle"), instead of render("vignette.md", output_format =
2014 Dec 09
2
UTF8 markdown vignette
Dear all,
I'm trying to use a Markdown vignette with UTF-8 encoding. It compiles well when knitting the vignette in RStudio, but it fails to recognize the UTF-8 settings when building the source package. Can someone point out what I'm doing wrong? I tried to put the relevant information below.
Best regards,
Thierry
Details:
Using 64-bit R 3.1.2 with encoding = "native.enc"
2014 Dec 09
4
UTF8 markdown vignette
A few things to clarify:
1. You do not necessarily have to keep the \usepackage{} line if you
use %\VignetteEncoding{UTF-8}, because Pandoc will use UTF-8 anyway in
its LaTeX template.
2. Perhaps the vignette engine in R has done something clever to
convert utf8 to UTF-8, but I'd recommend %\VignetteEncoding{UTF-8}
instead of %\VignetteEncoding{utf8} to make sure it is a valid
encoding name,
2014 Dec 09
3
UTF8 markdown vignette
On 09/12/2014, 4:38 PM, ONKELINX, Thierry wrote:
> Dear Yihui,
>
> I have created a reproducible example at https://github.com/ThierryO/utf8vignette
>
> The \usepackage{} line is needed, otherwise R CMD check --as-cran will give a warning.
> %\VignetteEncoding{UTF-8} did not solve the problem.
I've just taken a look at the sources, and that's only in R-devel, it
never
2014 Dec 09
0
UTF8 markdown vignette
On 09/12/2014 11:13 AM, Yihui Xie wrote:
> A few things to clarify:
>
> 1. You do not necessarily have to keep the \usepackage{} line if you
> use %\VignetteEncoding{UTF-8}, because Pandoc will use UTF-8 anyway in
> its LaTeX template.
>
> 2. Perhaps the vignette engine in R has done something clever to
> convert utf8 to UTF-8, but I'd recommend
2014 Dec 09
0
UTF8 markdown vignette
On 09/12/2014, 5:19 AM, ONKELINX, Thierry wrote:
> Dear Duncan,
>
> The UTF-8 characters aren't properly rendered in the pdf version of the vignette.
> $?? ????? ?????? ?????? ????? ?? ?? is rendered as $????? ?????????? ???????????? ????? ?????? ? ???????? ????????
That looks as though the UTF-8 characters are being interpreted as
Latin1 characters (or whatever your native
2014 Dec 09
0
UTF8 markdown vignette
Dear Yihui,
I have created a reproducible example at https://github.com/ThierryO/utf8vignette
The \usepackage{} line is needed, otherwise R CMD check --as-cran will give a warning.
%\VignetteEncoding{UTF-8} did not solve the problem.
I use rmarkdown_0.3.11
HTML vignette is not an option as the vignette demonstrates the use of a custom beamer output format.
Best regards,
Thierry
ir. Thierry
2014 Dec 09
0
UTF8 markdown vignette
On 09/12/2014, 4:48 AM, ONKELINX, Thierry wrote:
> Dear all,
>
> I'm trying to use a Markdown vignette with UTF-8 encoding. It compiles well when knitting the vignette in RStudio, but it fails to recognize the UTF-8 settings when building the source package. Can someone point out what I'm doing wrong? I tried to put the relevant information below.
You don't describe the
2016 May 03
2
vignette/knitr help
I need some help understanding a problem running the tests on the
'digest' package. Initially, I got the message that the 'knitr' package
was needed to run vignettes:
Running vignettes for package ?digest?
Error in loadVignetteBuilder(vigns$pkgdir) :
vignette builder 'knitr' not found
So I installed the knitr package and all its dependents (?mime?,
?stringi?,
2014 Dec 19
1
UTF8 markdown vignette
On 18/12/2014, 12:17 AM, Yihui Xie wrote:
> For the record, I saw a change had been made in R-devel:
> https://github.com/wch/r-source/commit/d53b098 (Thanks, Duncan)
> Meanwhile, I also made a change in knitr to assume UTF-8 unless R
> passes an encoding to the vignette engine:
> https://github.com/yihui/knitr/commit/23c6c8e2 Both will solve the
> original problem, but
2014 Dec 10
2
UTF8 markdown vignette
On 09/12/2014, 10:36 PM, Yihui Xie wrote:
> I took a look at the R source and I realized that the encoding was
> actually never passed to the vignette engine:
> https://github.com/wch/r-source/blob/e721ef5f4/src/library/tools/R/Vignettes.R#L507
> Apparently only the file and quiet arguments are passed to the
> vignette engine. Did I miss anything?
I think it's actually a little
2015 Oct 31
1
Example input data with example output using relative pathway in vignette of R package?
I'm putting together an R package. I would like to show example code in the
vignette, where example data files (included in the package) are used to
generate an (example) output file.
I read about using example data in Hadley Wickham's post (
http://r-pkgs.had.co.nz/data.html), and believe I should keep my example
data as raw data, as it must be parsed to generate the output.
So, I
2015 Oct 18
2
Linking to documentation from a vignette using markdown?
Hello:
What's the preferred way to link to package documentation from a
vignette using markdown?
My current draft includes
"[cumsum](https://stat.ethz.ch/R-manual/R-devel/library/base/html/cumsum.html)"
to link to the help page for cusum{base} and
"[KFAS](https://rweb.crmda.ku.edu/cran/web/packages/KFAS/KFAS.pdf)" to
link to the pdf documentation for
2013 Feb 11
1
Avoid re-building a vignette
I once knew the answer to this, but can't find where I found it.
Say I have a vignette that I don't want R to automatically rebuild, perhaps it uses some
data I can't share or takes too long to run or whatever. Say it is
mypackage/vignettes/charlie.Rnw
It can create the pdf from an R session that actually has the data, place that result in
inst/doc/charlie.pdf, then run
R
2015 Oct 19
1
Linking to documentation from a vignette using markdown?
Hi, Duncan:
On 10/18/2015 8:18 PM, Duncan Murdoch wrote:
> On 18/10/2015 5:51 PM, Spencer Graves wrote:
>> Hello:
>>
>>
>> What's the preferred way to link to package documentation from a
>> vignette using markdown?
>>
>>
>> My current draft includes
>>
2012 Sep 04
3
R, knitr y markdown . ¿Cómo insertar tabla de contenidos en documento markdown?
Hola, ¿qué tal?
Estoy haciendo un informe con R, knitr, y markdown y no sé cómo podría
añadirle una tabla de contenidos. O mejorar el aspecto del fichero
final en html.
¿Algún consejo?
Gracias.
2013 Jul 01
2
Error al correr archivo markdown
Si, ya habia hecho un archivo markdown y lo habia corrido hace unos cuantos
meses
El sistema es windows 7 y R version 3.0.1 (2013-05-16)
el mensaje es el siguiente: > require(knitr); knit('Quiz1Markdown.Rmd',
encoding='ISO8859-1');
Loading required package: knitr
Error in loadNamespace(i, c(lib.loc, .libPaths()), versionCheck = vI[[i]])
:
there is no package called
2017 Jan 13
2
input en markdown
Hola
¿Quizá por aquí?
https://github.com/yihui/knitr/issues/268
El 13 de enero de 2017, 12:26, Rubén Gómez Antolí <lobo en mucharuina.com>
escribió:
>
>
> El 13/01/17 a las 11:50, Antonio Maurandi López escribió:
> > Hola lista:
> >
> > Una duda rápida (espero).
> >
> > ¿Se puede hacer un "inlcude" o un "input" en markdown?
>
2011 Nov 18
2
cannot set the path to installed R packages when building a package vignette
Dear colleagues,
I am having issues trying to build a R package I recently wrote.
I am using R 2.14.0 and my package depends on another package called aod.
Running:
R CMD Sweave vignette.Rnw
is perfectly fine and the vignette compiles properly.
but when I use
R CMD build mypackage
to build the tar.gz I get the following error:
* installing the package to re-build vignettes
* creating
2018 Jul 09
2
Parametrized Vignettest in R packages
On 09/07/2018 3:24 PM, Witold E Wolski wrote:
> Dear Yihui,
>
> Thank you for the valuable questions.
>
> sample_analysis is a "tibble" while
> configuration is an "R6" class.
> But I also have parametrized reports where I pass R reference classes
> as arguments.
>
> This is the Rmd yaml params part corresponding to the error message.
>
>