Modern LaTeX • Hacker News Board

Re: Modern LaTeX

#221

Post by xiaohanyu » Thu, May 08, 2025, 12:46 PM UTC

herewulf wrote: post #31

I'm finally updating my CV after years of neglect. I'm keen on switching to the route of Org mode -> LaTeX -> PDF. It's partly because I love the simplicity/power of Org and I do all my writing in it nowadays, the other part is to separate the content from the presentation so I can have the content in two different languages but still end up with the same formatted document for both. Anyone have experience with this…

If you do not insist on org-mode, then maybe you can try to organize your CV in YAML format with a tool called YAMLResume: https://yamlresume.dev, which transforms a resume in YAML to LaTeX and generate PDF.

Re: Modern LaTeX

#222

Post by xiaohanyu » Thu, May 08, 2025, 12:48 PM UTC

dev_l1x_be wrote: post #115

For me Typst replaced Latex years ago. pros: - one small compiler that can output: pdf, png, svg, html - compilation is fast (see below) - syntax is much cleaner than Latex - few ways of to a thing - already has all the templates most people need - tooling is good enough with VS Code - supports SVG images cons: - less users? time typst compile cv.typ ________________________________________________________ Executed i…

Typst is a pretty good alternative to LaTeX and I agree all pros in your comment, with only one major deal breaker now: its CJK support is not mature enough and not producation-ready yet.

I wrote a post half year ago explained the details for my decision between LaTeX and Typst: https://blog.ppresume.com/posts/on-typesetting-engines#typst

Re: Modern LaTeX

#223

Post by naikrovek » Fri, May 09, 2025, 1:19 AM UTC

eru wrote: post #218

naikrovek wrote: post #217

Earlier quoted context omitted.

Yeah, I wonder how good TeX renderers would have gotten if page rendering happened client side in a browser.

TeX worked (and works) in batch mode on ancient hardware. Today's computers are so much faster, that this should actually be fast enough to run interactively without having to change or optimise too much.

Why does TeX take so long to render documents today, then?

Re: Modern LaTeX

#224

Post by mzl » Fri, May 09, 2025, 8:07 AM UTC

josephg wrote: post #50

mzl wrote: post #43

Earlier quoted context omitted.

MDX as a middle ground with most of the text standard markdown and the escape hatch of custom React JSX when needed has worked well for me.

MDX advertises itself as "markdown + components", but its not commonmark compatible. I tried using it a few years ago. In the process, I migrated over some regular markdown documents and they render incorrectly using MDX. I filed a bug (this was a few years ago) and I was told commonmark compatibility was an explicit non goal for the project. Meh.

I didn't know that, that is unfortunate to hear.