I definitely want to get more involved with lilypond development! Of
course there is always the question if I'm brilliant enough :-)))
[http://lilypond.org/web/devel/participating/]
I think I could work in one of these tasks:
> BUILD-MEISTER
> BUG-MEISTER
> NEWSLETTER EDITOR
But I prefer to wai
Hi,
I don't know the correct geometry terminology, but piece is always placed
below composer and opus, like
composer
opus
piece
===
===notes===
I would find it more natural (and space saving!) to write piece and opus at
the same y positio
[EMAIL PROTECTED] writes:
> > relying on the TeX backend. That implies minimal font encoding
> > handling.
>
> Be careful to made a distinction between font and input encoding! Use
Now that we've dived into this matter, we understand the
distinction.
> > We have not yet found the trick to let
> If we want to replace [La]TeX titling kludges (in lilypond.py), we
> must at the very least offer something that is capable of printing
> our own examples (Les N'er'eides, S"angers Morgenlied) without
> relying on the TeX backend. That implies minimal font encoding
> handling.
Be careful to ma
[EMAIL PROTECTED] writes:
> > This release marks the end of an era for me. For the past years I've
> > hacked on LilyPond during my (PhD)study and unemployment. Tomorrow, I
> > will start a regular job as logistics consultant, which means that
> > from now on I won't be able to fix LilyPond bugs wi
> This release marks the end of an era for me. For the past years I've
> hacked on LilyPond during my (PhD)study and unemployment. Tomorrow, I
> will start a regular job as logistics consultant, which means that
> from now on I won't be able to fix LilyPond bugs within the hour.
Congratulations on
