quarto-dev / quarto-dev/quarto-cli

Cannot put notes on Section Header slides

Open
#7,383 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug pandoc pptx upstream
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

Bug description

First, it's so awesome that we can now create well-formatted Powerpoint files from R Studio!

Today I ran across what might be a bug or might just be a limitation: I am creating a PPTX file using a template that has Title, Section Header, and Title and Content slide formats. I tried to add notes to the slides and the rendering would break. After some testing, I found that when I added notes to Section Header slides, the section headers were formatted like Title and Content slides and the Title and Content slides were not formatted properly at all. The entire Powerpoint would render this way if there were notes on ANY of the Section Header slides. I can add notes to the Title and Content slides without issue.

Thanks!

Steps to reproduce
---
title: "Fake file for reproducing"
subtitle: "Whoop here it is"
format: pptx
---

# This is a Section Header slide with one hashtag to denote

::: {.notes}
I wanted notes on the section header slides but it breaks the rendering completely. If I leave off the notes on the section header slides everything works great.
:::

## This is a Title and Content slide which breaks if I put notes on Section Header slide

* Woooooo
* Wooooooooo
* Wooooooooooo

## Here is another Title and Content slide which will look terrible as well

Expected behavior

I should get 4 slides: a title slide, a Section Header slide, and two Title and Content slides.

Actual behavior

I get 2 slides: a title slide and a terrible slide with all the 3 slide content together

Your environment
  • IDE: RStudio 2023.06.2 Build 561
  • OS: Mac Ventura 13.5
Quarto check output

I have no idea how to do this. Where do you type bash?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue using the supplied QMD example and a PowerPoint template containing Title, Section Header, and Title and Content layouts. Compare output with and without notes on Section Header slides; done means the document renders four correctly formatted slides rather than two merged slides.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.