You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, since downlit is intended to be used by other packages, it's difficult to apply downlit in situations where the user has less control over the output format (e.g. blogdown, learnr, etc.).
downlit could provide two functions, downlit_html() and downlit_md() that are rmarkdown output formats with a downlit post-processor.
For example, for a standard HTML document with custom options
There is a proposal rstudio/rmarkdown#1941 which still await some review and probably updates with newer downlit. (We plan to work on rmarkdown this month). There was an issue with bookdown however regarding how the processing is done using xml2.
For now, only distill has integrated support for highlighting using a knitr hook.
Having a wrapper format is another interesting option - offering integration is usual format seems best however. What do you think ?
For github_document() or md_document, this is a bit different as highlighting won't be useful. I have opened rstudio/rmarkdown#2284 to track and discuss.
Currently, since downlit is intended to be used by other packages, it's difficult to apply downlit in situations where the user has less control over the output format (e.g. blogdown, learnr, etc.).
downlit could provide two functions,
downlit_html()
anddownlit_md()
that are rmarkdown output formats with a downlit post-processor.For example, for a standard HTML document with custom options
a user could ask for downlit to automatically post-process the output by using a
downlit::downlit_html
parent output format:The text was updated successfully, but these errors were encountered: