Re: GOP2-3 - GLISS (final)

[Bernard Hurley]

On Thu, Aug 09, 2012 at 10:05:14AM +0100, Graham Percival wrote:
> 
> 
> ** Subset for first phase
> 
> In greater detail: I’m suggesting that we have multiple rounds of
> syntax stabilization. The proposed elements of current lilypond
> notation which we will stabilize is captured by these two files:
> 
> \version "2.16.0"
> \header {
>   title = "don't overwrite this title"
>   composer = "the lilypond GLISS team"
> }
> \score {
>   \new Staff {
>     \new Voice {
>       \partial 8 d8 |
>       c4 d' e, f'' |
>       \times 2/3 {a4 b c} \grace {d16} d2 |
>       \acciaccatura {b16} c2 \appoggiatura {b16} c2 |
>     }
>   }
>   \layout {}
>   \midi {}
> }
> 
> \version "2.16.0"
> \score {
>   \new Staff {
>     \new Voice {
>       \relative c, {
>         \clef "bass"
>         \time 3/4
>         \tempo "Andante" 4 = 120
>         c2\mp e8 c' |
>         g'2. |
>         \time 6/8
>         \key d \major
>         \tempo "Allegro" 4. = 120
>         f4.\f eisis8 eis r |
>         deses,8 des r e'8 c c,8 |
>       }
>     }
>   }
> }
> 
> and then we guarantee that these files will compile, completely
> unmodified (no convert-ly allowed), for every lilypond 3.x
> version.

This seems a great place to start. I have started to write an
application that will eventually be able to both generate lilypond
code and read a subset of it. The gradual stabilising of lily
will be very helpful.

Bernard