Document conversion and assets

Configure a converter#

Open Settings → Tools → LaTeX → Conversion. Choose Pandoc or Morph, locate its executable, or use Auto-detect. Use the tool version required by your project; the plugin does not bundle every external converter.

Convert to a new output first#

Invoke Convert LaTeX to Typst… on a LaTeX document, or Convert Typst to LaTeX… on a .typ file, through the Convert Document context/Refactor/Tools menus. The converter writes temporary output before an existing destination can be replaced.

Start with a small document:

\documentclass{article}
\begin{document}
\section{Summary}
A result with \emph{emphasis} and $x^2$.
\end{document}

Inspect the generated heading, emphasis, and formula. Then test the workshop’s cross-references, bibliography, and longtable to see where conversion needs manual work. A successful process exit does not establish equivalent layout or semantics.

Keep assets reachable#

Pandoc resource directories tell Pandoc where to find referenced assets. Enter one directory per line; relative values start at the project root. These and extra Pandoc arguments do not apply identically to Morph. Review output paths and warnings before accepting the diff.

Image insertion and paste actions can help create appropriate source references, but the eventual build still needs the actual file in the expected location. Keep source images with the document rather than relying on a machine-local clipboard or temporary directory.

Review the hard cases#

Custom macros, package effects, floats, TikZ, Beamer overlays, bibliography pipelines, and Typst styles/functions can be flattened, emitted as raw content, or rejected. Compile/render the destination format and compare the result. Keep the handwritten original until the converted document has passed that review.