On Tue, 12 Aug 2008 20:21:19 -0700 "Patrick McCarty" <[EMAIL PROTECTED]> wrote:
> *NR 1.6.2.1 Staff symbol > > This section is describing every single way to modify the properties > of StaffSymbol. The only content that doesn't involve \override > commands is the explanation of \stopStaff and \startStaff. Should I > continue using this structure even though it violates GDP policy? If > not, what content should remain in the main text? Leave that material there, but don't more stuff like it. There are a few NR subsubsections that go into such details (setting automatic beams comes to mind). > *NR 1.6.2.2 Ossia staves > > I have collected four different methods of creating ossia staves from > the mailing lists, etc. They are all attached and produce identical > output. Should I include all of these methods in the main text, or > should I describe a general strategy and put these (or more exciting > versions of them) in @snippets? I'm not convinced that \stopStaff and \removeEmptyStaff are good ways of creating ossia. My hope is that the advanced users / developers can discuss this and reach some consensus, and then you'd document those 2-4 good solutions in NR 1.6.2.2. Cheers, - Graham _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
