Ok here is where I am confused. There is a structure
for files which makes a file valid.
Then there is a grammar which must also be followed
for the lanuguage of lilypond.
 
I get the feeling after reading the docs that the
structure of lilypond is loose.

What I mean is that it appear (if I am not wrong) that
there are elements that can appear a number of places
in a document and others that can appear only in
certain places.

I want to be able to generalize and also limit the
structure of a basic lilypond file:

lets say a file with a melody only.

If I ask the question what elements must a lilypond
file have or it won't be valid structuraly will I get
an answer?

If I ask for a valid parent child relationship of
elements will I find such a thing?

This issue is compounded for me by most lilypond
examples which use includes or variables x = y
so that it is often hard to see what the structure is.

I am not complaining rather I am trying to understand.

I realize part of my problem comes from my experience
with xml/html where there are strict rules for nesting
and validity and wellformedbness...


A documentation page titled file structure should lay
down some rules for file structure instead of listing
a few of the top level elements.

I for my part find it confusing when an element is not
nested. Although I realize that with lilypond there is
less worry about missing brackets that way.

I will read some more and experiment some more and see
what I come up with.

Aaron
--- Mats Bengtsson <[EMAIL PROTECTED]> wrote:

> (Graham, or someone else, we should really try to
> make sure that
> all commands and reserved words available in
> LilyPond are listed
> in the Index. \layout is one of those missing. Doing
> such an exercise
> would also help identifying what information is
> missing from the manual
> today.)
> 
> Part of an answer to your question can be found in
> the
> sections "Changing context default settings" and
> "Defining new contexts" in the manual. There's also
> some
> information in "Line length", but there doesn't seem
> to be
> any introduction to the concept anywhere. For
> example, I couldn't
> find any information on that you can put a
> \layout{...} block
> on the top level of the file to make it apply to all
> scores in the
> file (or at least within the \book) whereas it will
> only apply to
> the current score if you put the declaration inside
> \score{...}.
> 
>     /Mats
> 
> 
> Aaron Mehl wrote:
> > Hi   all,
> > 
> > In a previous email I asked if layout replaced
> paper.
> > I was told to look at outputs, which I did. The
> paper
> > output section details \paper{}
> > 
> > but I see no mention of \layout {}
> > 
> > where in the docs is \layout discussed?
> > 
> > Thanks
> > Aaron
> > 
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam?  Yahoo! Mail has the best spam
> protection around 
> > http://mail.yahoo.com 
> > 
> > 
> > _______________________________________________
> > lilypond-user mailing list
> > lilypond-user@gnu.org
> >
> http://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> -- 
> =============================================
>       Mats Bengtsson
>       Signal Processing
>       Signals, Sensors and Systems
>       Royal Institute of Technology
>       SE-100 44  STOCKHOLM
>       Sweden
>       Phone: (+46) 8 790 8463                         
>          Fax:   (+46) 8 790 7260
>       Email: [EMAIL PROTECTED]
>       WWW: http://www.s3.kth.se/~mabe
> =============================================
> 



                
__________________________________ 
Discover Yahoo! 
Find restaurants, movies, travel and more fun for the weekend. Check it out! 
http://discover.yahoo.com/weekend.html 



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

Reply via email to