[EMAIL PROTECTED] writes:
> > If I understand the situation correctly, it seems like we just need to
> > assign Unicode codes to each glyph before saving (e.g., as a .dfont or
> > .ttf).
>
> Well, that's what I'm not sure about. I think (hope) that just moving
> chacacters out of the control-char
Hey! I found Jan's demonstration on the list showing how to specify
exact position /length of stems:
\property Voice.Beam \override #'positions = #'(-0.6 . -0.5)
works for the first two bars, I suspect I'll have to adjust all the way
when notes change. (No new screenshot yet).
And positio
Kieren Richard MacMillan writes:
> Having spent a little more time in pfaedit, I think I now understand
> what needs to be done. I would love to help the lilypond cause if I
> can, so if you want, I would be pleased to pfaedit the fonts so that
> they are "acceptable" and then make them available
On Sunday 14 December 2003 13:17, Richard Lyons wrote:
> Another small problem.
>
> I have a tie in a phrasing slur.
[...]
Okay, the tie has now decided to print even across the time signature --
don't know what I did wrong before... But I still need to deepen the
slur (to get round string nota
Another small problem.
I have a tie in a phrasing slur. Unfortunately the tie crosses a new
time signature, so lilypond drops it. I put a slur instead, but the
slur crashes through the phrasing slur. I think I should be able to
flatten the slur, but my best guess,
\once \property Voice.Sl
On Sunday 14 December 2003 03:39, Graham Percival wrote:
[...]
> Ahh, another LilyPond cellist! There's quite a few of us. :)
My daughter is the cellist. But good to know I'm in the right place.
> a4^\open
>
> It's in the section of the manual that deals with articulations (and
> fingerings).
SUMMARY: Am I shortening stems the right way?
Can anyone tell if I do things the best way?
As an exercise for complicated piano voicing I tried to put
down the first bars of Chopin op. 28.1 (C Major Prelude).
As expected I ran into several problems and I would like
some
