Pandoc failing on context call

[Tiefseetauchner]

It may be a little stupid, and in #9712 it's been asked but...

Well, I'm working on converting something using TiefDownConverter. Specifically, I'm trying to make a songbook using TiefLied (Yes I really like naming my stuff after myself hehe).

My approach was to make a typ file per song with the #song in it and run TDC on them. So in essence, TDC will take typst files, throw them at pandoc in a command line like pandoc -t typst -o output.typ input1.typ input2.typ input3.typ. Yes, in this case, Pandoc is just a glorified strconcat, but it makes sense performance wise. This is not a standard usecase of TDC to be clear, but what is really...

Regardless, I have a typst file like so:

#import "@preview/tieflied:0.1.0": annotation, bridge, chorus, song, verse

#song(
  title: "Dominoes",
  author: "Anson Seabra",
)[
  #verse[It hurts and I don't know why\
    Was it something I did?\
    Along the ride, in another life\
    Is there something I missed?\
    The generation's up in smoke\
    We look like kids but feel like ghosts\
    Just try and try to feel alive]
]

(Shortened)

And I'm running into issues with Pandoc. Simplified, when running pandoc -t typst -f typst -o asdf.typ 2\ -\ Dominoes.typ, Pandoc gets sad.

"2 - Dominoes.typ" (line 7, column 4):
unexpected end of input
expecting end of input
Identifier "context" not found

Lotsa preamble for this question: Why does Pandoc fail in this case? The typst is just updating a state:

context authors-state.update(authors => {
  if authors.keys().contains(author) {
    authors.at(author).songs.push(title)
    return authors
  }
  authors.insert(author.name, (songs: (title,)))
  authors
})

[jgm]

state isn't yet supported.

I don't see why you don't just use cat for this!
Even without state, typst -> typst via pandoc will be lossy, because everything goes through pandoc's own less expressive document model.

[Tiefseetauchner]

I don't see why you don't just use cat for this!

Ah :) The joys. Because the idea is to make it modular. In essence, throw in the Markdown and Typst and idk, HTML files, and out comes a beautiful whatever. I'm abusing TDC and Pandoc here.

Even without state, typst -> typst via pandoc will be lossy, because everything goes through pandoc's own less expressive document model.

Yeah, I wanted to see how lossy it is. Apparently "unsupported" lossy.

Thanks :)

[Tiefseetauchner]

You gave me the idea, thank you. I implemented an argument to allow swapping pandoc for any arbitrary executable. Now I can "just use cat" and still keep the modular nature of TDC. Thanks for the idea! <3