Octavation syntax consistency (was: grand predefined-command thread)

2008-06-28 Thread Valentin Villenave
2008/6/28 Graham Percival <[EMAIL PROTECTED]>: > If there's any command renamings or new commands that you have in > mind (mostly from doc work), please post it now. If there isn't > sufficient opposition in the next few days, I'll add the commands. This is not really a predef, but for the past

Re: Octavation syntax consistency (was: grand predefined-command thread)

2008-06-28 Thread Reinhold Kainhofer
Am Samstag, 28. Juni 2008 schrieb Valentin Villenave: > This is not really a predef, but for the past couple of weeks I've > been trying to implement an easier syntax for octavations, e.g. > > \octava 1 > or > \octava #1 > > instead of > > #(set-octavation 1) > > Such a command would be much more c

[PATCH] Re: Octavation syntax consistency (was: grand predefined-command thread)

2008-06-28 Thread Reinhold Kainhofer
Am Samstag, 28. Juni 2008 schrieb Reinhold Kainhofer: > Am Samstag, 28. Juni 2008 schrieb Valentin Villenave: > > This is not really a predef, but for the past couple of weeks I've > > been trying to implement an easier syntax for octavations, e.g. > > > > \octava 1 > > or > > \octava #1 > > > > in

Docs: Parenthesized tempo marks

2008-06-28 Thread Reinhold Kainhofer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I just realized that with the new \tempo function it's very easy to generate parenthesized tempo marks: Simply use an empty text, i.e. \tempo "" 4=60 will produce (quarter = 60) That might be mentioned in the docs, too, since it's quite common t

convertrules.py with decorator update for today's git

2008-06-28 Thread Wilbert Berendsen
This is an updated patch for the convertrules.py script, rewritten using a decorator (rationale and info at http://lists.gnu.org/archive/html/lilypond-devel/2008-06/msg00163.html ) best regards! Wilbert Berendsen -- LilyKDE, LilyPond for KDE: http://lilykde.googlecode.com/ convertrules-decor

Re: Markup snippet breaking docs (\rotate)

2008-06-28 Thread Neil Puttock
2008/6/28 Graham Percival <[EMAIL PROTECTED]>: > On Fri, 27 Jun 2008 21:51:00 +0100 > "Neil Puttock" <[EMAIL PROTECTED]> wrote: > >> The following snippet works fine: >> >> @lilypond[verbatim,quote] >> \\markup { foo \\rotate #180 bar } >> @end lilypond >> >> Any idea what's going wrong? > > Maybe

Re: Markup snippet breaking docs (\rotate)

2008-06-28 Thread Graham Percival
On Sat, 28 Jun 2008 15:27:10 +0100 "Neil Puttock" <[EMAIL PROTECTED]> wrote: > 2008/6/28 Graham Percival <[EMAIL PROTECTED]>: > There's one exception to \command { } though; \combine can only take > two markups as arguments, rather than a list. Do you think it's worth > noting this in its descript

Re: GDP question about piano templates & dynamics

2008-06-28 Thread Neil Puttock
2008/6/25 Graham Percival <[EMAIL PROTECTED]>: > Neil, > > If you're not busy finishing the markup stuff, could you take a > look at this? I don't think it's a good idea to implement a PianoDynamics context until it's working properly; while the centring works fine, there are problems with the hor

Re: GDP question about piano templates & dynamics

2008-06-28 Thread Andrew Hawryluk
I will leave the Piano docs as they are with respect to dynamics and the templates, at least for now. In the meanwhile, I am looking forward to the New_dynamic_engraver very much! Andrew On Sat, Jun 28, 2008 at 9:02 AM, Neil Puttock <[EMAIL PROTECTED]> wrote: > 2008/6/25 Graham Percival <[EMAIL P

Re: [PATCH] Re: Octavation syntax consistency (was: grand predefined-command thread)

2008-06-28 Thread Valentin Villenave
2008/6/28 Reinhold Kainhofer <[EMAIL PROTECTED]>: >> Well, you don't need to be skilled too much, but that part about "a sec" is >> definitely true ;-) Attached is an example. Yes, so did I try but I misread the source code (I thought I'd have to use ly:export, and a 'void music expression). >>

Re: GDP question about piano templates & dynamics

2008-06-28 Thread Valentin Villenave
2008/6/28 Neil Puttock <[EMAIL PROTECTED]>: > I wish that were the case; got any tips on working faster (without > causing massive breakage)? :) Similarly, I'm looking for tips on how to write sensible docs on hairy stuff such as 1.8 Text :) (I've just seen Nicolas has made my font-size docs nea

Re: GDP question about piano templates & dynamics

2008-06-28 Thread Neil Puttock
2008/6/28 Andrew Hawryluk <[EMAIL PROTECTED]>: > I will leave the Piano docs as they are with respect to dynamics and > the templates, at least for now. In the meanwhile, I am looking > forward to the New_dynamic_engraver very much! Hehe, I wouldn't get too excited; the new engravers are already i

Re: GDP question about piano templates & dynamics

2008-06-28 Thread Andrew Hawryluk
Well, at least that explains what the New_fingering_engraver is! As long as the engraver is under construction, is it easy to make the skyline 'disappear' between dynamic marks so that it behaves more like the figured bass engraver (see image)? Currently the entire row of dynamic marks are shifted

Re: grand predefined-command thread

2008-06-28 Thread Patrick McCarty
On Fri, Jun 27, 2008 at 9:40 PM, Graham Percival <[EMAIL PROTECTED]> wrote: > > If there's any command renamings or new commands that you have in > mind (mostly from doc work), please post it now. If there isn't > sufficient opposition in the next few days, I'll add the commands. Okay, here are m

Re: GDP question about piano templates & dynamics

2008-06-28 Thread Neil Puttock
2008/6/28 Andrew Hawryluk <[EMAIL PROTECTED]>: > As long as the engraver is under construction, is it easy to make the > skyline 'disappear' between dynamic marks so that it behaves more like > the figured bass engraver (see image)? Currently the entire row of > dynamic marks are shifted verticall

Re: grand predefined-command thread

2008-06-28 Thread Valentin Villenave
> On Fri, Jun 27, 2008 at 9:40 PM, Graham Percival <[EMAIL PROTECTED]> wrote: >> >> If there's any command renamings or new commands that you have in >> mind (mostly from doc work), please post it now. If there isn't >> sufficient opposition in the next few days, I'll add the commands. \sustainDo

GDP status July 2008

2008-06-28 Thread Graham Percival
There's two months left in GDP. I'd like to reserve one month for final clean-up and whatnot, so that leaves one month for the bulk of the work. Here's my list of what I'm hoping people to finish in July. If you don't think you can accomplish it, let me know; I should be able to shift some peopl

Re: GDP status July 2008

2008-06-28 Thread Graham Percival
On Sat, 28 Jun 2008 09:32:53 +0100 "Trevor Daniels" <[EMAIL PROTECTED]> wrote: > I think I can do this by end-Aug (but not by > end-July) provided I can leave any detailed > formatting stuff for someone else to tidy up. That's fine; I'm not concerned about. Just make sure the docs compile. :)

Re: GDP status July 2008

2008-06-28 Thread Trevor Daniels
Graham, you wrote There's two months left in GDP. I'd like to reserve one month for final clean-up and whatnot, so that leaves one month for the bulk of the work. Here's my list of what I'm hoping people to finish in July. If you don't think you can accomplish it, let me know; I should be ab

Re: GDP question about piano templates & dynamics

2008-06-28 Thread Graham Percival
On Sat, 28 Jun 2008 19:43:44 +0200 "Valentin Villenave" <[EMAIL PROTECTED]> wrote: > 2008/6/28 Neil Puttock <[EMAIL PROTECTED]>: > > > I wish that were the case; got any tips on working faster (without > > causing massive breakage)? :) Focus. Let's say that you're working on \underline: - does

Re: Docs: Parenthesized tempo marks

2008-06-28 Thread Graham Percival
Thanks. Carl will bear this in mind when he gets around to this section. Cheers, - Graham On Sat, 28 Jun 2008 14:21:26 +0200 Reinhold Kainhofer <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I just realized that with the new \tempo function it's very easy to