callout with table produces problem in docx

[vtraag]

Bug description

When a callout contains a table, the generated docx contains "unreadable content" according to Microsoft Word (Office 365).

Steps to reproduce

1. Create a file test.qmd containing the following Quarto

::: {.callout-note}

| Column A | Column B |
|----------|----------|
|        A |        B |

:::

Produces a problem when converted to `.docx`

2. Generate docx using quarto render test.qmd --to docx
3. Open file in Microsoft Word.

Expected behavior

The generated docx should not contain "unreadable content".

Actual behavior

The generated docx contains "unreadable content".

Your environment

Run from the command line from Ubuntu (22.04) and Windows both reproduce this problem. Note that the error in the generated .docx is reported by Microsoft Word, not by Libre Office.

The problem appears with quarto version1.3.433. Double checked with latest pre-release 1.4.268 and the problem persists.

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.433
      Path: /opt/quarto/bin

[✓] Checking basic markdown render....OK

[✓] Checking Python 3 installation....OK
      Version: 3.10.9 (Conda)
      Path: /home/vtraag/mambaforge/envs/science/bin/python
      Jupyter: 4.11.1
      Kernels: python3

[✓] Checking Jupyter engine render....OK

[✓] Checking R installation...........OK
      Version: 4.2.3
      Path: /opt/R/4.2.3/lib/R
      LibPaths:
        - /home/vtraag/R/x86_64-pc-linux-gnu-library/4.2
        - /opt/R/4.2.3/lib/R/library
      knitr: 1.43
      rmarkdown: 2.23

[✓] Checking Knitr engine render......OK

[mcanouil]

The problem appears with quarto version1.3.433.

You seem to imply, this was working before, but I cannot see this working in 1.2.475 nor 1.1.251.

Anyway, I can confirm it's not working with the latest dev version. Thanks for the report.

Note that enabling collapse cannot work for obvious reason in Word document.

[vtraag]

You seem to imply, this was working before, but I cannot see this working in 1.2.475 nor 1.1.251.

Apologies, my wording might be ambiguous indeed. I meant that the problem is showing in 1.3.433, not that it first appears there.

Note that enabling collapse cannot work for obvious reason in Word document.

Yes, indeed, this won't work, I'm aware. This was a leftover from the bigger project where this problem surfaced. It can be safely removed, and the problem will still appear. I've edited it now accordingly.

[cscheid]

Indeed, this document doesn't validate:

./tmp/document-pretty.xml:8: element tblBorders: Schemas validity error : Element '{http://schemas.openxmlformats.org/wordprocessingml/2006/main}tblBorders': This element is not expected. Expected is one of ( {http://schemas.openxmlformats.org/wordprocessingml/2006/main}tblCaption, {http://schemas.openxmlformats.org/wordprocessingml/2006/main}tblDescription, {http://schemas.openxmlformats.org/wordprocessingml/2006/main}tblPrChange ).
./tmp/document-pretty.xml:17: element tr: Schemas validity error : Element '{http://schemas.openxmlformats.org/wordprocessingml/2006/main}tr': This element is not expected. Expected is ( {http://schemas.openxmlformats.org/wordprocessingml/2006/main}tblGrid ).

[schwa021]

This problem is still present. Any estimate on a fix date?

[mcanouil]

When there is an update it's documented on the relevant issues.

[dragonstyle]

This appears to only occur in specific situations - for example - the above repro case only occurs when a title is omitted (at least in my testing using Quarto 1.4). There are OOXML validation errors in the XML that we are producing, but the validation errors are identical when testing a version of the above document with and without a title (and only the one produced without a title indicates it is corrupt when opened).