If you have a custom font that you need to use in your PDF ticket, you can edit the HTML template to use it. Follow the instructions under the "Modifying the HTML/Liquid Code" section on the Customizing Your PDF Ticket help page to learn how to edit the template directly. This advanced feature requires some knowledge of HTML, CSS, and Liquid templates.
The PDF renderer supports most HTML and CSS options you'd have in a browser, with minor caveats, so you can load the font as normal using the "@import" and "@font-face" CSS directives to load an external font from a URL. For example:
@import url('http://fonts.googleapis.com/css2?family=Noto+Sans+JP&display=swap');
@font-face {
font-family: 'Noto Sans JP';
src: url('http://fonts.googleapis.com/css2?family=Noto+Sans+JP&display=swap');
font-weight: normal;
}
and then using the new "Noto Sans JP" font family throughout the rest of the template:
A crucial caveat to the PDF renderer capabilities, it only supports URLs with the "HTTP" protocol, no "HTTPS," and so in our example, we loaded the font using the "HTTP://" prefix.
That's it; you can now load a custom font in your PDF ticket. If you need any help, feel free to contact us.