Hi list,

on Mutopia Project and other such sites there are quite a few older (as
in version 2.12 or 2.13) lilypond sources.

convert-ly is my friend. However there regularly are settings and commands
that convert-ly does not deal with. Examples would be:

  % keep 32nd notes in their beams
  #(revert-auto-beam-setting '(end 1 32 4 4) 1 8)
  #(revert-auto-beam-setting '(end 1 32 4 4) 3 8)
  #(revert-auto-beam-setting '(end 1 32 4 4) 5 8)
  #(revert-auto-beam-setting '(end 1 32 4 4) 7 8)

or

    \override VerticalAlignment #'max-stretch = #ly:align-interface::calc-
max-stretch

or

    \override VerticalAxisGroup #'minimum-Y-extent = #'(-3 . 4)

or

  between-system-padding = #0.1

The last one had been changed be convert-ly into

  obsolete-between-system-padding = #0.1  system-system-spacing #'padding = 
#(/ obsolete-between-system-padding staff-space)  score-system-spacing 
#'padding = #(/ obsolete-between-system-padding staff-space)

(all in one line) and I'm not quite convinced that is correct (as it
creates an error when processed by 2.19.52).


I'm prepared to deal with all of these manually. For this I'd like a
pointer as to where I could search for a description what these features
were and what did replace them.

My assumption is that revert-auto-beam-setting simply is no longer needed
with current versions of lilypond while VerticalAxisGroup.minimum-Y-extent
has been replaced by something else (what?)

For the max-stretch set of properties/functions I have no clue at all.

Could someone provide a pointer as to where I could look?

Alternatively I'd be happy to raise all such questions on this list and
hope for someone knowledgeable to provide answers... ;)



Kind regards,
Michael
-- 
 Michael Gerdau       email: m...@qata.de
 GPG-keys available on request or at public keyserver

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to