I agree, it would be great for custom fonts to be added into the business such that they become portable.
For the mean time though, I’m happy to use that naming syntax as it does solve it and shouldn’t be too much work to adapt to a potential future font method.
Thanks very much for the help!
In case others run into the issue, using this workaround you have to set the font weight in the name used in font-family, as well as within the font-weight style attribute. So for me, starting from:
<td style="font-family: Jost; font-weight: bold; font-size: 32px">{{ title }}</td>
you can see I was aiming to use the Bold weight, so the new line used is:
<td style="font-family: 'Jost Bold', Jost; font-weight:bold; font-size: 32px">{{ title }}</td>
Without that font-weight style attribute also set to ‘bold’, the preview View uses the Regular weight font, whilst the PDF output uses the Bold weight.