bug: missing imported identifiers in `b.typ`

[DanikVitek]

Failed to convert typst to docx with the following message:

Converting TYP -> PDF with Typst
Extracting math source code
Extracted 105 math blocks
Converting TYP -> DOCX with Pandoc
"b.typ" (line 1, column 4):
Identifier "arraify" not found
Error: Failed to convert Typst -> DOCX with Pandoc

The "arraify" identifier comes from the algorithmic package, used for pseudocode blocks

[sghng]

It's then clear that this is because I didn't import the packages in b.typ.

The solution that's on the top of my head is when obtaining the math block, also scan which identifiers are not in the Typst stdlib, and find them and import them in b.typ.

This is likely straightforward for most package imports: we use LSP (or directly inspect the AST?) to find the definition, copy that line of code to the top of b.typ, and problem is solved.

However, if the dependency is more complicated (won't be surprised if some user defined their own command to be used in a math environment), it can be very hard to get the whole syntax tree into b.typ.

@DanikVitek could you try the --debug option when running typ2docx, and inspect the .typ2docx/b.typ file, and post the problematic math block along with their originals in your document here?

[DanikVitek]

The problematic block seems to be this one. There are several of them.

$(#arraify(args).join(", "))$

The block comes from the algorithmic package:

#let call(
  name,
  kw: "function",
  inline: false,
  style: smallcaps,
  args,
  ..body,
) = (
  if inline {
    [#style(name)\(#arraify(args).join(", ")\)]
  } else {
    iflike(
      kw1: kw,
      kw3: "end",
      (style(name) + $(#arraify(args).join(", "))$),
      ..body,
    )
  }
)

[sghng]

The problematic block seems to be this one. There are several of them.

$(#arraify(args).join(", "))$

@DanikVitek Got it. It's easy to make arraify work (just include #import "@preview/algorithmc: * in b.typ), but the args might be a bigger problem.

Where and how is args defined? If you defined it elsewhere it'll be quite hard (I guess) to make it work. As I will need to make the tool 1) examine the AST 2) find all logic dependencies of args 3) fetch their code 4) place them in b.typ

This can get extremely messy if you have multiple args defined in different context/scope. I will then need to scope them...

This is not a trivial feature to implement, fortunately I took compiler course before so probably still manageable, but it'll take quite some time...

[DanikVitek]

args is the name of the argument to the call public function of the algorithmic package. This is a base function used for many other functions declared in the package. The function can also be used to declare custom pseudocode keywords and such.

For my case, the formulae isolation is not necessary, as those are used just for visuals of the pseudocode statements.

I can think of one way to bybass this for now: provide the CLI with line number ranges to skip formulae extraction from.