laurmaedje

9 ms·

1.
by laurmaedje 10mo ago
It seems to have started slowly. For me, Github releases have failed to serve requests for hours already.
2.
by laurmaedje 11mo ago
The backslashes are not really relevant to the problem discussed in the post. The ambiguity between symbols and argument-taking macros exists just the same in LaTeX. Consider: $ f_\abs{x} $ $ f_\pi{x} $ LaTeX just happens to do
3.
by laurmaedje 11mo ago
Pandoc [1] can convert LaTeX to Typst. [1]: https://pandoc.org/
4.
by laurmaedje 11mo ago
(Author of the post and issue comment here.) The preferences there were honestly rather ad-hoc w.r.t to the pull request and the approach the pull request took. And (as the author laid out), the PR was a rather ad-hoc solution for a problem
5.
by laurmaedje 11mo ago
While not really related to the math topic, let me answer this: - You can add an arbitrary number of trailing `[..]` blocks and they are just trailing arguments. So 2 & 3 are really the same. - 3 & 4 are different because argument l
6.
by laurmaedje 1y ago
That's fixed, thanks to a community contribution! [1] For what it's worth, Typst did have font subsetting from the start, but it was rather bad for CFF-flavoured OpenType fonts. The same contributor has recently put a lot work int
7.
by laurmaedje 2y ago
As one of the core developers, I would say "stubbornly sticking to their interpretation" is not entirely fair. I am open to changing this, but I don't want to do it hastily --- because that means changing things twice. Figuri
8.
by laurmaedje 2y ago
(Typst dev here.) That's one of the next big things we plan to work on once Typst 0.12 has shipped. :)
9.
by laurmaedje 2y ago
If you're talking about weak widow/orphan support for headings in particular, that will finally be fixed in Typst 0.12.
10.
by laurmaedje 2y ago
Hey, I'm one of the Typst devs and author of the issue. The reason there is no logging yet is because we want to get it _right_ rather than landing a permanent temporary solution. And there were simply more urgent things to do so far.
11.
by laurmaedje 2y ago
Good point! lr should support lengths in addition to ratios. Should be easy to add.
12.
by laurmaedje 2y ago
I'm not sure what you're referring to because when justification is enabled Typst uses almost the same line breaking algorithm as TeX. [1] One problem we had was over-eager hyphenation. We've addressed that recently. [2] [1]:
13.
by laurmaedje 2y ago
Hey, Typst dev here. Regarding HTML export: It's not bikeshedding. It's more that, while we consider HTML as pretty important, we decided that fixing and improving the layout engine first was even more important. Basically getting
14.
by laurmaedje 3y ago
Those are supported, too.
15.
by laurmaedje 3y ago
#set text(lang: "de") would set it to German for instance. See also: https://typst.app/docs/reference/text/text/#parameters-lang
16.
by laurmaedje 3y ago
Typst handles hyphenation very similarly to TeX. https://github.com/typst/hypher https://laurmaedje.github.io/posts/hypher/
17.
by laurmaedje 3y ago
I'm one of the Typst devs and I do agree with you here. LaTeX has a lot of trouble with accessibility because it's hard to retain semantic information through layers of macros. However, I think we are in a better starting position
18.
by laurmaedje 3y ago
I have a question about the point on highlighting in particular. With a subscription-based model, don't you lose out on the ability to partially highlight a file based on the visible ranges in the editor? Unless you re-subscribe to the
19.
by laurmaedje 4y ago
If you want to write the letters phi, you can write p h i if you mean implied multiplication or "phi" if it should be a single unit. In general, Typst's syntax is designed to make every sequence of characters expressible, jus
20.
by laurmaedje 4y ago
Yes, SVG support is built-in.
21.
by laurmaedje 4y ago
It's built completely from scratch, but the math layout algorithm is based on TeX.
22.
by laurmaedje 4y ago
It's not a code example. It's Typst code that is used to calculate the fibonacci numbers that are displayed in the table.
23.
by laurmaedje 4y ago
On the shaping side, support should be quite good as rustybuzz replicates harfbuzz results 1-1. (I think, it passes the whole test suite.) Regarding higher-level text layout: We have implemented BiDi, shaping, line breaking, reshaping, and
24.
by laurmaedje 4y ago
You raise many interesting problems. While I have answered each one individually below, the general answer is: Typst is still a young project and while its already possible to create papers and other documents in it, lots of stuff is still
25.
by laurmaedje 4y ago
I would argue that font rendering and text shaping are completely separate problems. The font renderer doesn't need to know about directions, language, locales and scripts and using one of these simple libraries doesn't mean that
26.
by laurmaedje 4y ago
Double slash for stacked fractions was also my first impulse upon reading your post. Currently, it starts a line comment even within math, but that could be changed. We'll consider it!
27.
by laurmaedje 4y ago
This is interesting feedback. I imagine defining stackedness through global styling wouldn't help, as you would like to decide on a case-by-case basis which one is preferrable?
28.
by laurmaedje 4y ago
> What licence is typst under? We will open source in March, probably with a permissive license, but that's not yet definitively decided. > Will it be able to reference page numbers from a different book dynamically? (so if book-
29.
by laurmaedje 4y ago
For the purposes of this thesis I coded the citation style and numbering using Typst's introspection system and handwrote the references. However, we have also written a BibLaTeX-compatible citation system called hayagriva [1] for Typs
30.
by laurmaedje 4y ago
We have switched back and forth on this because we also wanted to stay as close to Markdown as possible, just for the familiarity. However, the fact that Typst also uses the hashtag to indicate an inline expression led to too much confusion

More ›