![]() ![]() Different XP installations may have added fonts, such as Arial Unicode MS, which is shipped with MS Office, and then the problem changes. Testing your demo in a virtual Windows XP, which presumably corresponds to an old out-of-the box XP, Japanese characters are not displayed at all. It is possible that in some context, Chrome might be trying to use rendering technology that fails in (some flavors of) Windows XP. ![]() It may have other effects, and its specification is very vague. It is of typographic nature, and the known and somewhat documented effects relate to kerning and ligatures, which probably don’t apply to Japanese writing anyway. ![]() For example, the following set of packages covers most of existing kaomoji: ttf-freefont, ttf-arphic-uming, and ttf-indic-otf. In any case, the text-rendering property setting can safely be removed (or set to auto, the initial value). Kaomoji are sometimes referred to as 'Japanese emoticons' and are composed of characters from various character sets, including CJK and Indic fonts. I suspect that the setting comes from another source. In that case, change the class names there.Īnd there is no text-rendering setting there either. It may indirectly affect headings, if you heading elements have class attributes coinciding with those used in Font Awesome. I cannot see any CSS code related to headings in the CSS files in the Font Awesome package. But I don’t see how Font Awesome relates to the problem. This trickery mostly works, because the special fonts are served as downloadable fonts with wrong information about character support. Font Awesome uses fontastic trickery that is based using fonts that contain iconic images in place of normal characters, in special fonts. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |