David Kastrup <d...@gnu.org> writes: > "m...@mikesolomon.org" <m...@mikesolomon.org> writes: > >> Hey all, >> >> I'm not too good at writing convert-ly rules. Is there a model I can >> use for replacing a property with another? Specifically, I'd like to >> write a patch changing: >> >> TupletBracket.staff-padding >> >> to: >> >> TupletBracket.bracket-staff-padding >> >> as one cannot currently use the side position interface callbacks on >> TupletBrackets because staff-padding in the tuplet-bracket-interface >> works differently than staff-padding in the side-position-interface. >> >> Lemme know if anyone has a good solution. Otherwise I'll hack away... > > Probably allow arbitrary space around the period, namely \s*\.\s* in the > middle. If you want to support the old-style override/revert syntax, > things are much more complex: you'd probable be best off picking the > rule actually converting _into_ xxx.xxx syntax as a template. > > However, I'd lean towards "it's your own fault if you did not convert, > even if the old behavior still works" stance regarding convert-ly in > this particular case.
Clarification "it's your own fault if you did not convert" from \override TupletBracket #'staff-padding to \override TupletBracket.staff-padding I was not trying to imply that you don't need a convert-ly rule at all. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
