Re: Sometimes order is significant

[Wols Lists]

On 26/05/15 15:02, Knute Snortum wrote:
> Thanks for the reply and the cheat sheet.
> 
The way I look at it, is to look at the *meaning*, not the *representation*.

First, you need the note, eg "C above middle C", which is c''. Next
comes whether to display any accidentals, which is a property of the
note, as is the length. So logically those could be swapped, but I think
lily says they have to be in that order.

Finally come all the ornamentations - accents, markups, dynamics, etc
which have no tight binding to the note, only the note location, so can
come in any order. I have my own consistent pattern, but that's just to
make it easy for me, lily doesn't care.

Cheers,
Wol
> 
> Knute Snortum
> (via Gmail)
> 
> On Mon, May 25, 2015 at 2:56 PM, Nathan Ho <address@hidden
> <mailto:address@hidden>> wrote:
> 
>     On Mon, May 25, 2015 at 2:38 PM, Nathan Ho <address@hidden
>     <mailto:address@hidden>> wrote:
> 
> 
>         This cheat sheet shows many note syntax elements in the correct
>         order:
> 
>         http://joramberger.de/files/lilypond_sheet_2.18_en.pdf
> 
>         It seems that all the components starting with string number can
>         be placed in any order.
> 
> 
>     Here's a more formal answer which can be found by delving into the
>     LilyPond grammar.
>     
> http://www.lilypond.org/doc/v2.18/Documentation/contributor/lilypond-grammar
> 
>     To oversimplify, a monophonic note is divided into a "simple_event"
>     and any number of "post_events." A simple_event breaks down like so:
> 
>     - pitch (note name + octave)
>     - forced accidental markers
>     - octave check
>     - note duration and multiplier
>     - \rest
> 
>     Beams, slurs, articulations, fingerings, etc. all fall under
>     post_events, which can occur in any order.
> 
>     Regards,
>     Nathan
> 
> 
> 
> 
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>