Re: Kievan_ligature_engraver for normal staff

[Svetlana Lobanova]

Hi, Thomas!

Thank you a lot for your effort! Seems I need to get closer with lilypond's 
internals and programming )))

I made two variables \startFix with your code and \stopFix like that:

stopFix = {
  \override NoteHead.stem-attachment = ##t
  \override NoteHead.after-line-breaking = ##t
}

It's buggy, as I my knowledge doesn't allow to find default values, but it 
works for turning fix on and off. That would be enough in most cases and I can 
use my old spacing hacks where kievan ligatures don't help.

-- 
Best wishes, 
Svetlana


21.06.2016, 00:22, "Thomas Morley" <address@hidden>:
> Hi Svetlana,
>
> 2016-06-16 12:42 GMT+02:00 Svetlana Lobanova <address@hidden>:
>>  Thomas, thaks a lot! Your workaround is wery interesting and fits for 
>> simple cases.
>>
>>  Now I thought carefully about all complex examples which are not fixed this 
>> way.
>>  1) Eights (rare) and sixteens (wery specific use, there is even no special 
>> sign for a single sixteenth note in kievan scores) have beams and flags, 
>> which also should be shifted.
>>  2) Dotted notes should have shifted dots.
>>  3) Sometimes I use \prall and it also is not in place this way.
>>
>>  Looking at all of these I wonder if we have to move all of them forwards or 
>> just move a noteheads and slurs backwards?
>
> Well, my approach using 'extra-offset was already last resort ...
>
>>  Also, could we use the fix only inside ligatures and not outside of them? 
>> In ideal case I wouldn't put single notes inside ligature brackets, and 
>> there is no problem with shifted notes ouside of ligatures already.
>
> Kievan_ligature_engraver and kievan-ligature-interface doesn't offer
> any useful pointers, p.e. I've no clue what 'primitive is supposed to
> be ...
>
> Sorry, but I have no reasonable idea to get forward
>   Harm