-
Notifications
You must be signed in to change notification settings - Fork 326
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
Markdown tables isn't formatted in newer Quarto versions #10904
Comments
This is with latest quarto pre-release. And how website also show the problem as the linked shared. possibly related to Pandoc's change in pandoc 3.2.1
We updated in |
Oh in fact this is definitely something we needed to check when we would update Pandoc ( |
Ok so here is the situation. @cscheid Happy to discuss this live when you're available.
@cscheid based on this, I don't think we can remove the Or at least we need more adaptation. With new Pandoc behavior for table, there is now no more ways to know this is a table produced by Pandoc and not a raw html table passed through. In Quarto we have a third type which is raw HTML table being parsed by Quarto and written back by pandoc (with If we don't want to break our default behavior, I do think we still need a way to add the As shared in #10607, what was done on R Markdown side is to add back the odd and even class on Table process by Pandoc (using Lua Filter) as this was the way to not change any other styling in all the package that would rely on this So we could do the same, at least for HTML table written with |
I have opened a PR for discussion using this idea of Lua filter to revert back Pandoc removal |
Discussed in #10902
Originally posted by snhansen September 27, 2024
Description
I just noticed that markdown tables suddenly doesn't have any formatting done. Is this intentional? The reason I'm asking is because it's how (most of the) tables are presented in the documentation, see e.g. https://quarto.org/docs/authoring/tables.html#markdown-tables
This example from the documentation
renders like this for me:
The text was updated successfully, but these errors were encountered: