I'm using Polylang in my own blog, and handling multilingual through subdomains.
In this context (when you have your main language at http://example.com and other languages at http://lang.example.com) fonts, like other resources, are loaded from the main domain (http://example.com), through Cross-Origin Resource Sharing (CORS).
Unlike stylesheets or scripts, fonts are blocked because no Access-Control-Allow-Origin header is present on the requested resource, therefore the subdomain is not allowed to access the resource.
One solution is setting the Access-Control-Allow-Origin header for the required resources through Apache or nginx (see David Walsh), but we should find a solution for all our users.
I'm using Polylang in my own blog, and handling multilingual through subdomains.
In this context (when you have your main language at http://example.com and other languages at http://lang.example.com) fonts, like other resources, are loaded from the main domain (http://example.com), through Cross-Origin Resource Sharing (CORS).
Unlike stylesheets or scripts, fonts are blocked because no
Access-Control-Allow-Origin
header is present on the requested resource, therefore the subdomain is not allowed to access the resource.