lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

non-technical help for spacing issues


From: Graham Percival
Subject: non-technical help for spacing issues
Date: Tue, 26 Oct 2010 06:32:33 +0100

This is directed at people saying "I can't do anything to help..."

As per my comment #4 in
  http://code.google.com/p/lilypond/issues/detail?id=1290
, we could really use an advanced user (or developer) to help with
tweaking the default values for the new spacing code.

REQUIRED
- desire to get 2.14 out the door, and a few hours of spare time.  I'd
say 2-10 hours?
- knowledge of tweaks (particularly "style sheets", aka \layout {
\context {}}) stuff
- knowledge of the old 2.12 spacing behaviour is a plus
- familiarity with a moderately large body of scores (say, more than
10?) a plus.  This could either come from your own work, or mutopia,
or whatever.
- familiarity with git changelog messages and the mailing list
archives is a plus.

NOT REQUIRED
- no C++ or scheme knowledge required
- ability to compile source from git is a plus, but not required.  If
you need a more recent version than 2.13.37, I'll compile+upload a
special binary just for you


Basically, just try compiling your scores (and any problematic scores
reported by users) with the new spacing code.  If/when something
breaks, then make a \layout { \context{}} thing and change some
overrides until it stops breaking.  Whenever you add an override,
check that it doesn't break any of your other scores.  You'll want to
do this as a separate \include file, of course.
This will be a good test of the new spacing docs -- be warned that you
might find incorrect or missing information in the currently-only
docs.  Well, you won't actually *find* missing information, of course.
 Otherwise it wouldn't be missing.  :)   make an honest attempt to
figure out any problems by yourself, by looking at the git commit
messages and/or emails on lilypond-devel, but if you can't figure out
how to do something, it's fundamentally a problem of the docs, not you
personally.  So don't feel shy about complaining.

Cheers,
- Graham



reply via email to

[Prev in Thread] Current Thread [Next in Thread]