democat

6 ms·

1. 1.▲
   by democat 8mo ago

   You are absolutely right. Thank you for pointing this out! Regarding your questions: 1. The `\pair` issue: This is definitely a bug. My macro expander is based on text replacement and obviously cannot handle nested parameters. I will fix th
2. 2.▲
   by democat 8mo ago

   You are absolutely spot on. Both systems are Turing-complete, so a perfect conversion without a full runtime execution is theoretically impossible for the general case. That's exactly the trade-off Tylax makes: we aren't trying to
3. 3.▲
   by democat 8mo ago

   Great question! I love Pandoc and use it often, but as a "universal" converter, it sometimes misses the nuances of specific pairs. Tylax is designed specifically for the LaTeX $\leftrightarrow$ Typst workflow. By focusing on just
4. 4.▲
   by democat 8mo ago

   Thanks for the stress test! You are absolutely right, and I really appreciate you catching this edge case. I've traced the issue in the codebase: 1. The recursion depth limit *is* triggering correctly (preventing an infinite loop). 2.
5. 5.▲
   Show HN: Tylax – A bidirectional LaTeX to Typst converter in Rust(github.com)

   27 points by democat 8mo ago|9 comments