Custom Fonts in Web Maps - Available for Popups but Not Labels

MGAL

Our org has been using Map Viewer Classic, and labeling features using Garamond (not a default font) is nothing new for us. Take our offices feature layer for example - I can open it with Map Viewer Classic and see Garamond listed as an available font (this is available because I installed it...).

 

If I open the same layer in the new Map Viewer, the labels revert back to Arial, and Garamond is no longer available as a font choice for labels. 

HOWEVER

If I add this HTML snippet to the pop up (in Map Viewer),

<p>
    <span style="font-family:Garamond;">This is Garamond!</span><br>
    This is the default font!
</p>

Garamond shows in the pop up. This tells me that Garamond is available, but it's not populating correctly? 

What do I need to do in order to make Garamond available in Map Viewer as a font choice for labels? 

 

Thanks

-Mike

MGAL

I figured it out. You have to add the Garamond.ttf files to your Portal's font folder. This is different from system fonts - every time the Portal service boots up, it looks in this folder & checks for ttf files. For each new .ttf, the system will automatically create a series of ."pbf" files. The new JS API (4.x) uses these so-called "font glyphs" in the Map Viewer. Once the pbf files are created, the original ttf files are deleted.

I'll update this post once I am able to safely restart my Portal service.

Update: I'll admit, AI chats can seem really convincing. Still hunting for an answer.