Re: Arbitrary accidental glyphs

[Han-Wen Nienhuys]

Ah, ok.  The problem is that the Pango font is 'virtual': pango
decomposes the string into sections each of which can use a different
font.

On Sat, Jul 19, 2008 at 10:51 AM, Graham Breed <address@hidden> wrote:
> Han-Wen Nienhuys wrote:
>>
>> On Thu, Jul 17, 2008 at 11:10 AM, Graham Breed <address@hidden> wrote:
>>
>>>     \override Accidental #'font-name = #"Sagittal"
>>>
>>> in a script, and characters from Accidental's glyph-name-alist can come
>>> from
>>> Sagittal.  The problem is that LilyPond can't retrieve named glyphs from
>>> a
>>> non-standard font.
>>
>> that's wierd.  Lily basically outputs
>>
>>  /glyphname showglyph
>>
>> Postscript code, so it should work for any font that has glyph names.
>
> The code is (scm/output-ps.scm)
>
>
> (define (named-glyph font glyph)
>  (ly:format "~a /~a glyphshow " ;;Why is there a space at the end?
>             (ps-font-command font)
>             glyph))
>
>
> So it's also trying to output a description of the font, which expands to
> include the filename, and a Pango_font doesn't have one.  Changing it to
>
>
> (define (named-glyph font glyph)
>  (ly:format "/~a glyphshow" glyph))
>
>
> means no error gets generated but the output has things like this:
>
>
> /noteheads.s2 showglyph
> 458.9567 -744.0706 moveto
> 0.0500 3.2322 -0.0250 -2.2722 0.0800 draw_round_box
> 9.3556 -746.5706 moveto
> /sharp showglyph
>
>
> It's trying to print the accidentals with the same font as the note heads.
>  The result is garbage.  So how do we tell it to use the Pango_font?
>
>
>                  Graham
>



-- 
Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen