How to use custom fonts without rendering as bitmaps

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 Fall Back Fonts. These are a series of font types that start with your Custom Font but fall back on to other fonts that are similar if your custom font isn't available.  

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 Fall Back Fonts:

Adding Fall Back Fonts

To add Fall Back fonts:

1. 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:
   
   
   
2. 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:
   
3. Click Manage to ensure that the uploaded fonts have been removed.
   
   
4. From the Font Family drop-down list, select (or type) the required font type.
   In this example, we've selected Calibri:
   
5. 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):
   
6. Save your changes.