Citing R-Packages via "grateful::cite_packages()" breaks in pdf-output in quarto 1.4.549, but works in 1.3.450 #8580
-
DescriptionHello. I am quite a bit baffled. I recently updated to quarto v.1.4.549 - initially via SetupI have attached 4 sets of files, for the following scenarios:
Note that the file rendered is identical across all scenarios. While this means that the quarto v.1.3.450-cases contain breaking table captions, I considered equal input data more relevant in this scenario. Invalid table-captions should also not have anything to do with the issue itself. No external citations are required. Packages are installed from renv for projects, and must be installed prior to use for standalone versions if not installed already. v.1.4.549In both standalone and project setups, In HTML/DOCX, In PDF, all packages are added to the bibliography and displayed at the end of the file (again, with the exception of 1.3.450In HTML/DOCX/PDF, all citations (except for Example found in this repo I can't imagine what is causing this, but this is currently hard-breaking a project of mine; which is now retrospectively going to be downgraded to 1.3.450. Thankfully I had not yet transitioned much significant content to 1.4-features, so this at least saves me some time now. I hope these details are sufficient to reproduce this problem. Thank you. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 19 replies
This comment has been hidden.
This comment has been hidden.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
That's a bug. |
Beta Was this translation helpful? Give feedback.
-
I installed General infoThere are 2 main methods to caption a table:
The presence of either one of these introduces the bugs described below; their erroneous intermediary outputs are seemingly identical. The example below is for captioning via When rendering to Removing the The Take the following document: ---
title: "reprex_new_standalone_overwriting_cites"
bibliography: "grateful-refs.bib"
format:
pdf:
keep-md: true
keep-tex: true
html:
keep-md: true
docx:
keep-md: true
---
(table [-@tbl-PackageVersions2])
This is a playground for Quarto `r quarto::quarto_version()`.
Standalone file, rendered in RStudio via `Render Current Document`.
---
```{r}
library(grateful)
library(knitr)
library(sessioninfo)
library(formatdown)
library(processx)
library(quarto)
library(renv)
library(rmarkdown)
library(tidyverse)
library(yaml)
cites <- cite_packages(
output = "table"
, out.dir = "."
, cite.tidyverse = TRUE
, pkgs = "All"
, include.RStudio = TRUE
, dependencies = FALSE
#, omit = c("base","formatdown")
)
print(cites)
typeof(cites)
```
---
caption via Cell label `#| tbl-cap`
<!-- caption via `knitr(...,caption = "caption")` -->
```{r}
#| label: tbl-PackageVersions2
#| echo: FALSE
#| warning: FALSE
#| cache: FALSE
#| tbl-cap: "caption via tbl-cap"
kable(cites)
```
---
manual table copied from the `.md`-intermediate: the cites themselves _can_ get rendered correctly.
|Package |Version |Citation |
|:-----------|:-------|:----------------------------------------------|
|base |4.3.2 |@base |
|formatdown |0.1.2 |@formatdown |
|knitr |1.45 |@knitr2014; @knitr2015; @knitr2023 |
|processx |3.8.3 |@processx |
|quarto |1.3 |@quarto |
|renv |1.0.3 |@renv |
|rmarkdown |2.25 |@rmarkdown2018; @rmarkdown2020; @rmarkdown2023 |
|sessioninfo |1.2.2 |@sessioninfo |
|tidyverse |2.0.0 |@tidyverse |
|yaml |2.3.8 |@yaml |
---
```{r}
sessionInfo()
``` This document consists of 2 tables, however the second one is merely the raw-markdown table resulting from conversion retrieved from the In PDF, the first citation in the table3 (in this scenario, Additional issuesWhile writing down this follow-up, I discovered a couple more things that go wrong.
The document used in this comment, alongside all rendered output-data & intermediaries can be found in the Note that the changes I perform for additional details (e.g. removing yaml-keys) is not reflected, as this is only a single source-doc. Footnotes
|
Beta Was this translation helpful? Give feedback.
@Gewerd-Strauss The issue is now fixed and should be available in the future v1.5.9 pre-release build (not yet available).