On Thu, Jun 23, 2011 at 1:53 PM, Graham Percival <gra...@percival-music.ca> wrote: > Please stop capitalizing "patch". If you're referring to issue > 1264, the patch broke the build, and in any case it's postponed > until GLISS.
Er, no it didn't. (TBH, I do remember Neil noticing a very minor, unrelated error though.) The only reason why I didn't push forward is because you said it was a GLISS thing... And since it's now integrated in my own framework as a hackish superset on top of LilyPond, I've been happily and selfishly using it for months without feeling the need to unearth it upstream :-) > It might be a good idea to learn some scheme, or at the very least > do some more experimentation. I mean, ultimately what matters is > the quality of the output. Try a few different commands in your > scores, look at the output, and pick the one you like the best. Xavier, this code is actually quite easy to understand; we have two arguments "dynamic" and "string", both of which are actually text strings. The 'tweaks part is only there to add extra horizontal space, based on the string-length of the string argument., and the 'text property of the AbsoluteDynamicEvent we create is, well, the text that will be printed (in this particular case, a markup that include the "dynamic" argument, and the additional "string" as italic text). If you have some time, please do read http://lilypond.org/doc/v2.15/Documentation/extending/scheme-in-lilypond and http://www.gnu.org/software/guile/manual/ it makes for a fascinating reading reading experience, at least if you're anything like me. Feel free to ask me directly if you need more explanations about this code or what I'm using now: http://git.savannah.gnu.org/cgit/opus-libre.git/tree/bin/text.scm#n26 Cheers, Valentin. _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
