This is a simplified explanation as the real solution considered different languages too. Only if none of these fonts have a glyph for the character do you get the placeholder for a missing glyph. If it can't render a character in the first defined font, it will look to the next in the family and if none provide the character it will look to the ContentControlThemeFontFamily resource. It uses the specified list (family) of fonts on a character by character basis. I don't know if HTML/CSS rendering is cleverer than that (please comment below, if you know) but the XAML text renderer is smarter than just using the same font for everything. If the first specified font is available use that for all the text, if it's not available use the next font, etc. In my head, I always thought of the HTML/CSS specification of multiple fonts as applying all or nothing to the text. FontFamily="Segoe Script,Segoe MDL2 Assets"
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |