51 ms·

I'm sorry, what exactly is the issue with typst?

• kitchi 5mo ago
  No issues per se, but academic publishing has deep roots in the latex ecosystem. So templates from publishers are often not available in typst, or the publisher insists on a latex formatted file. Often supervisors/professors etc will also resist using typst because of the cognitive overhead on their already oversubscribed time. Typst has about 40 years of history to overcome and that will take a long time to do.
  • leephillips 5mo ago
    Everything you say is true, although Typst is making slow headway¹. Also, it’s possible, using some Pandoc magic², to enjoy aspects of Typst markup while generating a LaTeX document. 1 https://lwn.net/Articles/1037577/ https://lwn.net/Articles/1037577/ 2 https://lee-phillips.org/typstfilters/ https://lee-phillips.org/typstfilters/
• CJefferson 5mo ago
  They made a new format with basically no accessibility. We finally got latex usable by blind people with acceptable html output, I’m not moving to something worse.
  • xigoi 5mo ago
    In what ways is HTML produced by transpiling LaTeX more accessible that HTML produced by Typst?
    • CJefferson 5mo ago
      The HTML generated by LaTeX is currently very good (you can read basically every paper on arXiV in HTML). The html generated by Typst just.. doesn't really work currently. I checked a few weeks ago, tables didn't output sensibly. Looking at the docs their plan doesn't seem to be to aim for total coverage in general.
      • leephillips 5mo ago
        By “The HTML generated by LaTeX” do you mean by latexml (the tool used, I think, by arxiv) or something else?