Does anyone know how to get a list of all fonts th...
# advancedpdf
s
Does anyone know how to get a list of all fonts that NetSuite already has available for us? I see there is an
nsfont
object that is used to load various versions of NotoSans from, but I can’t find the full list of fonts documented in SuiteAnswers. I know I can load my own fonts from the filing cabinet, but I don’t want to do that if a font I want or one very close to it is already available. Thanks!
The only font/font-family that seems to work without being loaded is sans-serif or Helvetica (which appear to be the same)
nsfont.Verdana
also exists and can be loaded like NotoSans. It seems odd for NetSuite to only support three sans serif fonts: Helvetica, NotoSans, and Verdana, but I can’t get any other fonts to work without loading them from the filing cabinet myself.
nsfont.Verdana_Bold
and
nsfont.Verdana_Italic
also exist
m
There's some info about Built-In fonts on page 30 of the BFO User Guide
s
Interesting, thanks @michoel. So the reason we can use Helvetica, Times, Courier, Symbol, ZapfDingbats without linking is BFO provides them. I hadn’t thought about BFO providing them, I assumed that whatever system fonts existed on NetSuite’s servers would be available, but that appears not to be the case. NetSuite adds in Verdana and several versions of NotoSans (and possibly some other serif or monospace fonts, but I don’t really have any need for those) through nsfont, likely just for extended character support. I tried a variety of other common non-serif fonts like nsfont.Arial, but none of them, even Arial, were there. Based on this, unless you want to be limited to such a small selection of fonts, I guess loading your own from the filing cabinet is the way to go. We have been specifying
Arial, Georgia, sans-serif
as the font-family, and I guess it was always just falling back to Helvetica before since neither Arial nor Georgia are actually available. That makes sense since the layouts we did should have worked in Arial, but never looked right in our PDF’s, and now I know why and how to fix it.