First Quirks You Will Notice Moving From LaTeX to Typst скачать в хорошем качестве

First Quirks You Will Notice Moving From LaTeX to Typst

0:00 Intro 0:10 Defaults 1:07 Syntax 2:44 Typography 4:19 Mathematics 6:08 Programming 7:41 Miscellaneous Compared to the "enhancements" version of this video, you'll notice that some statements here clash with what is said there. I tried to equally depict both perspectives. That might also be why I included more pending features on Typst's side this time. What you won't find in this video is how to bring features from LaTeX to Typst. I also don't identify converting `.tex` to `.typ` or Typst's fundamental layout model as a "quirk", instead they're completely predictable differences. Think of the list as a collection of impressions on a fairly casual level. Whatever it is that you could consider a con here for Typst probably just has a higher learning curve relative to the rest of the list. It's also important to note that the list is more or less about the default state of both typesetting systems, so the state you're met with when you launch your editor of choice. I came across the listed items over time, but I might still be able to find their particular sources if you're interested, though the code snippets are my own creations. I also touched upon the wishlist from the first posted video. For the most part, I avoided discussing planned features, the prime example being lack of PDF embedding which is now said to arrive sooner than expected. I strongly encourage you to visit Guide for LaTeX users. All in all, you should be able to get used to Typst's design principles sooner or later. Clarification: At 1:30: I had to use maths mode for the `\cdot`, because it wouldn't appear outside of it. At 1:33: the `dots` in Typst's example are just a maths mode shorthand. Still, it's an "inconsistency" you don't encounter in Typst. Another situation like it is when you use `# set page(...)`, not `# set # page(...)`, because `# set` automatically puts you into code mode. When using Typst symbols in maths mode, you can omit the `# sym.` prefix, or `# math.` if you use that. Also, by "know the code" I mean knowning the Alt code that can be typed out manually using the keyboard. At 1:46: yes, apart from `\smallcaps{}` you can also write `\sc` in LaTeX, but that's an entirely different command, not just a different form of the one shown. At 4:02: when using Typst's predefined horizontal spaces in maths mode, you can omit the `# math.` prefix. At 5:50: the vertical fill is unavailable invalid in maths mode for both LaTeX and Typst. So while the choice of "is done anywhere" was incorrect for LaTeX, I didn't blame Typst for not having the vertical fill in maths mode. At 6:37: optional arguments in LaTeX can indeed be provided within curly brackets, however I probably should have mentioned it's a lot more common to see this in your own commands than some package's, let alone in a TeX primitive. And usually, they have to be present, even if empty. At 6:45: regarding the sparser presence of named arguments in LaTeX: they're more frequently found in commands coming from packages as opposed to those made by the user. So for example `\includegraphics[width = ..., height = ...]{...}`. At 7:59: as you can tell from the snippet on the screen, currently only two-letter language codes effect the document. Though if you get it wrong, any two- or three-letter word whatsoever won't trigger errors. At 8:31: those images come from the `mwe` package, but apparently nowadays `graphicx` comes preloaded with them.