Replies: 1 comment
-
What's typically a better idea is to instead emit your logical data as JSON or similar and ingest that in Typst via the data loading functions. Then you can handle the data generation in whatever language while using Typst's programming capabilities for the typesetting part. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'd love to use Typst for laying out machine-generated content, but as it stands, the Typst markup language doesn't seem trivial to emit.
Something like a stream of (ND)JSON could maybe work here, where e.g. (and I haven't thought this through!)
could become
or
could become
Is this a silly thought?
Beta Was this translation helpful? Give feedback.
All reactions