You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The rendering of package README.md files on the Typst Universe site uses Cascadia Mono to render code blocks. Unfortunately the site seems to be useing a webfont version of this font with a limited subset of characters available. According to the CSS, the font itself is is served from https://typst.app/assets/fonts/CascadiaMono-Regular-Sub.woff2.
This font seems to have been subsetted in such a way that it does not have the characters needed to render Turkish properly. I checked some French and German packages I found with non ASCII characters inside code blocks in their README.md files and they seemed fine, e.g. I confirmed that [öğçüé] and others were fine. Missing seem to be at least [ıİşŞğĞ]. This makes for some very sub-par rendering of my decasify package:
Given that many other diacritics are supported and the upstream font has support for Turkish, I would like to request a new subset be generated with more complete coverage, possibly without any language subset optimizations at all so that future language additions don't run into the same problem.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
The rendering of package README.md files on the Typst Universe site uses Cascadia Mono to render code blocks. Unfortunately the site seems to be useing a webfont version of this font with a limited subset of characters available. According to the CSS, the font itself is is served from https://typst.app/assets/fonts/CascadiaMono-Regular-Sub.woff2.
This font seems to have been subsetted in such a way that it does not have the characters needed to render Turkish properly. I checked some French and German packages I found with non ASCII characters inside code blocks in their README.md files and they seemed fine, e.g. I confirmed that
[öğçüé]
and others were fine. Missing seem to be at least[ıİşŞğĞ]
. This makes for some very sub-par rendering of my decasify package:Given that many other diacritics are supported and the upstream font has support for Turkish, I would like to request a new subset be generated with more complete coverage, possibly without any language subset optimizations at all so that future language additions don't run into the same problem.
The text was updated successfully, but these errors were encountered: