Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Switch Rcpp Vignette Engine away from highlight #604
Switching away from this engine to either
In each vignette, the following must be changed:
Switch each code chunk to use knitr options:
In each vignette, YML matter must be added:
In addition, code segments must be switched over to using the GFM code ticked fence design.
However, this involves more work potentially porting over LaTeX syntax to use native RMarkdown to take full advantage of the format.
Probably going to go down the RMarkdown route.
The main issue is the custom syntax in a few files (e.g.
Outside of that, using parameterized reports the date and version information can easily be placed within the document.
Sorry but I am really no fan of the font.
I happen like the old vignettes.
I am with you in principle as these days I do write new content in markdown (even if that becomes latex and pdf, nice current example with a paper draft) but I am not that in practice I have a lot of energy for convergence exercises. We'll see.
We could always create a brand new R Markdown template which uses the old vigette's LaTeX as it's starting point.…
On Sun, Jan 1, 2017 at 1:26 AM, Dirk Eddelbuettel ***@***.***> wrote: Sorry but I am really no fan of the font. I happen like the old vignettes. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#604 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGXx5I7tqrdaBPo8mPf0tnjlNRlz1qwks5rN0cdgaJpZM4LDfQu> .
And we could start list with a set of features we want.
ie if someone insists on doing all this work (hi, @coatless) the outcome should be something professional and markedly better than what we have right now. Think "10x argument" to induce switching to something new. Don't take ten too literally. My main point is to take a switch worthwhile it has to offer something.
And in aggregate I still think this makes it a lower-priority item.
I agree that the switch is a lower priority item, however, it is an item that is important for the primary reason that it enables easier contributions to documentation (c.f. #433 rendering issues and required add-on script). Moreover, as the API docs (#602) come online, there is the new dependency of
With this being said, the objective behind showing progress was to indicate a valid path was found and the results weren't too disappointing. In the interim, new concrete targets were introduced that provide a guiding force for whether a switch should occur.
Touching on these points briefly, we have:
Regarding the conversion process, the majority of the work once the template is concocted is to run:
# in shell pandoc Rcpp-vignette.tex -o Rcpp-vignette.md