The following site is a SharePoint site in one of my Microsoft 365 tenants, and I know I am on macOS. font-family: "Segoe UI", "Comic Sans MS", "Segoe UI Web (West European)", "Segoe UI", -apple-system, BlinkMacSystemFont, "Roboto", "Helvetica Neue", sans-serif
Because of its unique design characteristics and its universal availability, you can always inject “Comic Sans MS” into the font family, and visually identify where it applies. Another benefit of using font icons is that, in case you change the theme from light to dark, the icons are updated as well, depending on the theme. Microsoft probably thinks that’s ‘simpler’ for users but it’s not because now the true font is totally hidden.
Here’s an example from Word 365 where the font name definitely does NOT match the font used for the emoji. Atom symbol in Segoe UI Symbol, Deja Vu Sans, Symbola.svg 323 × 99 15 KB.
About me segoe ui light.png 678 × 178 10 KB. 'Microsoft' written in Segoe UI font (not a Microsoft logo).svg 1,872 × 351 4 KB.
Thanks to Comic sans this made debugging of font loading easy. An easier solution I found is to use font icons, already predefined in the fonts Segoe MDL2 Assets and Segoe UI Symbol, the best part is you can bind the font size to a particular value, depending upon the screen size everything else is taken care of. The substituted font (Segoe UI Symbol) should appear in the font list if you select just that character. google fonts segoe ui code example Example: google fonts css Check out the font names and change finger paint to another font name to how different google font appears on webpage. The following 30 files are in this category, out of 30 total. Here is an example from my iOS device: Left card: default visual fonts. Or just click the same link on the Mono page. In the list of fonts shipped with Win7 you'll find Segoe UI v5.01 with a 'License' link. Search the Ascender site using the handy search box in the upper right corner.
font-family: "Font 1", "Comic Sans MS", "Font 2" I didn’t say that Microsoft fonts install on Apple device but, Segoe font is being sent with the report therefore it will be available when you view the report on the iOS device. The MS link is confusing, because it links to Segoe UI Mono, not Segoe UI.
So the “debug font family” then looks something like this. It is distinguishable from its predecessor Tahoma and the OS X user interface font Lucida Grande by its rounder letters. One trick I used in the past to make sure a font gets rendered correctly was to add a font that doesn’t look similar to the others. Sample: Segoe UI ('User Interface') is a member of the Segoe family used in Microsoft products for user interface text, as well as for some online user assistance material, intended to improve the consistency in how users see all text across all languages. In general fallback fonts looks similar so most user or developer might not be able to see and the difference between correct and failing font. This approach also makes it sometimes hard to debug. For example, you’d want to add "02B0-"036F, or at least \hat, to the range of all the math alphabets if you wanted to use the combining accent.This approach is an excellent fallback mechanism of the web, making sure that the Browser at least renders a similar font if the perfect font is unavailable. If you want Segoe UI specifically, you can select all the symbols it contains with the range= option of \setmathfont, with another font such as Fira Math as your fallback for the rest.