Re: keyboard-headword.ly

[Neil Puttock]

2008/7/1 Graham Percival <address@hidden>:

> This example gives a warning:
> Preprocessing graphical objects...
> programming error: FT_Get_Glyph_Name () error: invalid argument
> continuing, cross fingers
> programming error: Glyph has no name, but font supports glyph
> naming.
> Skipping glyph U+FFFFFFFF, file
> /Users/gperciva/Apps/LilyPond.app/Contents/Resources/share/lilypond/current/fonts/otf/CenturySchL-Ital.otf
>
> but looks ok at first glance.  Please investigate and file a bug
> report.

This looks like the error Valentin reported earlier; the snippet works
fine for me.

> Speaking of that, if you're interested, I'd love to be able to
> compile all the docs without error messages.  Some examples in
> introduction.itely produce warnings because it's doing weird stuff
> with output (removing all engravers other than note heads, for
> example).  But it would be awesome if everything else could be
> compiled without warnings.
> This unfortuantely requires both a fair amount of technical
> skills, and a fair amount of time.  This is certainly a
> low-priority issue, though -- and if you're not interested, don't
> bother at all.

Certainly some of the warnings could be fixed, but there are also the
interface warnings (e.g. for ancient snippets) which are probably a
bit trickier.

> I'm not certain if you intended this to be used for keyboards
> instead of pitches, but I've added to keyboards for now.

I don't mind where you put it; it's Trevor's snippet from that thread
you mentioned. :)

BTW, I think some of the headwords would look better without ragged-right = ##t.

Regards,
Neil