We put LaTeX (and Asciimath and PlantUML) parsing into Asciidoc kinds and it works well.
Running the LaTeX parser over Markdown is a total shitshow, of course, but we all knew that. Use at your own risk. No, the other people don't do it any better. They just don't test as much and don't even notice that sections disappear or are garbled, or that prose text gets mathified.
awesome work 👀
Still need to add TikZ and BPMN, but I need to sleep and catch up on my day job.
At the moment, I just render a placeholder SVG, with a fold-out of the original syntax-highlighted code.
If you are a serious academic and want to make sure that your stuff always renders well and sections don't disappear, then you need to PUT IT IN ASCIIDOC.
Markdown is for comments or chit-chat or support issues. It is not the proper format for your Ph.D. thesis, don't be silly.
TeXtstr seems to have no problems, maybe with the Tex Willer logo, it could be fun, https://www.texstr.org/
cc: nostr:npub18vay956v7zs5qtgc65mvn54v96cuvqv6j9fmu4cgfjqkt5vjuvjsc47nzf
For simple stuff it works well, but I am sure I could break it trying some more complex stuff. For example I just implemented $ and $$ for marking latex content, avoiding \(\) and \[\] for simplicity. Also, most of the markdown+latex component that renders the text was single prompted and I think I may have used 3 more prompts or so to fix some edge cases. I can see why people are resistant to adding it to the NIP or implementing on their clients, but I really needed this feature and just vibe hacked it.
