PrestoBlogs™ work by mirroring the look and feel of your company website. However, if your website relies on special web fonts, your PrestoBlog™ may not be able to use them. As a result, you might notice different fonts on your PrestoBlog™, or even gaps where characters from that special font would normally appear.
Fortunately, there are a few workarounds that may help to resolve this problem. These workarounds will depend on your web font setup.
1. Fonts on my site are hosted by a 3rd party font provider
Ensure that your Presstacular domain (blog.yourcompany.com) has permission to access and render the fonts. This normally is done either through your font provider's website, or by contacting your font provider through email.
In some cases, the font provider may be unable to provide access to your PrestoBlog™ domain. Unfortunately, in these cases, there is no workaround and our recommendation is to try an alternative font provider that offers this feature.
2. Fonts on my site are hosted locally
Issues with fonts sourced from your own domain tend to be related to webserver configuration issues. Specifically the webserver configuration needs to grant permission to your PrestoBlog™ domain such that fonts can load successfully.
Instructions for the two most popular webserver's are provided below. If you're using something else, you should be able to find equivalent instructions within the documentation for your specific webserver.
AddType font/ttf .ttf
AddType font/eot .eot
AddType font/otf .otf
AddType font/woff .woff
Header set Access-Control-Allow-Origin "*"
For Microsoft's IIS:
<?xml version="1.0" encoding="utf-8"?>
<add name="Access-Control-Allow-Origin" value="*"" />
3. Your fonts are embedded within your stylesheet or html
We've never seen a problem with inline fonts before, but if you have rendering issues while using such fonts we'd like to hear about them. Please contact firstname.lastname@example.org so we can investigate and determine a viable solution, if any.