Font is substituted for no reason

Question

I converted an annotation layer created in ArcMap, and published it as a Map Image Layer from Pro. It gives a warning about fonts, but I have installed the fonts on both my Portal and Server machines. When it renders in Map Viewer Classic, I see it's substituted Arial for the Shadow font.

I know the font is available on the server. See "Astoria" rendered erroneously in Arial here and the Popup with text that I set to Shadow by changing the HTML.

Is there a way to convince Server not to make everything Arial? Maybe a style or css page somewhere??

Here is what the map looks like in ArcGIS Pro, using the map used to publish the MIL. Look at the label "Astoria" in Shadow,

Scott_Tansley · Answer

Logical step would be to find a test candidate who hasn't got the font installed, and see what they get in popups etc.  I think you will find it will become user specific.

Brian_Wilson · Answer

This explains why it shows up in popups, because I did install the font locally so that I could use it in ArcGIS Pro so that I could publish with it. So all my popup test does is prove that (1) Esri does not strip out that particular HTML from the popup and (2) my browser works.  Thanks for explaining that.

For maps Server renders the annotation into pixels in the server and delivers a PNG file to my browser. When the fonts are used in a map image layer, it works. Whatever renders the annotation has a limited idea of what fonts are available, there is probably a list of fonts hard coded into it.

Looks like there are three teams working on this, Pro, MIL, and Annotation. The PRO and MIL teams completed their work. The Annotation team did not.

Therefore from the end user perspective, this is another case where the "correct solution" is to ignore it.

Scott_Tansley · Answer

The thing with the popup is that it's rendered and drawn on each user's machine.  That means the font needs to be installed on each machine.  It's use on the server is for generating Map Image Layers.

The location where we install it does not 'share that over the web' to end users.

I'm not sure if you can embed fonts into a Web App Builder/Experience Builder app.  That's outside of my normal practice.  But typically web developers who want to use specific fonts in an application will host the font as a part of their app so that it's available to the end browser.

Currently, the HTML/CSS will be telling the end users browser to use Shadow, and if Shadow isn't available then the browser will decide what to use.