quarto-dev / quarto-dev/quarto-cli
Callout Blocks in PDF Divided Awkwardly
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
Bug description
My book's callout blocks, in PDF format, are divided into small pieces that do not fill a page (across multiple pages), rather than filling the page and (if the content runs beyond the end of the page) being divided by the end of the page. (This admittedly could be because my callout blocks contain a large amount of non-traditional content--tables, equations, images, etc.--which may interfere with the page breaks / segmenting.)
Steps to reproduce
Expected behavior
The callout block, in pdf format, should be divided by the end of the page (when the content takes up multiple pages).
Actual behavior
The callout block is divided into snippets (that are well short of the page limit) across multiple pages
Your environment
- IDE: VS Code: 1.84.2
- OS: Edition Windows 10 Enterprise
Version 22H2
Installed on 9/8/2022
OS build 19045.3693
Experience Windows Feature Experience Pack 1000.19053.1000.0
Quarto check output
Checking versions of quarto binary dependencies... Pandoc version 3.1.1: OK Dart Sass version 1.55.0: OK [>] Checking versions of quarto dependencies......OK [>] Checking Quarto installation......OK Version: 1.3.361 Path: C:\Users\amazel\AppData\Local\Programs\Quarto\bin CodePage: 1252 [>] Checking basic markdown render....OK [>] Checking Python 3 installation....OK Version: 3.11.4 Path: C:/Users/amazel/AppData/Local/Programs/Python/Python311/python.exe Jupyter: (None) Jupyter is not available in this Python installation. Install with py -m pip install jupyter There is an unactivated Python environment in Anaconda3. Did you forget to activate it? [>] Checking R installation...........OK Version: 4.3.0 Path: C:/Users/amazel/AppData/Local/Programs/R/R-4.3.0 LibPaths: - C:/Users/amazel/AppData/Local/R/win-library/4.3 - C:/Users/amazel/AppData/Local/Programs/R/R-4.3.0/library knitr: 1.43 rmarkdown: 2.22 [>] Checking Knitr 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 reproducing the issue with the linked callout_error.pdf and review the Quarto check output, especially the reported Quarto and Pandoc versions. The payload names no source file or test; done means confirming that a multi-page PDF callout fills each page before breaking, including with tables, equations, and images.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100