similar to: 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 =

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,

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

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

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

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

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

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

I?m preparing a package (fastR) for submission to CRAN, but the vignette index keeps going AWOL, or at least R CMD check ?as-cran thinks so. I?ve tried several things and gave myself the weekend to think of other things, but I can?t figure it out. Perhaps someone on the list can lend a hand. Here?s one example situation, where I build the index.html file myself and put it in inst/doc/index.html

Dear all, I'm trying to write a post_processor() for a custom rmarkdown format. The goal of the post_processor() is to modify the latex file before it is compiled. For some reason the post_processor() is not run. The post_processor() does work when I run it manually on the tex file. Any suggestions on what I'm doing wrong? Below is the relevant snippet of the code. The full code is

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. > >

Dear Duncan, Thanks for chiming in. Could you explain how you set debug() on post_processor()? I've tried adding debug(post_processor) to rsos_article() or adding debug(post_processor) when after post_processor was defined in the debugger. Neither work for me. All supporting files are available within the package. The code below should be reproducible on your machine.

On 06/09/2017 5:41 AM, Thierry Onkelinx wrote: > Dear all, > > I'm trying to write a post_processor() for a custom rmarkdown format. The > goal of the post_processor() is to modify the latex file before it is > compiled. For some reason the post_processor() is not run. The > post_processor() does work when I run it manually on the tex file. > > Any suggestions on what

On 07/09/2017 2:04 PM, Duncan Murdoch wrote: > On 07/09/2017 10:11 AM, Thierry Onkelinx wrote: >> Dear Duncan, >> >> Thanks for chiming in. Could you explain how you set debug() on >> post_processor()? I've tried adding debug(post_processor) to >> rsos_article() or adding debug(post_processor) when after post_processor >> was defined in the debugger.

Are you sure that you want to read in the output_file in text <- readLines(output_file, warn = FALSE)? best regards, Heinz Thierry Onkelinx wrote/hat geschrieben on/am 06.09.2017 11:41: > Dear all, > > I'm trying to write a post_processor() for a custom rmarkdown format. The > goal of the post_processor() is to modify the latex file before it is > compiled. For some

On 5/3/16 11:29 AM, Thierry Onkelinx wrote: > Dear Mick, > > Note that both knitr and rmarkdown are listed under Suggests: both are > required to compile the vignette. Installing rmarkdown should solve > the problem. If not, please provide more information. OS, R version, > digest version, ... > > This is occurring in the context of an automated testing environment that

On 07/09/2017 10:11 AM, Thierry Onkelinx wrote: > Dear Duncan, > > Thanks for chiming in. Could you explain how you set debug() on > post_processor()? I've tried adding debug(post_processor) to > rsos_article() or adding debug(post_processor) when after post_processor > was defined in the debugger. Neither work for me. Not working for me either right now for some reason

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?,

A package uses VignetteEngine: knitr; the package itself does not Suggests: knitr, but it Suggests: BiocStyle which in turn Suggests: knitr. Nonetheless, R CMD check fails indicating that a package required for checking is not declared. Is it really the intention that the original package duplicate Suggests: knitr? This is only with a recent R. In detail, with $ Rdev --version|head -3 R Under

Dear R-devs, Scenario: When checking a package via `R CMD check package_tar.ball`, required / suggested packages may be missing. R subsequently returns a list of packages that are missing (delimited by spaces). Example: ``` R CMD check glmSparseNet_0.99.13.tar.gz * using log directory '/home/ubuntu/Bioconductor/glmSparseNet.Rcheck' * using R Under development (unstable) (2018-06-06