[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 1057 in lilypond: Expand issue #218 to provide a practical soluti
From: |
lilypond |
Subject: |
Issue 1057 in lilypond: Expand issue #218 to provide a practical solution |
Date: |
Tue, 13 Apr 2010 13:00:19 +0000 |
Status: Accepted
Owner: ----
New issue 1057 by lemzwerg: Expand issue #218 to provide a practical
solution
http://code.google.com/p/lilypond/issues/detail?id=1057
The solution given in issue #218 is definitely too generic. Look at the
attached example. The `toward-stem-shift' applies to all Script grobs
which is clearly wrong. In particular, accents shouldn't be shifted at
all. Depending on the articulation symbol we need different values.
BTW, looking into the full score of `Wozzeck', I've noticed different
values of `toward-stem-shift', depending on the direction of the beam. See
attached image. I'm not sure whether this happens in polyphonic situations
only.
In summary, assuming we have a Script grob with glyph name `foo', we would
need properties `foo-upstem-shift' and `foo-downstem-shift'. To make life
easier, we should probably provide `default-upstem-shift' and
`default-downstem-shift' which gets used for all glyphs which don't have an
explicitly set shift property.
Attachments:
staccato.ly 835 bytes
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
- Issue 1057 in lilypond: Expand issue #218 to provide a practical solution,
lilypond <=