Hi Didi, On Wed, May 5, 2010 at 6:00 PM, Didi & MiMi Kanjahn <[email protected]> wrote: > > I'll try again to explain the font selection problem: > > The line 3 should look the same as in line 2 (see the Word pdf) > - the glyph shapes of these two fonts are for all practical > purposes the same ('Khmer Busra' is an updated version of 'Khmer > Mondulkiri book'). However, in the pdf-file line 3 looks the > same as line 4, so Lilypond took that font instead. There is a > possibility that Lilipond took yet another font alltogether > (though unlikely), because I have (too) many fonts with similar > names on my system.
Sorry for the delayed response. I am unable to confirm the precise problem, but I *suspect* that this problem is related to the way Pango handles fonts. The PangoFontDescription structure within Pango identifies the keyword "book" as a specific font weight, so your font is being processed as having "Khmer Mondulkiri" for the font-family identifier and "book" as the font weight. If you rename your "Khmer Mondulkiri book" font to something different (maybe add an extra "o": "Khmer Mondulkiri boook"), do you have the same results? > A couple years ago, with a much earlier version of Lilypond I > noted that if a font name includes a number (e.g. '.Mondulkiri A > 5'), this number was ignored and a different font (I presumed it > was '.Mondulkiri A') was actually rendered. I don't know if this is the same problem or not. But if you notice it again, let us know. Thanks, Patrick _______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
