On 6/4/10 4:04 PM, "Xavier Scheuer" <x.sche...@gmail.com> wrote:
> 2010/6/4 Frédéric Bron <frederic.b...@m4x.org> :
>
>> added to issue 1029 and to LSR.
>>
>> What next can a frog do for this?
>
> Hi (yeah, me again)! :)
>
> I have no authority in development, nor in bug policy, but I have a
> proposal about how to handle this issue.
>
> Actually I think we could "divide" this issue into 2 separate ones:
>
> 1. short-term fix: change "thumb" definition (avoid-slur . around
> + add other "Fingering" properties that also exists for Script),
> but keeping \thumb engraved by "Script_engraver".
> Here is what I think could be fine:
>
> ("thumb"
> . (
> (script-stencil . (feta . ("thumb" . "thumb")))
> (avoid-slur . around)
> (padding . 0.5)
> (direction . ,UP)
> (slur-padding . 0.2)
> (staff-padding . 0.5)))
>
>
> 2. mid(long)-term fix: transfer \thumb to "New_fingering_engraver".
> Actually I would rather call that "extending New_fingering_engraver"
> It would be also cool to add the possibility for
> "New_fingering_engraver" to support _finger changes_, whose
> currently suggested input is as a TextScript:
> c^\markup { \finger "2 - 3" }
> (see NR 1.7.1).
>
> My suggestion is to kindly ask Frédéric to take care of #1, i.e.
> changing "thumb" definition in Script, and so close this issue 1029.
>
> And open a new issue "Extend New_fingering_engraver" to also print
> \thumb and /custom Fingering markups/ (useful to, for example, finger
> changes), see #2.
>
> What do you think guys of this double proposal?
> Frédéric, Carl, Bug Squad members?
Seems like a good proposal to me. I don't think that there will be
much momentum for extending New_fingering_engraver, but putting it in the
tracker would be great.
We should also add another issue: Change New_fingering_engraver to
Fingering_engraver. We need to get rid of the old Fingering_engraver and
rename New_fingering_engraver to Fingering_engraver. Part of this issue
involves determining what the Fingering_engraver has that
New_fingering_engraver doesn't, if anything, so we don't lose functionality.
Thanks,
Carl
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
