-
Notifications
You must be signed in to change notification settings - Fork 332
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
new crossrefs+flextable+docx interaction #7321
Comments
This is part of #4944. |
I spent a couple of hours trying to figure out what is going wrong and failed here - I can't tell what we might be emitting that's bad. |
Let's check non-table crossrefs (duh) |
Thank you to the developers working on this! I discovered something interesting when using Quarto's new custom float cross-reference types to implement a workaround that may help you debug. In the YAML header you can define a new custom table type. I used 'table' as the key instead of 'tbl'.
This works without the "unreadable content" warning. BUT if I tell Quarto I want the caption on top of the table, as follows, I then get the unreadable content issue.
|
@altonrus I edited your comment slightly. You can use more backticks in your code block declaration to allow backticks in the code. |
@altonrus |
Based on @altonrus finding the following works for me for docx output:
The problem only seems to be the caption location for docx output. |
I can confirm the warning only appears using default |
Thank you for your interest. |
In .docx format, crossreferenceable code cells with flextable outputs cause Microsoft Word to emit a warning about a malformed document.
This doesn't happen when the code cell isn't crossreferenceable, so we're doing something bad to it.
The text was updated successfully, but these errors were encountered: