Page Comparison

...

Font files may require pre-deployment processing to avoid issues loading during PDF generation or printing. Embedding Fonts as base64 data urls works best, as this can be inlined or added directly to precompiled framework CSS for inclusion in your HTML/JS.

Note: On Windows, custom font files are sometimes needed to avoid issues with PDF rendering, as the PDF rendering engine environment only has access to a limited set of fonts, and these are not guaranteed to match the operating system installed fonts. In these cases, fonts can be included using @font-face CSS declarations and relative urls to your fonts, which should be included alongside your HTML/JS resources, for example:

@font-face {
   font-family: 'MyWebFont';
   src: local(''),
       url('resources/myfont.woff2') format('woff2'), 
       url('resources/myfont.woff') format('woff'),
       url('resources/myfont.ttf') format('truetype'), 
       url('resources/myfont.svg#NotoSansKR') format('svg'); 
}
body {
	font-family: 'MyWebFont', Fallback, sans-serif;
}