Semicolon swallowed after link with org mode input and typst as pdf engine

[egh]

org_semicolon_typst.txt

Explain the problem.

A semicolon after a link seems to be swallowed somehow when outputting pdf with typst.

$ mv org_semicolon_typst.txt org_semicolon_typst.org
$ pandoc org_semicolon_typst.org -o out.pdf --pdf-engine typst

Outputs: out.pdf
Pandoc version?

$ pandoc --version
pandoc 3.1.10
Features: +server +lua
Scripting engine: Lua 5.4
User data directory: /home/egh/.pandoc
Copyright (C) 2006-2023 John MacFarlane. Web: https://pandoc.org
This is free software; see the source for copying conditions. There is no
warranty, not even for merchantability or fitness for a particular purpose.

[jgm]

From this input, pandoc produces the following typst output:

== Foo
<foo>
- #link("http://example.org")[foo]; bar

The semicolon is there. So, this seems to be a feature (or bug) of typst? You should consult with typst experts, probably, to figure out what is happening.

[egh]

Thank you for looking into this. I will file an upstream bug.

[egh]

This seems to be intended behavior in typst. See https://typst.app/docs/reference/scripting/#expressions

In Typst, markup and code are fused into one. All but the most common elements are created with functions. To make this as convenient as possible, Typst provides compact syntax to embed a code expression into markup: An expression is introduced with a hash (#) and normal markup parsing resumes after the expression is finished. If a character would continue the expression but should be interpreted as text, the expression can forcibly be ended with a semicolon (;).

I asked about this here: typst/typst#2960 (reply in thread)

So I think pandoc needs to "forcibly" end the expression with a semicolon.

[jgm]

Oh, of course. I think I'll just produce it whenever we have inline code, to be safe.

[egh]

Thank you for the very quick fix!