-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parse R code (dataframe) to rmarkdown formatting #208
Comments
Here is a workaround and function that give decent results. Reproducible rmarkdown example:
However, this workaround won't work if you are indenting your publications in
Despite the indenting problem, would you consider adding this function to |
I was looking for a similar formatting when using vitae templates. Worked fantastically, thanks! |
I would like to import my publications from Google Scholar with the
scholar
package and format them in rmarkdown (primary author in bold, journals in italics, etc.), steps I am currently doing manually. The problem is turning R code to rmarkdown and making it look good.In my code chunk I use
results = "asis"
and create the dataframe. The result when knitted formats italics and bold correctly, however all entries end up squeezed in a single paragraph instead of several lines with spaces between them.I know you mentioned in another issue it might not be possible to create a .bib bibliography file that could then be used with
scholar::bibliography_entries
. However, I was wondering if there was any way to get nicely formatted knitted rmarkdown code from an R code chunk. I feel that, given the Google Scholar data is all there (and accurate in my case), it's a shame I can't use it to format it properly.We would just need a way to declutter the squeezed paragraph on separate lines that so it looks like other regular rmarkdown entries. I've tried pasting
\\newline
and\\linebreak
at the end of each entry but it seems LaTeX doesn't end up parsing it correctly as it just prints those commands as part of the text entries.The text was updated successfully, but these errors were encountered: