Using multiple crossref options

[lorenzoFabbri]

Description

In my main Quarto document I am including another one using {{ < include ... > }}. In the main document I am using the default options for crossref, while in the second one (the one included), I specified the following:

crossref:
  fig-title: "Supplementary Figure"
  fig-prefix: "Supplementary Figure"
  tbl-title: "Supplementary Table"
  tbl-prefix: "Supplementary Table"

The problem is that now all the tables and figures are referenced using this options (e.g., there are no more normal Table X). Is it possible to combine multiple options for crossref in different documents?

Moreover, when I cite inline for instance a table using @, there is no space between the last word before the reference and the reference itslef (e.g., "given inSupplementary Table X").

I am using R version 4.3.1 (2023-06-16) and Quarto version 1.4.487.

[cderv]

In the main document I am using the default options for crossref, while in the second one (the one included), I specified the following

In our doc (https://quarto.org/docs/authoring/includes.html) we say in a Red important callout

Include shortcodes are equivalent to copying and pasting the text from the included file into the main file. This means that relative references (links, images, etc.) inside the included file resolve based on the directory of the main file not the included file.

It also means that if the included file has a metadata block, that block will take effect in all included files. In most cases, having metadata blocks in an included file will cause unexpected behavior.

What exactly would you like to do ? How to you expect "include" to behave ?

As we explain in the doc it is "equivalent to copying and pasting the text from the included file into the main file" - It is not including another independently rendered document

[lorenzoFabbri]

Main Quarto document:

---
title: "Estimating associations..."

format:
  docx:
    reference-doc: reference_document.docx
    citeproc: false

crossref:
  custom: 
    - kind: float
      ref-type: supptbl
      latex-env: supptbl
      prefix: Table S
      name: Table S
      space-before-numbering: false
    - kind: float
      ref-type: suppfig
      latex-env: suppfig
      prefix: Figure S
      name: Figure S
      space-before-numbering: false

link-citations: true
linkcolor: blue

editor_options: 
  chunk_output_type: console

execute:
  echo: false
  warning: false
  error: false
  message: false
---

```{r}
here::i_am("output/paper/manuscript.qmd")
```

{{< include _si.qmd >}}

_si.qmd contains:

```{r info-chems}
#| label: supptbl-info-chems
#| tbl-cap: Information about non-persistent EDCs

edcs_info
```

reference_document.docx

[cderv]

Could you make the example reproducible ? edcs_info or output/paper/manuscript.qmd is not available to us.

[cderv]

I think you hit something we don't support yet - teach knitr to forward some custom crossref element. The specific label prefix is unknown to knitr and not passed currently to the .md output. It should probably be pass through...

Try the usual Markdown syntax, without trying to set some cell options

---
title: "Estimating associations..."
format: html
keep-md: true
crossref:
  custom: 
    - kind: float
      ref-type: supptbl
      latex-env: supptbl
      prefix: Table S
      name: Table S
      space-before-numbering: false
    - kind: float
      ref-type: suppfig
      latex-env: suppfig
      prefix: Figure S
      name: Figure S
      space-before-numbering: false
link-citations: true
linkcolor: blue
editor_options: 
  chunk_output_type: console
execute:
  echo: false
  warning: false
  error: false
  message: false
---

{{< include _si.qmd >}}

See @supptbl-info-chems

With _si.qmd being

::: {#supptbl-info-chems}

```{r info-chems}
knitr::kable(head(cars))
```

Information about non-persistent EDCs
:::

It should works

(and see that I needed to build a reproducible to help - that is why it is really helpful and important that one is provided when reporting issue or asking question - it really saves us time and help us help you!)

[lorenzoFabbri]

You're absolutely right. I would have modified it to be completely reproducible soon.
The thing is that in my document that was a gt table... I see what you did. Wrapping the R code. I'll test it.

[cderv]

I opened an issue about the new custom crossref and cell engine not working as users are trying

• Teach engine about new custom crossref #7665