[mcanouil]

Introduce the ability to set custom height and width for landscape sections in DOCX format, enhancing document formatting flexibility. Default values are provided if none are specified.

• Add tests
• Add changelog entry

Investigate #12917

[posit-snyk-bot]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

[cscheid]

I understand why you added unit handling here, but this makes me think that we need to figure out how to get unit handling to behave uniformly across Quarto.

[cscheid]

@gordonwoodhull What do you think if we took the code you wrote in src/resources/filters/modules/typst_css.lua and made it a general-purpose Lua module to be used across our filters? It would require a bit of refactoring, but I think it's worth it.

[mcanouil]

Feel free to take over the PR.
It was mostly a proof of concept of what it could be.

[gordonwoodhull]

Sure! The routines in typst_css.lua

1. parse a CSS length with suffix
2. output the Typst equivalent of a parsed length, where 5 out of 43 length units pass through, and two are translated (px and the pseudo-unit %).

I guess what we'd do is move the parse functions to, like, a parse_css module, and then write length output functions for other output formats, where docx always outputs to twips with no suffix.

And we could leave the door open to generalize colors in the same way later.

[cscheid]

Thanks! We need a changelog entry and tests as well.

[mcanouil]

I'm closing this pull request without a replacement.

While reworking it, I found that Quarto doesn't set the page size of a Word document at all, so Word falls back to its regional default (details in #12917).
Changing the landscape default would move the mismatch from one group of users to another.
Explicit sizes would still be useful, but they'd need integer twips and other names, because width and height already mean layout-cell size on divs.

I've suggested a documentation note with a raw OpenXML workaround on #12917 instead.