Hacker News new | ask | show | jobs
by enriquto 615 days ago
> Yes that works.

Oh, that great! My major point of friction with LaTeX is that using unicode is not straightforward. You sort of can, by including the right packages and using the right interpreters, but it imposes strange constraints involving the fonts that you can use and whatnot.

Regarding the usage, it's probably my fault. I tried to compile it locally and it didn't work at first (requires newer rustc version).
1 comments
jimhefferon 615 days ago
> My major point of friction with LaTeX is that using unicode is not straightforward.

Possibly you are describing how it used to be before the input encoding standard for LaTeX switched to UTF-8?

link
enriquto 615 days ago
No. I'm talking about modern LaTeX. You can easily write é outside of math mode, but not inside. By default, you cannot write α either inside nor outside of math. By using the right packages, you can do both, but other things break.
link
aragilar 615 days ago
Which engine? I believe XeTeX and LuaTeX support it natively?
link
enriquto 615 days ago
Yes, that is the problem, precisely. Lualatex and xelatex do not support all the features of plain latex (mostly "hacky" things, like pdf controls, js animations in beamer, etc). So, you have to chose between using these features and being able to type unicode letters directly.

Probably there is a magic combination of engines and packages that allows to do everything at the same time, but I haven't found it.

If this works natively in typst, it's a great selling point for me (although I dislike the markdown-like syntax).

link
aragilar 615 days ago
Uh, pdftex, xetex and luatex should support everything of the original tex engine, but each has extended tex, so some things will work on pdftex (which I think is what you're thinking of as plain latex), others on xetex and then others on luatex (or pairs of engines, I know microtype works on pdftex and luatex, but not xetex). I don't think this is an tex specific problem, more a natural result when there's multiple implementations.

I suspect as typst only has a single implementation (I believe), it won't have the problem of different engines ;)

link