This is only a suggestion for improvement. It could be useful to have some method of converting existing .md files to .Rmd

Rationale: anyone who made .md files without .Rmd and wants to convert them to .Rmd will have a lot of copy/pasting ahead of them. Such a method could spare them that labour.

Although [a perfect conversion may not be

This is not an issue, but a recommendation.

I would like to suggest that in the docs available in the Rmarkdown book you include two examples in chapter 15 (parameterized reports):

• passing parameters as raw markdown text for the parameterized reports.
• setting the title using a parameter

This information is available in other parts of the book,

The following snippets included in a test.jmd with the build command. Note I'm using """ to indicate code blocks as Github intercepts the markdown.

weave(papersdir("test.jmd"), 
  out_path=:doc,
  doctype = "md2pdf"
  )

demonstrate the various ways Figures are not working.

"""julia
using Plots

plot(1:10)
"""

This works, as expected. The plot takes up

When opening a weaved document with the console open, you can observe that the browser attempts to load a font for KaTeX. The weaver seems to be using relative URL's for these fonts, but they aren't anywhere to be found in this repository.

These references should be changed to use the fonts hosted by Cloudflare at https://cdnjs.com/libraries/KaTeX. With that being said, I'm wondering if that's

Interested in the possibilities of narrative schemas with litvis but found insuficient documentation to get started. Can you link to additional resources?

Not sure if this is a bug but maybe is worth reporting as it may have unintended consequences.

mdf <- data.frame(a=c(1,2,3),b=letters[1:3])
pander(mdf)

# However if mdf row.names is non sequential then the row.names are printed
attributes(mdf)$row.names <- as.integer(c(1,5,8))
pander(mdf)

This is more of a request / question. I'd like to know if this added feature is something that could be incorporated into Literate, or if it's better for Documenter, or just create a separate package.

The gist of the feature (pages_array) is that the nes

So far lit always assumes your intention is to build the Markdown source into executable code, but there are also cases where isolating the documentation is useful – publishing a user manual on the web site for a project, for example. Such efforts are very much in line with the goals of lit and literate program, though the "last mile" problem of actually exposing the documentation is obviously b

This should be quite easy. There is not much to check:

• generate docs and see that the files exist: both transformed sources and md-files
• check that old files are cleaned up
• check that setting locations map works as expected

sbt docs on scripted testing