Hello,

Commits fc1946c290e5f253769a306efff1b0224178aaa5 and 
9e1b534c81e101c449acfa176f923be57cbcaea5 have added a patch in to the Learning 
Manual.

The NR still needs to be done.

Tracker opened http://code.google.com/p/lilypond/issues/detail?id=1197 (thanks 
Phil)

James


-----Original Message-----
From: Trevor Daniels [mailto:t.dani...@treda.co.uk]
Sent: Thu 29/07/2010 23:31
To: James Lowe; lilypond-u...@gnu.org
Cc: Lily-Devel List
Subject: Re: tempo commands not in learning manual
 

Dan Wilckens wrote Thursday, July 29, 2010 2:47 PM


> Hi James,
>
> I mainly thought the tempo command was too hard to find in the 
> documentation--too illogically placed for me to track down easily 
> navigating the notation reference headings (just tried it in the 
> 2.13 doc's, had similar problems before with 2.12 doc's) and I 
> actually couldn't find the command at all in the learning manual 
> in a couple minutes of clicking around the section headings. 
> (Admittedly, in the index it is easy to find.)
>
> My suggestion is to include the \tempo "Allegro" 4=160 type 
> command in the Rhythms section of the Learning Manual, since tempo 
> is fundamental to rhythm, and I didn't find it anywhere else in 
> the learning manual; I'd even put it as early as 1.2.1, along with 
> Clef, Time Signature,

I agree.  A simple example could be included in the same brief
style as the others between Time Signature and Clef in 1.2.1.
This would be easy to do.

> etc., or at least in section 2.1.  And, I'd also suggest it be put 
> somewhere more logical in the Notation Reference as well, since 
> its current location Under Staff Notation->Writing Parts is among 
> the last places I'd think to look to find tempo commands; maybe in 
> section 1.2.3, Displaying Rhythms, alongside Time Signature etc.

I agree with this too.  The Metronome marks section would be
better placed in 1.2.3 immediately after Time signature, but
the move would require some juggling with a number of snippets.
There are higher priority doc items, though.

Trevor




_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to