[EMAIL PROTECTED] writes:
> the semicolons). You could use "\name Staff" instead of "Staff;" for
OK.
> 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
I've been thinking about a distinction between simple and compound
expressions for assignments. The simple ones need ;, the compound
ones don't.
> situation of having them sometimes required arbitrarily, sometimes
> optional, and sometimes illegal is very bad, in my opinion.
Yes.
> 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.
I think I implemented a padding field somewhere [searching .. ] . No
opps. Added to TODO
> Is the \output keyword going to be reused? Or should/will it be removed?
>
No, Yes.
>
> 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".
>
OK. I'll check it out.
> 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.
added to TODO.
>
> 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.
I have no clue, but I suspect a holy reference would not contain
spelling errors.
> Is there a general name for the thing that comes after \consists?
Yes, it should be the name a class of LilyPond, derived from
Translator
> 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?
Line_group_engraver_group and Engraver_group_engraver are almost the
same, but Line_group_engraver_group puts the things contained in the
context into a compound graphical element. The
Hara_kiri_line_group_engraver additionally makes the compound
disappear if it doesn't contain notes. Score_engraver is the
top-level engraver. Any top-level engraver should be a type derived
from Global_translator.
> What happens if I define a translator without giving it a name? Does
> it just vanish, or have no effect?
I am not sure. Try it!
> P.S. My name is Adrian Mariano, not Andrew Moriano.
OOPS!
--
Han-Wen Nienhuys, [EMAIL PROTECTED] ** GNU LilyPond - The Music Typesetter
http://www.cs.uu.nl/people/hanwen/lilypond/index.html
