Issue10294 new code for two column layout on typst 0.12.x

[jarnowic]

Typst 0.12.0 introduces some changes for two column layout, preferring #page(columns: <N>) for global two column output, and supplementing #place with new parameters scope and clearance to layout one column content (such as titleplage) on two column documents. This patch tries to upgrade the typst.template to comply with the newer requirements. Check issue 10294.

[jgm]

template.typst has a set page with other attributes. Why not put the columns there rather than in default.typst?

[jarnowic]

template.typst has a set page with other attributes. Why not put the columns there rather than in default.typst?

Because default.typst is where the variables can be accessed to from the YAML headers or the command line, iiuc; template.typst is out of reach, so pandoc variables cannot affect it.

To tell the truth, I am still not quite sure why so many defaults are set in template.typst; it seems to me that only the variables to be used in customizations in the typst documents should be declared in the typst template, while the document layout decisions might be delayed to the document itself. Looks to me as if template.typst would work as a latex.fmt, just declaring the variables available, while all layout defaults should be moved into default.typst to give room for customization, just as in LaTeX classes and packages. My apologies for the comparison, but that's the model I am more familiar with; groff_ms is still, not much unlike typst, work in progress on my side.

So, if i were to suggest something, i'd say that the layout code should be moved from template.typst into default.typst to allow for more customizations, and not the other way around; but we may ask the proponent of the original typst interface, I guess.

[jgm]

template.typst is out of reach, so pandoc variables cannot affect it.

Not so. You can put variables in partials!

[jarnowic]

template.typst is out of reach, so pandoc variables cannot affect it.

Not so. You can put variables in partials!

you're right; and doing so keeps the change less intrusive than the other one. proceeding.

[jarnowic]

template.typst is out of reach, so pandoc variables cannot affect it.

Not so. You can put variables in partials!

you're right; and doing so keeps the change less intrusive than the other one. proceed

template.typst is out of reach, so pandoc variables cannot affect it.

Not so. You can put variables in partials!

you're right; and doing so keeps the change less intrusive than the other one. proceeding.

I think it is ready now...

[jgm]

looks good - I'll merge this and update the tests.