Relevant Products: Exclaimer Cloud - Signatures for Office 365 | Exclaimer Cloud - Signatures for G Suite
Scenario
You are not sure if the font you have chosen for your signature template design is web safe and available for use in your Exclaimer Signature solution.
Once you have established whether your chosen font is web safe or not, you can implement a font stack into your signature.
If your chosen font is not available across all operating systems, you can create a font stack with a list of fallback fonts.
- Font stacks are used to control how the font will appear to the recipient if they do not have access to your chosen font.
- Fallback fonts allow you to specify websafe alternatives to fall back on if needed. This allows you to control how the signature appears across all devices as you can choose the most similar fallback font to your original font.
For more information, see Web safe fonts and font stacks.
Implementing Font Stack
Follow the steps below to implement font stack into your signature:
- Take the initial Font type you are looking to use. In this example, we use Calibri.
- Create a Font Stack with your chosen fonts, ensuring you separate each font with a comma and space.
Example: Calibri, Candara, Segoe, Segoe UI, Optima, Arial, sans-serif.
Note: If you are not sure which fonts to use, take a look at the CSS Font Stack for a list of fonts that already have font stacks created. - Select the entire signature by selecting the outer edge of the template.
The Signature properties window is displayed:
- In Font Family, remove the current font type and replace it with your Font Stack.
- Once the changes have been made, simply close the window for the changes to take place.