Laurenz
Reopening until Typst 0.12 is released.
Doesn't seem like the switch to Libertinus Serif fixed this. :/ Not sure whether this is related: https://github.com/alerque/libertinus/issues/511 cc: @alerque
Congratulations on your newborn. I hope everything turns out well!
Is this with the 0.13.1 release or the latest main branch? If it's the former, please also try the latter. PDF export changed significantly.
Writing non-Latin (e.g. Chinese) text without a configured font leads to unpredictable font fallback
> Maybe just move Noto Sans CJK to the higher position of fallback list. There isn't really one. It goes into last resort fallback here, where all bets are kinda...
Writing non-Latin (e.g. Chinese) text without a configured font leads to unpredictable font fallback
I'm not sure whether it's helpful to make it slightly less bad. Relying on font fallback will always be worse than having properly configured fonts. I think there's things we...
Writing non-Latin (e.g. Chinese) text without a configured font leads to unpredictable font fallback
Not sure. The web app has little say in font selection. It just provides a FontBook. So this might require changes in Typst.
Writing non-Latin (e.g. Chinese) text without a configured font leads to unpredictable font fallback
I'm not sure whether it's really better to make it slightly less bad because then it might be just good enough to not configure a proper font, but still bad.
Writing non-Latin (e.g. Chinese) text without a configured font leads to unpredictable font fallback
I guess it also depends on whether you just have a bit of Chinese text or a document full of it. In the former case, it might be enough.
I think only allowing explicit ones is the way to go. I changed this because it was annoying when autocomplete popped up immediately after a comma.