On 8/30/07, Graham Percival <[EMAIL PROTECTED]> wrote: > Trevor Bača wrote: > > Sure, I'd be happy to. (And if winds up being too complicated, then > > that's certainly OK; just keep me in check!) > > > Go nuts. :) My only concern is the vertical space of the printed > music on the page. For the lilypond input, do whatever you want. > Overrides, scheme, Turing machine simulation, whatever. > > If I'm reading right then I think you're thinking of like a "headword" > > example above each section in the manual? So there would be 1 fancy > > example for 8.1.1, another fancy example for 8.1.2, and a third for > > 8.1.3, and so on? > > > A "headword" for each *section*, not subsection. There's X lines of > fancy example for 8.1. Nothing for 8.1.1, 8.1.2, 8.1.3, etc. Just to > make sure we're on the same page, open up 8.1 Text. I want this to look > like this: > ------------------------------------- > > 8.1 Text > This section explains how to include text (with various formatting) in > your scores. > To write accented and special text (such as characters from other > languages), simply insert the characters directly into the lilypond > file. The file must be saved as UTF-8. For more information, see Text > encoding <cid:[email protected]>. > > ---------------- > ---fancy------ > ---music--------- > ----example----- > --------------------- > > * Text scripts <cid:[email protected]> > * Text and line spanners <cid:[email protected]> > * Text spanners <cid:[email protected]> > > > > I'd like to see at least "* Text scripts" when I look at this page in > the docs; that's the reason for the vertical constraint.
OK, sure thing. I'll take a look over the long weekend here in the US ... :-) -- Trevor Bača [EMAIL PROTECTED]
_______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
