No edit summary |
No edit summary |
||
Line 7: | Line 7: | ||
[[Image:SIGs_Fonts_QA_gucharmap.png | center | gucharmap screenshot]] | [[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. | 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. |
Revision as of 12:40, 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.