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
Currently, the unicode-range property is only provided for the [weight].css files. I suggest we provide the property for all CSS files so the browser can dynamically filter out unused font subsets.
The text was updated successfully, but these errors were encountered:
The only blocker for this is the lack of information on what unicode-range's certain languages cover. The current information we have is insufficient to determine the optimal ranges for each subset as CJK fonts are split into numbered subsets. So we will need to find a way to analyze the font files for the correct information. Would appreciate some suggestions for this.
Currently, the
unicode-range
property is only provided for the[weight].css
files. I suggest we provide the property for all CSS files so the browser can dynamically filter out unused font subsets.The text was updated successfully, but these errors were encountered: