On Mon, Sep 20, 2010 at 9:34 PM, Mark Polesky <[email protected]> wrote: > Graham Percival wrote: >>> -...@subheading Other programs can export LilyPond code >>> +...@subheading Other programs that can export LilyPond code >> >> This makes it sound as though the previous programs can >> export lilypond code. Only Denemo falls into that >> category; all the other programs are text editor-types. >> >> Could you just omit this change? > > How about just "Programs that can export LilyPond code"? If > you don't like that I'll just keep the old version.
That's fine. >> Hmm. I know that the current entry for Strasheela uses >> @qq, but I'd rather avoid that. Could you omit the @qq, >> or if you want to totally play by copyright law, ask >> Trevor (off-list) for permission to re-use that sentence >> fragment on our website? Or just write a new one-sentence >> description? > > Since the sentence is almost exactly what Trevor suggested > off-list (I condensed it from two sentences), I prefer to > keep the @qq, but if there's any other reason you don't like > the @qq, let me know. A @qq is a quotation. Are we directly quoting their website? Why? Why can't we just write+use our own description -- especially since it sounds like Trevor already did this? I mean, if he said "sure, go ahead and describe it as a foobazzling the bar", then I'm fine with that description -- but just remove the @qq, and write: foo is a program which bazzles the bar. I'm kind-of applying academic thinking here... when you mention a paper in your "related work", you're not supposed to just quote a sentence from their abstract; you're expected to write your own description of the paper. Dunno why this traditional originated. >> While we're at it, could you write a new description for >> [Strasheela]? Again, I'd prefer to avoid a @qq unless >> it's necessary. If not, I'm happy to do this; I used >> strasheela for my Masters degree. > > I wouldn't know what to write; if you want to write it in > your reply, I'll add it to the patch. I've added it to my TODO list, but I won't get to it until tomorrow. If you want, you can move on with the patch, and I'll change it later. Cheers, - Graham _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
