Antlr sounds excessive for either of those. Use an ordinary xml library for docx (if there's not already one for docx) and something simple for typst.
Programming
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
I want to compile the docx INTO a typst file, not a separate parser for each
Oh, ok, antlr would be inappropriate then. I'd check whether pandoc already does that conversion.
I just checked, it does convert to Typst but I do want to write custom stuff alongside what pandoc will output, that seems like the right tool and saves me a lot of efforts, thanks
ANTLR is for writing parsers. You don't need a new custom parser, just use an existing XML parser.
I'm not sure what the best approach would be, but for reading docx you might be better off using something like Apache POI. Docx may be XML, but it's imo absolute abuse of XML. POI shields you a little bit from all the nonsense happening in docx. I could see ANTLR working for Typst since there's probably not another interface for it.
I don't think it'll support it, but you could also check if this can be done with pandoc.
I don't know anything about Typst, but I do know that .docx files are really just a zip file containing a folder structure with a bunch of xml (and a few other) files. I've written a few find/replace docx scripts in bash utilizing this information.
Since the source is XML XSLT may work to transform it.