This is because for exporting to PDF, it is necessary to strictly specify required parameters like font-weight, font-style or font-stretch respectively except the correct font-family name for the custom fonts.
Take custom fonts “national” as example, the font family name is “Copyright Klim Type Foundry”.


Following the KB37127, create and deploy the custom font plugin. Sample custom fontNamesPikcer.xml file as below.

But with this KB, it does not include CSS rule. To utilize the new custom fonts in dossiers, users should select the corresponding font family and define its variants. For example, to use “National Bold”, users should choose “National” as font family, and then set Bold.

In the Text Box, currently only Bold and Italic are supported, while Condensed or other font properties are not in the text box editor.
And if just with above setting, simply specify full name in font-family, don’t add properties, like font-with, font-style or font-stretch, such font face rules will only work in Strategy Web/Library. As for exporting dossier to PDF, it is necessary to strictly follow the standards.
To define the CSS rules as follow:
