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
Below is the minimal reproducible example (index.Rmd file):
---
title: Figure cross-reference issue in HTML
documentclass: book
site: bookdown::bookdown_site
output:
bookdown::html_document2: default
---
```{r eval=TRUE, include=TRUE}
sessionInfo('bookdown')
rmarkdown::pandoc_version()
xfun::session_info('bookdown')
```
# Zero 1 {-#zero1}
Some text in 1st unnumbered section.
# Practically long header about some theories {#theory}
## Markdown Syntax {#markdown-syntax}
...
### Images {#markdown-syntax-media}
First figure of first section is below, it reference is Fig. \@ref(fig:md-logo).
![(\#fig:md-logo) Markdown logo](https://upload.wikimedia.org/wikipedia/commons/thumb/4/48/Markdown-mark.svg/208px-Markdown-mark.svg.png)
...
While knitting this document using RStudio 2024.04.0 Build 735 with integrated latest pandoc 3.1.11 to HTML I get the wrong rendering
Here my figure is not numbered. So the cross-reference works as expected, but "Figure 1.1: " is not shown.
It is fresh installation of Ubuntu MATE 24.04 LTS.
Other details:
Running remotes::install_github("rstudio/bookdown") does not help.
Also please note that RStudio 2023.03.2-454 with pandoc 2.19.2 produces correct rendering.
The text was updated successfully, but these errors were encountered:
Below is the minimal reproducible example (
index.Rmd
file):While knitting this document using RStudio 2024.04.0 Build 735 with integrated latest pandoc 3.1.11 to HTML I get the wrong rendering
Here my figure is not numbered. So the cross-reference works as expected, but "Figure 1.1: " is not shown.
It is fresh installation of Ubuntu MATE 24.04 LTS.
Other details:
Running
remotes::install_github("rstudio/bookdown")
does not help.Also please note that RStudio 2023.03.2-454 with pandoc 2.19.2 produces correct rendering.
The text was updated successfully, but these errors were encountered: