Update on this thread - I’ve recently confirmed that @Justin_Axure 's suggestion of simply adding one entry to the Share > Fonts Tab section that links to the all.css file DOES HAVE UNDESIRED SIDE-EFFECTS. Here’s how to reproduce:
-
In Axure -> Share -> Fonts Tab -> Add just one font - Font Awesome’s all.css font (https://pro.fontawesome.com/releases/v5.10.1/css/), and leave font mappings unused.
-
Go to https://fontawesome.com/icons -> Click the Info circular icon in the upper right to see the copy link below each icon -> click the copy link on an icon -> In a text box in axure, paste that icon that’s in your clipboard, then highlight it and set the font to Font Awesome 5 Pro, and set the font style to SOLID. The icon should be a solid color now.
-
Publish to share.axure.com, and view.
You’d expect to see that icon in SOLID style.
What you actually see is that icon in BOLD style (thicker lines, but not solid shaded).
The reason this happens is the font mappings aren’t present, so the browser interprets SOLID as BOLD. However, if you follow the steps in the original post, the SOLID style will be correctly interpreted.
Also note that the links to these fonts is buried behind fontawesome.com -> Profile Menu -> Font Awesome CDN.
Originally it was buried even deeper, but after I posted this:
https://forum.axure.com/t/font-awesome-cdn-is-being-sunsetted-what-now/ and linked someone from the Font Awesome’s support team to it, they decided to move it to a slightly more discoverable place and removed the language indicating the CDN is going away. So, we’ll see what comes next.
In the meantime, unless I’m missing something, it appears the font mappings are still required.