Re: @lilypond[fragment] question

2010-10-01 Thread Graham Percival
On Mon, Sep 27, 2010 at 11:54 AM, Benkő Pál wrote: >> Nope.  My pet name for Ancient music is "the disaster that nobody >> cares about fixing". > > I do care (well, I am nobody and even I don't care for chant) > and have my pet issues, but I really don't know what other issues > there are - search

Re: @lilypond[fragment] question

2010-09-27 Thread Mark Polesky
Graham Percival wrote: > Nope. My pet name for Ancient music is "the disaster that > nobody cares about fixing". That particular bit should > either be in a Notation appendix, or written out in a full > lilypond example. Well, it's far more accessible to visually-impaired users than a lot of oth

Re: @lilypond[fragment] question

2010-09-27 Thread Benkő Pál
> Nope.  My pet name for Ancient music is "the disaster that nobody > cares about fixing". I do care (well, I am nobody and even I don't care for chant) and have my pet issues, but I really don't know what other issues there are - searching for "ancient" in the issues list gives a very short list

Re: @lilypond[fragment] question

2010-09-27 Thread Graham Percival
On Mon, Sep 27, 2010 at 5:01 AM, Mark Polesky wrote: > Graham Percival wrote: >> Err, yes, I'd forgotten about them.  All "main text" >> @lilyponds, then?  :) > > Haha, stop setting me up: > http://lilypond.org/doc/v2.13/Documentation/notation/typesetting-mensural-music#mensural-clefs Nope. My p

Re: @lilypond[fragment] question

2010-09-26 Thread Mark Polesky
Graham Percival wrote: >>> Oh, sorry. I misread your comment as linking the two... >>> yes, all @lilypond should have [quote]. >> >> Well, not *all* @lilypond instances. Certainly [quote] >> would be bad inside a table. I'm thinking of NR A.2 >> "Common chord modifiers" or NR B. "Cheat sheet". >

Re: @lilypond[fragment] question

2010-09-26 Thread Graham Percival
On Sun, Sep 26, 2010 at 05:53:15PM -0700, Mark Polesky wrote: > Graham Percival wrote: > > Oh, sorry. I misread your comment as linking the two... > > yes, all @lilypond should have [quote]. > > Well, not *all* @lilypond instances. Certainly [quote] > would be bad inside a table. I'm thinking o

Re: @lilypond[fragment] question

2010-09-26 Thread Mark Polesky
Graham Percival wrote: > Oh, sorry. I misread your comment as linking the two... > yes, all @lilypond should have [quote]. Well, not *all* @lilypond instances. Certainly [quote] would be bad inside a table. I'm thinking of NR A.2 "Common chord modifiers" or NR B. "Cheat sheet". - Mark

Re: @lilypond[fragment] question

2010-09-26 Thread Graham Percival
On Sun, Sep 26, 2010 at 8:14 PM, Mark Polesky wrote: > Graham Percival wrote: >>> Should I just replace "fragment" with "quote", or are >>> there reasons to keep "fragment"? >> >> No, because [quote] means [indent this image]... > > Did you look at the examples in the html?  I think they > should

Re: @lilypond[fragment] question

2010-09-26 Thread Mark Polesky
Graham Percival wrote: >> Should I just replace "fragment" with "quote", or are >> there reasons to keep "fragment"? > > No, because [quote] means [indent this image]... Did you look at the examples in the html? I think they should all be indented, no? - Mark _

Re: @lilypond[fragment] question

2010-09-26 Thread Graham Percival
On Sun, Sep 26, 2010 at 7:39 PM, Mark Polesky wrote: > changing-defaults.itely:2497 > changing-defaults.itely:2552 > changing-defaults.itely:2966 > changing-defaults.itely:2983 These are untouched from GDP. > rhythms.itely:1342 delete [frament] > rhythms.itely:1354 delete [fragment] > rhythm

@lilypond[fragment] question

2010-09-26 Thread Mark Polesky
I found some suspicious instances of @lilypond[fragment,...] that were missing the "quote" option: $ cd Documenation/notation $ git grep -n -e "@lilypond\[.*fragment.*\]" --and \ --not -e quote -- changing-defaults.itely rhythms.itely changing-defaults.itely:2497 changing-defaults.itely:2552 ch