Language Subsets

Information on languages and font subsets.

How this plugin affects subsets?

By default, you don’t have to do anything to support additional language subsets. The same language subsets configured by your themes or plugins will be used.

One difference from Google Web Fonts is that, recently, for modern browsers they simply add all the subsets for all font requests regardless of subset query. While this increases the CSS size, it’s a good method for their CDN which can serve something different to older browsers. But your webhost cannot.

A feature called unicode-range makes this possible. However, for browsers that don’t support unicode-range properly, this would lead to megabytes of unnecessary downloads. So we don’t use this strategy. We add only the subsets explicitly enabled.

Font was working before with your language but stopped after using the plugin?

The above is usually why. This also means your fonts weren’t even rendering for older browsers like IE11, Edge < 17, Safari < 10 etc.

You should configure your theme to set correct language subsets for your font. Most themes have settings related to subsets to be used. Alternatively, you can use Force Language Subsets feature on PRO.

If that doesn’t resolve it, refer to F.A.Q. for more troubleshooting.

Force Language Subsets PRO

To force a language subset, follow these steps:

1. Go to Settings > Self-Hosted Google Fonts.
2. Next to Force Subsets, simply tick the language subsets you wish to force for fonts.
3. Save settings and clear caches.