Relevant Products: Exclaimer Cloud - Signatures for Office 365 | Exclaimer Cloud - Signatures for G Suite
Scenario
You are using Exclaimer Cloud to deploy your signatures and would like to create a signature template that uses a Custom Font type, without using the Render as Bitmap option.
Resolution
To achieve this, you need to use a technique called 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.
If someone receives an email that includes your signature defined with a custom font, and they don't have that font type installed, the next available font type will be used.
Example of Fallback fonts:
Adding Fallback fonts
To add Fallback fonts:
- Once you have created your signature with the required elements, select any element to access its properties. The Properties window for the selected element is displayed.
This example displays the Table element properties:
- At the top of the Properties window, you'll see a 'breadcrumb trail' for related elements - you need to select the first entry in this trial, which will always be Signature.
Example:
- Click Manage to ensure that the uploaded fonts have been removed.
- From the Font Family drop-down list, select (or type) the required font type.
In this example, we've selected Calibri:
- You can add any number of Fall Back fonts, in the sequence that you wish them to be considered if the first font can't be used. Each font type should be separated by a comma.
Example:
We recommend: The final two font types in the signature are common fonts, such as Arial and Sans-Serif (or Serif, if you are using a font type similar to Times New Roman):
- Save your changes.