@david_chisnall I'm quite curious about how you landed in AsciiDoc... after all, I added a project of yours to my list about document formats:
https://alex.corcoles.net/notes/tech/document-formats
... which has a major focus on ASTs...
@david_chisnall I'm quite curious about how you landed in AsciiDoc... after all, I added a project of yours to my list about document formats:
https://alex.corcoles.net/notes/tech/document-formats
... which has a major focus on ASTs...
Our hardware engineering team wanted to use it for our datasheets. Their reasons were mostly:
It's not MS Word
It's not MS Word
It continues to not be MS Word
asciidoctor-diagram has a plugin that's really nice for rendering waveforms
It still isn't MS Word
I didn't want to burn more innovation tokens by writing the relevant wrappers for things like WaveDrom or be responsible for bugs.
Unfortunately, I overestimated how easy it was for us to extend AsciiDoctor.
@david_chisnall there was a fair attempt by the AsciiDoctor guy to write a *good* parser with a *good* AST, which would have improved things a lot. However, I think it stalled at some point:
https://github.com/opendevise/asciidoc-parsing-lab
BTW, their Zulip was very helpful back when I was messing in those things. (I started to write a parser in Prolog.)