> I was rather suggesting that someone other (me) is unnable to write a tutorial
> due to the un-frozen feature set. Of course the _basic_ elements will be the
> same (ie basic mudela) but for example various property-names is subject to
> change quite vigorously before 1.4 I understand.
> But now I know that a feature freeze is not likely, I got the answer to my
> question, thank you =).
I have also began to think about rewriting the documentation,
but I don't dare promise anything yet since I'll probably have
a quite busy fall anyway.
I think much work can be done already now on describing the
basic features and, not the least, to find a better structure
for the documentation. Completing the list of properties can
be done later.
The person writing the documentation should be well familiar with
Lilypond from some larger projects and should preferably also have
a basic idea of the implementation, since some detective work will
be needed to find and understand all the different features.
> I haven't tested this with the latest, but some 1.3 had grave problems with
> full score processing. I entered some bars of Schuberts unfinished and
> had to really give up on harakiri etc. This report will help noone ofcourse,
> just an example, maybe I will come back with a better report.
I've typeset a fairly large score by N.W. Gade (you can view a
version produced with Lilypond 1.2.x at www.gmd.de/Misc/Music)
and I recognize the problems with HaraKiri, but I can assure
you that those problems and basically all other problems I've
had with 1.3.x have been solve in the latest versions. The
only (!?) feature I miss at the moment is the possibility to
place the dynamics above the staff lines.
> Just a question off the top of my head: Is it possible to have barlines
> across whole scores ? I mean like in a StaffGroup or GrandStaff but _between_
> StaffGroups as well ? Should include example, I know, maybe later.
Certainly, just move the Span_bar_engraver to the ScoreContext.
This configurability is one of the strongest features of Lilypond,
but also one of the major problems when it comes to writing a
pedagogical documentation.
/Mats
