221–230 of 243 posts
Earlier quoted context omitted.
TeX has three actively-maintained engines, and there are a lot of folk putting work into improving LaTeX and its ecosystem. So effort is going into LaTeX, including performance, right now. Probably someone committed a perf improvement today, or in the last week. There are problems with TeX which can't be fixed, problems which Typst is directly addressing. I wish them all success. I will never understand the attitude…
What problems with TeX is Typst fixing? I ask because most issues I got using LaTeX tend to be the result of LaTeX additions, very rarely are they issues from TeX itself. Heck I even took to using TeX macros at some point because while they can be an amazing footgun they're also a lot simpler.
Earlier quoted context omitted.
I think you're imagining things... This spacing stuff is mostly defined in the font files and typst uses the same math font (or a more recent version, depending on your LaTeX config). I made a small comparison: https://imgur.com/a/0k6dsok Note that by default, typst uses the book weight from New Computer Modern. This corresponds to the default settings in LaTeX with the "fontsetup" package. The only difference I can…
You have a Mac with fractional scaling, your screenshots show the common blurriness render issue more than anything else I believe. Apart from that there is clearly a size difference but I agree that it's quite close. I think it's good to be detailed oriented but I'm not sure the fetish around Latex rendering is warranted.
Earlier quoted context omitted.
I played with this briefly, and saw that supplement can also take a function, which presumable how you make @wibble return '(34)' instead of 'Equation 34'? The function is passed the equation itself, so supplement: x => x makes the reference identical to the whole equation (!), but it wasn't obvious to me how to extract just the equation number from an equation x? This is a really common idiom in mathematical writing…
I would just define `#let eqref(target) = "(" + ref(target, supplement: none) + ")"` and then use it as in "from #eqref( ) we see that..". You can probably do that with a function given as supplement but it looks a bit involved, I think you'd have to do something like in this example: https://typst.app/docs/reference/model/ref/#customization (I think the reference system is an area where things can be improved to mai…
Earlier quoted context omitted.
What problems with TeX is Typst fixing? I ask because most issues I got using LaTeX tend to be the result of LaTeX additions, very rarely are they issues from TeX itself. Heck I even took to using TeX macros at some point because while they can be an amazing footgun they're also a lot simpler.
The user interface / language design. See talk "LaTeX: It's Not You, It's Me" by Martin Haug (cofounder). TeX's language design is at the level of Basic's. Which is in fact not surprising given the timeframe.
I suppose the fact that LaTeX works at all is a testament to TeX's power, but yes I can imagine a better base language could be relevant for something like Typst.
I tried typst several months (or was it already a year?) ago, and I found it really great. I was even able to easily modify a simple plugin after barely playing 1 hr with it, where in latex that I used for years, I never even tried (to be fair the amount of plugins meant I didn't need to).
I just wish I had a good reason to use it... maybe when the implement the html output ?
Earlier quoted context omitted.
The user interface / language design. See talk "LaTeX: It's Not You, It's Me" by Martin Haug (cofounder). TeX's language design is at the level of Basic's. Which is in fact not surprising given the timeframe.
Ah I see, so not exactly the kind of thing you'd notice making a document but you would if trying to extend the actual language. I mean TeX is basically an overpowered lambda calculus with a focus on text markup and generation. I suppose the fact that LaTeX works at all is a testament to TeX's power, but yes I can imagine a better base language could be relevant for something like Typst.
By "user interface" I mean (like Martin, in the linked video) the surface language, the way you interact with TeX, its syntax and how it presents itself to the user, the programming model. So definitely the kind of thing you'd notice making a document. Leaky abstractions and footguns are basically everywhere when you write a big LaTeX document.
> I mean TeX is basically an overpowered lambda calculus with a focus on text markup and generation.
No, lambda calculus has capture-avoiding substitution, aka hygienic macro expansion if you will. TeX has naive substitution. By the way, macro expansion is typically CBN, which is very much a rare and weird evaluation order (yes, Haskell, i know). TeX is much closer to some kind of assembly language for a virtual machine.
Earlier quoted context omitted.
and that tag is kind of moot -- as another commenter mentioned, it could have been some other html tag like a div
It's not a tag, there aren't even HTML/XML tags in Typst. The effect of that is giving the #figure(...) element the label `figure` (i.e. the name is what's inside the ). Probably using the label "figure" was not the best choice for an example, something like would have been a bit less confusing showing that it is an arbitrary name/id that you choose. Edit: and I think you also misinterpreted the other comment about t…
Earlier quoted context omitted.
You have a Mac with fractional scaling, your screenshots show the common blurriness render issue more than anything else I believe. Apart from that there is clearly a size difference but I agree that it's quite close. I think it's good to be detailed oriented but I'm not sure the fetish around Latex rendering is warranted.
I agree with you entirely fwliw. For me it's not a fetish particularly, the spacing just looks too wide in that one case and the comparisons if anything confirm that. "Too wide" is of course entirely a matter of personal opinion but I can't see myself switching to something I don't prefer the output of. I may well change my mind in future and I'm probably going to give typst a go at some point, because looking at the…
In any case, Typst seem so much nicer to use that I think it's OK to let go of some minor details...
Earlier quoted context omitted.
You have a Mac with fractional scaling, your screenshots show the common blurriness render issue more than anything else I believe. Apart from that there is clearly a size difference but I agree that it's quite close. I think it's good to be detailed oriented but I'm not sure the fetish around Latex rendering is warranted.
I think the size difference was just me being careless with zoom levels in different apps. I thought it was enough to make the point, since you can compare the space sizes to the character sizes. I put another comparison here: https://imgur.com/a/aZRx6fs , this time with same font size and zoom level. Anyway I agree that looking exactly the same as Latex is not particularly desirable, but it helps for convincing Late…
In this new screenshot the rendering is perfect and one can't really tell any difference.
As for Latex I think it's a strong desire to belong to a special club that makes people use it and try to stick to the very specific look. It does render math equation nicely, but the rest isn't anything special, especially compared to modern font/techniques.