(New page: <noinclude>''Or, where is that funny glyph taken from?''{{CompactHeader|fonts}} </noinclude> Sometimes all the '''fontconfig''' substitution and composing magic makes it hard to identify ...) |
No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
<noinclude>''Or, where is that funny glyph taken from?''{{CompactHeader|fonts}} | <noinclude>''Or, where is that funny glyph taken from?''{{CompactHeader|fonts-sig}} | ||
</noinclude> | </noinclude> | ||
Sometimes all the '''fontconfig''' substitution and composing magic makes it hard to identify the font files responsible for a mis-rendering. The font family applications typically display is the requested family, not what this request has been resolved to for a particular glyph. | Sometimes all the '''fontconfig''' substitution and composing magic makes it hard to identify the font files responsible for a mis-rendering. The font family applications typically display is the requested family, not what this request has been resolved to for a particular glyph. | ||
Looking up this glyph in the '''gucharmap''' application, using the same font family, is usually sufficient to learn where it's taken from. '''Gucharmap''' will display the origin font when you right-click on a glyph | Looking up this glyph in the '''gucharmap''' application, using the same font family, is usually sufficient to learn where it's taken from. '''Gucharmap''' will display the origin font when you right-click on a glyph. | ||
[[Image:SIGs_Fonts_QA_gucharmap.png | center | gucharmap screenshot]] | |||
Note, however that '''pango'''-enabled apps will not substitute glyphs on a per-glyph basis, but will try to take surrounding glyphs into account. Thus they may not use exactly the same rules as ''gucharmap'', and you may need to check several fonts in '''gucharmap''' before finding where a glyph origin. | |||
{{admon/tip|Pango language order|The language priority order that pango uses to render text can be set with the environment variable <code>PANGO_LANGUAGE</code>. For example setting <code>PANGO_LANGUAGE</code> to <code>"ja:zh:ko"</code> would prefer Japanese fonts, then Chinese and then Korean.}} | |||
<noinclude> | <noinclude> | ||
{{:Fonts_SIG_signature}} [[Category:Fonts | {{:Fonts_SIG_signature}} [[Category:Fonts and text QA]]</noinclude> | ||
Latest revision as of 19:48, 27 June 2008
Or, where is that funny glyph taken from?
Sometimes all the fontconfig substitution and composing magic makes it hard to identify the font files responsible for a mis-rendering. The font family applications typically display is the requested family, not what this request has been resolved to for a particular glyph.
Looking up this glyph in the gucharmap application, using the same font family, is usually sufficient to learn where it's taken from. Gucharmap will display the origin font when you right-click on a glyph.
Note, however that pango-enabled apps will not substitute glyphs on a per-glyph basis, but will try to take surrounding glyphs into account. Thus they may not use exactly the same rules as gucharmap, and you may need to check several fonts in gucharmap before finding where a glyph origin.
The language priority order that pango uses to render text can be set with the environment variable
PANGO_LANGUAGE. For example setting PANGO_LANGUAGE to "ja:zh:ko" would prefer Japanese fonts, then Chinese and then Korean.
The Fonts SIG takes loving care of Fedora fonts. Please join this special interest group if you are interested in creating, improving, packaging, or just suggesting a font. Any help will be appreciated.