How do I avoid weird arbitrary column layouts for Typst PDF tables generated by R (Kable)?

[BMMilligan1]

Description

I'm currently using quarto (in R studio) to render tables into Typst using the default template. If I produce a multi-column table with the code below (for example) the Typst output contains hard-set column widths that result in a lot of overflow issues with the text (see attached example). When I examine the raw Typst output (below), I see it is setting hard column percentages. Is there any way I can avoid this behaviour with some clever header includes or similar? I really don't want to have to set each table individually, or edit the raw Typst manually.

Using the latest version of R studio, quarto, etc etc on Mac OS.

<!--- This code reads a table from a csv file and displays it at the desired font size. Change the header.tex for PDF output
-->

.small .table {font-size: 11px;}

::: small

data <- read.csv(file = "sustainability-standards.csv")
library(knitr)
kable(data[1:7, ], caption = "Overview of Climate-related Disclosure and Reporting Standards.")

:::

<!--- End of code snippet
-->

:

#block[
#table(
columns: (2.49%, 18.15%, 16.37%, 17.79%, 27.76%, 17.44%),
align: (left,left,left,left,left,left,),
table.header([Region], [Standard], [Scope], [Coverage], [Purpose], [Uptake],),
table.hline(),
[Global], [Taskforce on Climate-related Financial Disclosures], [Climate-related financial disclosures], [Climate risk and opportunities], [Provide recommendations for diclosing climate-related risks and opportunities], [Wide adopted espectially in finance],
[Global], [Carbon Disclosure Project], [Climate and environmental reporting], [Climate change, water, security, deforestation], [Enable compnaies to measure and manage their environmental impacts], [Widely used globally],
[Global], [Integrated Reporting], [Financial, social and environmental reporting], [Financial performance, ecological, social metrics], [Promote transparency and holistic reporting], [Increasingly adopted by companies],
[Global], [Science-based Targets Initiative], [Set science-based climate targets], [Corporate GHG emissions], [Help companies set GHG reduction targets in line with climate science], [Widely recognised especially in corporate sector],
[USA], [Sustainability Accounting Standards Board], [Industry-specific standards], [Environmental, social, governance], [Provide industry-specific standards], [Growing adoption particularly in the US],
[Global], [Climate Disclosure Standards Board], [Climate-related financial disclosures], [Environmental information], [Integrate climate-related information into mainstream financial reporting], [Increasingly recognised globally],
[Global], [Global Reporting Initiative], [Sustainability reporting standards], [environmental, social, governance], [Provide comprehensive sustainability reporting guidelines], [Widely used globally],
)
]
#block

[mcanouil]

The default is to use equal widths for columns.
Use tbl-colwidths as described https://quarto.org/docs/authoring/tables.html#column-widths

Or eventually produce an HTML table with the columns width set.

Could you properly format your post using code blocks for code and terminal outputs? Thanks.
If your code contains code blocks, you need to enclose it using more backticks, i.e., usually four ````.
See https://quarto.org/bug-reports.html#formatting-make-githubs-markdown-work-for-us.

---

You can share a self-contained "working" (reproducible) Quarto document using the following syntax, i.e., using more backticks than you have in your document (usually four ````).
See https://quarto.org/bug-reports.html#small-is-beautiful-aim-for-a-single-document-with-10-lines.

If you have multiple files (and if it is absolutely required to have multiple files), please share as a Git repository.

R	Python
````qmd --- title: "Reproducible Quarto Document" format: html engine: knitr --- This is a reproducible Quarto document. {{< lipsum 1 >}} ```{r} x <- c(1, 2, 3, 4, 5) y <- c(1, 4, 9, 16, 25) plot(x, y) ``` {#fig-placeholder} {{< lipsum 1 >}} The end after @fig-placeholder. ````	````qmd --- title: "Reproducible Quarto Document" format: html engine: jupyter --- This is a reproducible Quarto document. {{< lipsum 1 >}} ```{python} import matplotlib.pyplot as plt x = [1, 2, 3, 4, 5] y = [1, 4, 9, 16, 25] plt.plot(x, y) plt.show() ``` {#fig-placeholder} {{< lipsum 1 >}} The end after @fig-placeholder. ````

Additionally and if not already given, please share the output of quarto check within a code blocks (i.e., using three backticks ```txt), see https://quarto.org/bug-reports.html#check.

[BMMilligan1]

Thank you! And noted. I also managed to solve it using a different set of Kable parameters. This code below produces correct automated table behaviour in Typst for reasons I don't understand.

```{r echo = FALSE, results = 'asis'}
data <- read.csv(file = "Figure-10.csv")
library(knitr)
kable(data[1:5, ], 
      caption = "Overview of Governance and Ethical Investing.",
      format = "simple",
      booktabs = TRUE,
      align = 'l')
```

[mcanouil]

Use keep-md: true and look at what your code produces in each cases.

Note that you should use the following syntax in Quarto.

```{r}
#| echo: false
#| results: asis
#| tbl-cap: "Overview of Governance and Ethical Investing."
data <- read.csv(file = "Figure-10.csv")
library(knitr)
kable(data[1:5, ], 
      format = "simple",
      align = 'l')
```

See knitr::kable and Quarto documentation about tables (and Pandoc on the same topic).

In Quarto, you should not have no options set in the code cell header but instead have all options should be written inside the code cell using YAML.