On Fri, 01 Oct 2010 13:15:21 -0700, Keith E OHara <k-ohara5...@oco.net> wrote:
On Fri, 01 Oct 2010 03:20:48 -0700, <lilypond-user-requ...@gnu.org> wrote:
All,
How about the other proposed changes?
Do they help to give new users a starting point for the types of scores you
write?
Do they steer new users away from issues and traps?
2) Change the key signature to something other than C.
3) Enter notes as written on parts, as opposed to concert pitch.
[ . . . ]
5) Add \midi{}.
6) Remove redundant parts
Having heard no complaints, a snippet with these changes is in the LSR awaiting
approval.
4) Add some introductory text
Short comments in the snippet itself point out the specifics, so the
introductory text is again very brief:
"This template demonstrates the use of nested @code{StaffGroup} and
@code{GrandStaff} contexts to sub-group instruments of the same type together, and a way
to use @code{\transpose} so that variables hold music for transposing instruments at
concert pitch."
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
