make[1]: Entering directory `/home/team/adrian/src/lilypond-1.0.13/debian'
rm -f out/changelog
ln changelog out/changelog
rm -f out/copyright
ln copyright out/copyright
rm -f out/postinst
ln postinst out/postinst
rm -f out/postrm
ln postrm out/postrm
rm -f out/rules
ln rules out/rules
rm -f out/watch
ln watch out/watch
make[1]: Circular out/BLURB <- out/BLURB dependency dropped.
rm -f out/BLURB
ln out/BLURB
ln: cannot access out/BLURB
make[1]: *** [out/BLURB] Error 2
make[1]: Leaving directory `/home/team/adrian/src/lilypond-1.0.13/debian'
make: *** [all] Error 2
I think you might want to consider changing the syntax in \translator
for specifying the name of the context (and maybe give some thought to
the semicolons). You could use "\name Staff" instead of "Staff;" for
example. This would make the content of the \translator block more
consistent with itself. There is a new inconsistency in the use of
semicolons. Inside a \paper, you must now use a semicolon after an
assignment. And it's also now sometimes necessary to have semicolons
after a "}" character. This could be very confusing. At the top
level, the semicolon is not required after assignments. In other
situations, semicolons are illegal after '}'. I think you should
decide: do you want lots of semicolons, or not. If you want
semicolons all over, make them legal (but optional) anywhere that people
might put them (after any close brace, after any keyword, after any
identifier reference, after any identifier assignment), and required
where they are needed to terminate argument lists. If you don't want
semicolons all over the place, make them illegal everwhere except when
they are needed to terminate argument lists. The present intermediate
situation of having them sometimes required arbitrarily, sometimes
optional, and sometimes illegal is very bad, in my opinion.
A while back I complained of inadequate space after repeat symbols and
such. Lately I've noticed that it seems like the space after ordinary
bar lines seems insufficient, particularly when the stem is on the
left side of the note, right next to a bar line. One thought that
occurred to me is that more space could be added around all bar
symbols by increasing their dimensions specified in the font tables.
But maybe this isn't a good solution. In any case, I think that the
spacing around bars should receive some thought at some point.
Is the \output keyword going to be reused? Or should/will it be removed?
foo = 1
\score{
\notes { a }
\paper{ foo = \translator{ \StaffContext}; }
}
produces a bus error. It seems to be related to the double definition
of the symbol "foo".
There seems to be something wrong with the new time signature stuff.
When I process the example file 'time.fly' I get a load of messages
like this:
warning: can't find character called `timesig-old6/42/2'
warning: can't find character called `timesig-old3/23/4'
warning: can't find character called `timesig-old4/44/4'
warning: can't find character called `timesig-old2/25/4'
warning: can't find character called `timesig-C4/46/4'
warning: can't find character called `timesig-C2/23/2'
There are a bunch of scripts listed in scripts.ly that don't work:
lbheel = \script { "bheel" 0 0 -1 0 0 }
rbheel = \script { "bheel" 0 0 1 0 0 }
lbtoe = \script { "btoe" 0 0 -1 0 0 }
rbtoe = \script { "btoe" 0 0 1 0 0 }
lfheel = \script { "fheel" 0 0 -1 0 0 }
rfheel = \script { "fheel" 0 0 1 0 0 }
lftoe = \script { "ftoe" 0 0 -1 0 0 }
rftoe = \script { "ftoe" 0 0 1 0 0 }
and also
portato= \script { "portato" 0 -1 0 1 0 }
They give some mysterious font errors.
It appears that there are some spelling errors in midi-item.cc for the
instrument_name_sz_a_ table. Are these strings specified by some holy
MIDI reference somewhere, or are they flexible. (In other words, can
I freely change them and send in a patch, or are they supposed to
match up with something else?) These are the ones I've noticed:
acordina = accordion
tango accordian = concertina
distortion guitar = distorted guitar
orchestral strings = harp
pan flute = wood flute
Is there a general name for the thing that comes after \consists?
The types for paper translators seem rather mysterious:
dit(code(Engraver_group_engraver))
dit(code(Hara_kiri_line_group_engraver))
dit(code(Line_group_engraver_group))
dit(code(Score_engraver)) ]
Is there some system to the naming here?
Is there a difference between types and the things that come after a
\consists keyword? Or are they the same kind of thing?
What happens if I define a translator without giving it a name? Does
it just vanish, or have no effect?
P.S. My name is Adrian Mariano, not Andrew Moriano.
