• Retiring@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    8 months ago

    There are a lot of typos in this book. Are you looking for someone to proofread? Great work btw

  • filister@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    8 months ago

    You guys should also check out Typst https://typst.app/. It is a lot easier than LaTeX even though not as powerful. It has meaningful error messages making the debugging a lot more user friendly.

    • nice@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      1
      ·
      8 months ago

      I had been using LaTeX at work and decided to give Typst a try:

      I installed the compiler and vscode extensions to run Typst natively.

      Setting up my orgs template in Typst was significantly easier then LaTeX and took about 20% less lines of code.

      I like the more modern, practical syntax for writing docs.

      It’s still a relatively young project though, so I found a few rough edges:

      • Paragraph indentation rules for my language weren’t available: managed to find a workaround though
      • Only allows use of relative paths for images, imports etc: apparently for security reasons, forces me to have template logo in almost every folder
      • Localized dates: Typst can’t do it
      • No \graphicspath like command: LaTeX will search for an image by filename in each specified folder, in order. Typst has no equivalent command (yet)

      Overall I was positively impressed, but went back to LaTeX mostly because of the last two points. Curious to see how Typst will be in a few years!

    • Retiring@lemmy.ml
      link
      fedilink
      arrow-up
      0
      arrow-down
      1
      ·
      8 months ago

      Under every single LaTeX themed post there is someone suggesting typst. Why use something open, if you can use something proprietary? /s