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
Hi!
I've recently noticed that the Google Fonts CSS API v2 has an option to not only specify the subset parameter for a font but also a text one: this is a (URL-enconded) string that contains the characters you want to use from the font and only these will be downloaded. For example, the following URL will result in only the number glyphs being downloaded for the Source Sans Pro font's bold weight, saving a lot of bandwidth by not downloading a full Latin subset of it.
Unfortunately, this module does not seem to support this parameter so I ended up manually importing the font for now, but I would love to see it support this part of the API, too -- especially since I cannot use some of the module's convenient features this way, like automatic prefetching.
If specified, text should be used instead of subset, details here.
Is there any plan to implement the handling of this parameter?
The text was updated successfully, but these errors were encountered:
Hi!
I've recently noticed that the Google Fonts CSS API v2 has an option to not only specify the
subset
parameter for a font but also atext
one: this is a (URL-enconded) string that contains the characters you want to use from the font and only these will be downloaded. For example, the following URL will result in only the number glyphs being downloaded for the Source Sans Pro font's bold weight, saving a lot of bandwidth by not downloading a full Latin subset of it.Unfortunately, this module does not seem to support this parameter so I ended up manually importing the font for now, but I would love to see it support this part of the API, too -- especially since I cannot use some of the module's convenient features this way, like automatic prefetching.
If specified,
text
should be used instead ofsubset
, details here.Is there any plan to implement the handling of this parameter?
The text was updated successfully, but these errors were encountered: