quarto-dev / quarto-dev/quarto-cli
`endfloat` package is not supported for quarto tables
Open
Nobody has claimed this yet.
enhancement
latex
tables
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
I have:
- searched the issue tracker for similar issues
- installed the latest version of Quarto CLI
- formatted my issue following the Bug Reports guide
Bug description
See MWE below:
---
title: "Minimal Working Example for endfloat Package"
format:
pdf:
include-in-header:
text: |
\usepackage{endfloat}
keep-tex: true
---
## Introduction
This document tests the LaTeX `endfloat` package in a Quarto PDF output. The `endfloat` package is configured to move figures to the end of the document while keeping tables in their original positions.
## Figure Example
Below is a figure that should appear at the end of the document due to the `endfloat` package.
```{r}
#| label: fig-sample
#| fig-cap: "This is a figure"
plot(1)
```
See @fig-sample for the figure reference.
## Table Example
Below is a table that should remain in its original position, as `endfloat` is configured to ignore tables.
```{r}
#| label: tbl-sample
#| tbl-cap: "A sample table"
#| echo: false
library(knitr)
data <- data.frame(
A = c(1, 2, 3),
B = c("X", "Y", "Z")
)
kable(data)
```
See @tbl-sample for the table reference.
## Conclusion
The figure (@fig-sample) should be placed at the end of the document, while the table (@tbl-sample) remains here in the main text.
My guess
I found the quarto tables uses longtable environment rather than table environment, this probably the root of problem.
Here is the output:
Steps to reproduce
No response
Actual behavior
No response
Expected behavior
No response
Your environment
No response
Quarto check output
> quarto check
Quarto 1.7.29
[✓] Checking environment information...
Quarto cache location: /Users/ming/Library/Caches/quarto
[✓] Checking versions of quarto binary dependencies...
Pandoc version 3.6.3: OK
Dart Sass version 1.85.1: OK
Deno version 1.46.3: OK
Typst version 0.13.0: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
Version: 1.7.29
Path: /Applications/quarto/bin
[✓] Checking tools....................OK
TinyTeX: v2025.06
Chromium: 869685
[✓] Checking LaTeX....................OK
Using: TinyTex
Path: /Users/ming/Library/TinyTeX/bin/universal-darwin
Version: 2025
[✓] Checking Chrome Headless....................OK
Using: Chrome found on system
Path: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
Source: MacOS known location
[✓] Checking basic markdown render....OK
[✓] Checking Python 3 installation....OK
Version: 3.12.4 (Conda)
Path: /Users/ming/.config/miniconda3/bin/python
Jupyter: 5.7.2
Kernels: python3
(|) Checking Jupyter engine render....2025-08-06 11:30:53,015 - traitlets - WARNING - Kernelspec name python3 cannot be found!
2025-08-06 11:30:53,015 - traitlets - ERROR - No such kernel named python3
Traceback (most recent call last):
File "/Users/ming/.config/miniconda3/lib/python3.12/site-packages/jupyter_client/manager.py", line 87, in wrapper
out = await method(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/ming/.config/miniconda3/lib/python3.12/site-packages/jupyter_client/manager.py", line 435, in _async_start_kernel
kernel_cmd, kw = await self._async_pre_start_kernel(**kw)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/ming/.config/miniconda3/lib/python3.12/site-packages/jupyter_client/manager.py", line 397, in _async_pre_start_kernel
self.kernel_spec,
^^^^^^^^^^^^^^^^
File "/Users/ming/.config/miniconda3/lib/python3.12/site-packages/jupyter_client/manager.py", line 195, in kernel_spec
self._kernel_spec = self.kernel_spec_manager.get_kernel_spec(self.kernel_name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/ming/.config/miniconda3/lib/python3.12/site-packages/jupyter_client/kernelspec.py", line 285, in get_kernel_spec
raise NoSuchKernel(kernel_name)
jupyter_client.kernelspec.NoSuchKernel: No such kernel named python3
No such kernel named python3
[✓] Checking Jupyter engine render....OK
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by rendering the provided MWE with Quarto PDF output and inspect the generated .tex file enabled by keep-tex, focusing on the longtable output and the endfloat configuration. Compare the generated document with the expected figure-at-end and table-in-place behavior, then use the smallest reproducible case to verify the corrected rendering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- latex, r
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100