Re: post-GDP doc team
Me too! Graham, despite all the grumping, you've managed to pull off what none of the previous maintainers/hackers managed to do: train a disorganized band of users into a lean mean documentation machine. My hat's off! Many thanks for all the hours you put in, and we hope to see you around from time to time. On Mon, Jul 28, 2008 at 7:53 PM, Neil Puttock <[EMAIL PROTECTED]> wrote: > 2008/7/27 Graham Percival <[EMAIL PROTECTED]>: > >> Neil: having a specific "technical help guy" is *very* useful; as >> I'm sure you've discovered, keeping up to date on all this is a >> full-time (volunteer) job by itself. Please take a look at >> technical-todo.txt on the GDP page, and copy all those issues to >> your own list. If anything doesn't make sense, ask me about it... >> although some of those issues were from a year ago, and may not >> still be valid. I'm going to take down that page as soon as I've >> heard that you've got it. > > Got it; I'll have a look through it over the next few days and drop > you a line if there's anything I'm unsure about. > > I can only echo the sentiments already expressed, Graham; you'll be > sorely missed. Hopefully some of your dedication and commitment has > rubbed off on us all so we can maintain the high standards you've set > for the docs. > > Regards, > Neil > > > ___ > lilypond-devel mailing list > lilypond-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/lilypond-devel > -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: \put-adjacent only works using Scheme markup
On Mon, Jul 28, 2008 at 8:36 PM, Neil Puttock <[EMAIL PROTECTED]> wrote: > Hi everybody, > > I've been trying to do a snippet for \put-adjacent in > define-markup-commands.scm, but it doesn't work using \markup because > there's no parser tag defined for the signature > MARKUP_HEAD_MARKUP0_SCM1_SCM2_MARKUP3. > > I see three options as a solution to this: > > 1. extend the parser just for this command; > > 2. pass the Scheme values (axis and direction) as a pair so we can use > MARKUP_HEAD_SCM0_MARKUP1_MARKUP2, which is admittedly rather > inelegant; > > 3. remove it from define-markup-commands.scm and convert it to a Please add a SCM0_SCM1_MARKUP2_MARKUP3 signature and use that. For uniformity, the markups always go last. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: post-GDP doc team
On Mon, 28 Jul 2008 11:58:37 +0200 "Francisco Vila" <[EMAIL PROTECTED]> wrote: > Just to be absolutely clear, people with git access can push the GDP > changes directly in git from now on? The people mentioned in this email thread, yes. :) > 2008/7/27 Graham Percival <[EMAIL PROTECTED]>: > > > I will continue to handle the other GDP contributors until Aug > > 18th > > Here I understand that "other" are the ones not in the to: header of > the message, and therefore we must not disturb you anymore. I am very > sorry if mu understanding of all the meanings of this message is not > fully clear from the very beginning. Not at all; I'm glad that you asked. It's not so much a question of "disturbing"; it's just that I don't think you six need me directing you personally any more. It's time for you to "leave the nest". (I don't know if there's a similar phrase in Spanish: the idea is that young birds must eventually learn how to fly on their own, and there's nothing the parent birds can do to help them at that stage) Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GDP: only 3 weeks left
On Mon, 28 Jul 2008 16:48:39 -0600 "Andrew Hawryluk" <[EMAIL PROTECTED]> wrote: > On 7/27/08, Graham Percival <[EMAIL PROTECTED]> wrote: > > Andrew: I know I asked you this a few days ago, but I've forgotten > > already -- are we ready for the second draft? And do you have any > > experience/interest in Winds? I don't have anybody down for that > > section yet. > > I think we're ready for the second draft of keyboards. Ok, done. > I have some experience writing for and playing winds, so I can clean > it up and add some references (unless someone else has already started > on it). Great! Carl, Jonathan: don't worry about winds then; focus on rhythms. It's a much larger section, anyway. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
\put-adjacent only works using Scheme markup
Hi everybody, I've been trying to do a snippet for \put-adjacent in define-markup-commands.scm, but it doesn't work using \markup because there's no parser tag defined for the signature MARKUP_HEAD_MARKUP0_SCM1_SCM2_MARKUP3. I see three options as a solution to this: 1. extend the parser just for this command; 2. pass the Scheme values (axis and direction) as a pair so we can use MARKUP_HEAD_SCM0_MARKUP1_MARKUP2, which is admittedly rather inelegant; 3. remove it from define-markup-commands.scm and convert it to a utility function so it can still be used for figured bass formatting (though this ignores the remote possiblity that somebody might have used the command in its Scheme form). Any thoughts as to the best course of action; possibly one I haven't thought of? :) Regards, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: post-GDP doc team
2008/7/28 Trevor Daniels <[EMAIL PROTECTED]>: > Neil, are you willing to help when I have questions about how > things work? I can and have looked at source code to try to > find answers, but sometimes (well, actually, usually) it's too > opaque to help much. Docs that are wrong are worse than no > docs, and sometimes I have doubts that what I am writing is > correct. Of course, Trevor; I'm happy to be of assistance if there's anything you're unsure about. Regards, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: post-GDP doc team
2008/7/27 Graham Percival <[EMAIL PROTECTED]>: > Neil: having a specific "technical help guy" is *very* useful; as > I'm sure you've discovered, keeping up to date on all this is a > full-time (volunteer) job by itself. Please take a look at > technical-todo.txt on the GDP page, and copy all those issues to > your own list. If anything doesn't make sense, ask me about it... > although some of those issues were from a year ago, and may not > still be valid. I'm going to take down that page as soon as I've > heard that you've got it. Got it; I'll have a look through it over the next few days and drop you a line if there's anything I'm unsure about. I can only echo the sentiments already expressed, Graham; you'll be sorely missed. Hopefully some of your dedication and commitment has rubbed off on us all so we can maintain the high standards you've set for the docs. Regards, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GDP: only 3 weeks left
On 7/27/08, Graham Percival <[EMAIL PROTECTED]> wrote: > Hi, GDP contributors! > > Andrew: I know I asked you this a few days ago, but I've forgotten > already -- are we ready for the second draft? And do you have any > experience/interest in Winds? I don't have anybody down for that > section yet. > I think we're ready for the second draft of keyboards. I have some experience writing for and playing winds, so I can clean it up and add some references (unless someone else has already started on it). Andrew ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [PATCH] MIDI command line option
2008/7/27 Han-Wen Nienhuys <[EMAIL PROTECTED]>: > Looks good to me. > > You may want to change the default for windows. I'm not quite sure how to achieve this; if there's a check for windows which alters the option at runtime, how can a user override this either in a .ly file or using the command line? Or is this a GUB issue? Regards, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: post-GDP doc team
It is difficult for me to answer a message like this. My English is rather LilyPond-specific, and I cannot use adequately words as owe, deserve and so on. I am sure that you know what I mean. Maybe the best hommage I can do for you is to try, by all means, to finish vocal.itely in three weeks. Unfortunately, I cannot ensure this, because I have to finish a small book (LP-related) for my first year PhD course, before september. After this, I will have much more time to spend. My real life work has changed very much, no webpage of my institution anymore, no Organology, no Score Typesetting, no Internet for Musicians. Only Chamber Music from now on. :-( This means much more time for LilyPond. I'd like to help in maintaining of the docs if it is possible. Translating into Spanish will soon reach a point in which only sporadic maintaining from time to time will be really necessary (I hope). There are large chunks of untranslated docs, though. Just to be absolutely clear, people with git access can push the GDP changes directly in git from now on? Graham: Good Luck. I have learned soo much from you! Thank you. 2008/7/27 Graham Percival <[EMAIL PROTECTED]>: > *Patrick, *Jonathan: please email patches to Neil; he'll apply them > to git for you. I'm happy to sponsor you for direct git access, > once we figure out how to handle git for doc-writers (see > the "separate git tree for docs" email). (...) > Maybe this is just a summer blip (everybody's on > vacation) It is. But different people have different spare time in different months of the year. > From now on, I'm not going to force myself to do anything for you > guys, so if I'm not in the mood to read about Rhythms or Fretted > strings, I'm not going to. This sounds as you are really, really tired. You have demonstrated a big big strength, willing and energy. Have a rest and you will see things of another colour. > Francisco: I don't know if you want to keep on working on the > English docs after GDP. Yes, as I said. > I highly doubt that vocal.itely will be > finished within 4 weeks, but after that's done you might want to > switch back to translating. I Have to translate, that's what I joined for. Remember, there are 400 million of spanish-speaking potential users out there waiting for a free software solution to music typesetting in their own language. > However, like Carl, I hope you'll > still review/comment on other doc work. Count on me, you all guys. > I will continue to handle the other GDP contributors until Aug > 18th Here I understand that "other" are the ones not in the to: header of the message, and therefore we must not disturb you anymore. I am very sorry if mu understanding of all the meanings of this message is not fully clear from the very beginning. Cheers! Again, Good Luck. Yours, -- Francisco Vila. Badajoz (Spain) http://www.paconet.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: [PATCH] Re: Octavation syntax consistency
Reinhold Kainhofer wrote Sunday, July 27, 2008 11:28 AM Am Donnerstag, 24. Juli 2008 schrieb Graham Percival: On Thu, 24 Jul 2008 23:32:08 +0200 > > Shouldn't that really be \octave #x since other commands are in > > English? > > Probably yes, but lilypond had already an \octave function, which > performed an octave check. It was only renamed to \octaveCheck a few > days ago, so I don't want to reuse that function name yet. Otherwise > legacy .ly files might run into problems. The term "ottava" is well-understood in English. I didn't even realize the term was originally German... I suppose we could use "\octavation" instead, though. Before I commit, I'd like to sort out the naming issue: - -) \octave is somehow ruled out by the old \octave (check) function - -) \ottava is inconsistent with the other (English) commands (and to me somehow sounds like absolute, not relative octavation) - -) \octavation sounds good to me What do you think? I'd vote for \octavation, which is also closer to the deprecated #(set-octavation ...). Renaming before the commit is really easy (I'll just search and replace in the patch before applying). Pity about \octave. As we can't use that (yet) my vote is for \ottava. Cheers, Reinhold Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: post-GDP doc team
Graham Percival wrote Sunday, July 27, 2008 9:40 AM Hi Trevor, Patick, Jonathan, Carl, Francisco, and Neil, I'm now finished my thesis, course work, and everything I need to get done until my thesis defense on Aug 19th. That's really good - not many people have three weeks to spare! However, this has caused me to feel immensely fatigued and unenthusiastic about lilypond work. Hardly surprising, given the effort you've been expending, and that's just what we can see on LilyPond work! You need at least a month's rest now, and you certainly deserve it. You've taught many of us an awful lot, and the LP community owe you a great debt. After GDP, I anticipate that we'll have 6 doc writers left: Trevor - LM 1-5, NR 3-6. *Patrick - NR work *Jonathan - NR work Carl - NR work and devel Francisco - possibly NR work, possibly translating Neil - LSR updating, general technical fixit guy Anyway, I'd urge you to read each other's sections -- and if you can't find any problems, send a one-line "looks good to me!" email. Speaking from experience, it really sucks when you've finished a 40-hour job and nobody says anything about it. Yup :( OK, I'll do my bit at reviewing. Invidual notes: Trevor: you know much better than I how LM 3-5 and NR 3-6 look. Do whatever you want before 2.12 is out, and then continue doing whatever you want. I always have ;) Seriously, it's looking increasingly unlikely that I'll get NR 5 into decent shape before end-Aug, as progress at the moment is painfully slow due to other activities. My goal at the moment is to resolve the FIXMEs and bring the standard up to at least that of 2.10. Patrick: please finish NR 1.3, 1.6, and then spend 2-3 hours on the formatting for NR 3 input.tely. I told Trevor focus on the material and ignore formatting issues. Thanks, Patrick. There are a couple of TODOs left, and I didn't even start to think about index entries, refs, snippets, etc. Feel free to modify anything else, too - another viewpoint is always good. Neil: having a specific "technical help guy" is *very* useful; as I'm sure you've discovered, keeping up to date on all this is a full-time (volunteer) job by itself. Neil, are you willing to help when I have questions about how things work? I can and have looked at source code to try to find answers, but sometimes (well, actually, usually) it's too opaque to help much. Docs that are wrong are worse than no docs, and sometimes I have doubts that what I am writing is correct. Cheers, - Graham Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
