maxcrees / tbl.typ Goto Github PK

• Column modifiers e and x should constrain text block width.
• Minimum width modifier w(...) should not be applied to spanned text blocks? Currently it is applied; investigate further and supply spec argument to cell-width-at if necessary. tbl.1 suggests that it is ignored unless a width is provided for all spanned columns (likewise with x above, but not e?). Is this behavior worth keeping?
• Shrink text block width if it does not wrap. This is closer to the behavior of text blocks in groff tbl. Choose minimum of determined width (minimum or based on table's max width) versus width of unconstrained text block? May also need to determine if wrapping is occurring (check height before / after constraining width).
• Text that is NOT in text blocks seems over eager to wrap itself, which can cause tables to display strangely. I think traditional behavior here is that such text should NEVER wrap on its own. If we can figure out how tell Typst to NOT wrap text, maybe this can be a new region option? Perhaps by replacing #pad(...) with #box(inset: (...), clip: true).

Allow something like

pad: (x: 5pt)

This could be implemented in a straightforward manner similar to 843c9d1 (distribute excess width to each column proportionally), but I think it would be semantically different than how it works in traditional tbl which adjusts column separations instead.

• Difference: vertical alignment changes from modifiers t and d apply to any corresponding cell, not just those that are row-spanned.
• Spaces before a leading period on a line of table data may not be sufficient to escape it (investigate)
• Add examples for class "A"
• Difference: document other extensions?
• Version history section

Probably need to use pt-length() with calc.max() in a similar fashion as column modifier e (equalize width).

layout did not converge within 5 attempts

Hint: check if any states or queries are updating themselves

I test all the styles, only "chicago-author-title" and "chicago-author-date" will occur this warning

• eval(..., mode: "markup") and eval(..., mode: "math"): typst/typst@f52c39c
• eval(..., scope: ...): typst/typst@803ae93

Starts a new table specification, with more table data to follow.