-
Notifications
You must be signed in to change notification settings - Fork 334
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pagebreak breaks PowerPoint #11893
Comments
I am not sure the page break shortcode has the right OpenXML code for PowerPoint. Word and PowerPoint don't use the same OpenXML code to do the same thing for some reason. Could you also fill the issue template as requested and properly format your post as showed when filling the template? See https://quarto.org/bug-reports.html#formatting-make-githubs-markdown-work-for-us. |
Why do you want to use this shortcode in PowerPoint instead of using what's described in the documentation? https://quarto.org/docs/presentations/powerpoint.html For instance, the headers level does not imply the same thing in presentation formats. Project profile would be the way here as you might have some layout to tweak in PowerPoint while not needed in PDF. Note that the shortcode documentation ever stated PowerPoint was supported, so this is not a bug, but an enhancement is possible. https://quarto.org/docs/authoring/markdown-basics.html#page-breaks |
The issue is caused by the default value used by the shortcode which is a form feed character |
Thanks @mcanouil ! Indeed This could be reported and fix upstream too : And I'll do the same in rmarkdown: |
I would like to output the same document in both PDF and Powerpoint, iteratively. In Psuedocode:
|
Bug description
This renders a PowerPoint that needs to be repaired, omitting the pagebreak does not. Hurts when rendering across formats, eg pdf and powerpoint.
Steps to reproduce
No response
Expected behavior
No response
Actual behavior
No response
Your environment
No response
Quarto check output
format: pptx
A page
Some stuff
{{< pagebreak >}}
Another page
some more stuff
The text was updated successfully, but these errors were encountered: