Skip to content

Commit

Permalink
Explain why RTF is special
Browse files Browse the repository at this point in the history
  • Loading branch information
jennybc committed Jul 24, 2018
1 parent 96df3c1 commit 1142582
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion docs/articles/articles/rtf.html

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion vignettes/articles/rtf.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ Here is the highlight call implied by the default behaviour of `reprex(..., venu
highlight foo_reprex.R --out-format rtf --no-trailing-nl --style darkbone --font 'Courier Regular' --font-size 50 > foo_reprex.rtf
```

It would be preferable to use something like [highlight package](https://cran.r-project.org/web/packages/highlight/index.html) at some point in the future, but we will experiment with this in the meantime.
It would be preferable to use something like the [highlight package](https://cran.r-project.org/web/packages/highlight/index.html) at some point in the future, but let us experiment with this hack in the meantime. Why is RTF special? Although Pandoc can produce RTF and, therefore, so can `rmarkdown::render()` and `reprex::reprex()`, Pandoc's syntax highlighting is unavailable for RTF output. For now, we've got to get the functionality from somewhere else.

## Basic usage

Expand Down

0 comments on commit 1142582

Please sign in to comment.