[EMAIL PROTECTED] (David ) writes:
> 
> > > Another thing that I don't understand att all is the context/translate
> > > stuff.  It's pretty hard to realize what contexts LilyPond will
> > > automatically insert in my score.  If I have a \context StaffGroup <
> > > \context Void < ... > >, it will add a Staff etc. And somewhere it
> > > seems to add an OrchestralScore or something also.
> > 
> > It is documented in the user manual, in the section "Notation
> > Contexts"; could you be more precise what part of the explanation you
> > don't understand? 
> 
> I guess it boils down to that I still haven't managed to build the
> documentation....  Currently I've come so far as to having pnmcrop
> core dump on me.

If you've found a bug, you should submit a bugreport.  Have you check
if this applies to you?

        The version of @file{pnmtopng} that is distributed with RedHat 5.1 and
        5.2 contains a bug: pnmtopng is dynamically linked to the wrong
        version of libpng, which results in cropped images.  Recompile it from 
        source, and make sure that the pnmtopng binary is linked statically to 
        the libpng that is included in libgr.  RedHat 6.0 does not have this 
        problem.

> I can't say I really understand contexts.  Is it possible to define
> your own contexts?

Yes.

> And is there any difference between your own
> contexts and the built-in (and automatic) ones?

Technically, there is no distinction between automatic and user
defined contexts; the automatic ones are loaded from
ly/engraver.ly. For practical purposes it is better  not to rely on
your own contexts, since they might not work if some implementations
are changed.

However, I think that giving users a possibility to define their own
contexts might be useful in some cases.


-- 

Han-Wen Nienhuys, [EMAIL PROTECTED] ** GNU LilyPond - The Music Typesetter 
      http://www.cs.uu.nl/people/hanwen/lilypond/index.html 

Reply via email to