[EMAIL PROTECTED] said:
> Is there any reasonable way to do this: I would like to have one file
> that can generate the same tune in two different modes without having
> to go through and rewrite all the music in the other mode.
What is the difference between the two, except that you replace e.g.
\key C \dorian; with \key C \phrygian; ?
> restStyle=mensural doesn't seem to work (lots of characters not found
> for rests.fly)
Rests longer than quarter notes shouldn't be affected by the restStyle.
In the mensural style, r4, r8 and r16 are defined whereas r32, r64 and
r128 are not available. For the latter, you'll get the warning and
nothing is printed. Probably, the warning printout should be improved
for this case.
> What is the difference between \cadenza 0; and the barNonAuto
> property?
I think that with \cadenza 0; all the music counts as a single bar, whereas
with barNonAuto, Lilypond will still silently count bars according to the
time signature, but without printing any bar lines in the output.
> What do the following properties do?
...
> "dynamicStyle"
The text style used to typeset the dynamics. I guess anything but the
default 'dynamic' font will look very weird. Especially since the
'f' in single forte is placed at the font symbol 'e' since it has
different slant than the 'f' in \ff, \sf a.s.o.
...
> type_ + "Direction"
> type_ + "HangOnClef"
> type_ + "ScriptPadding"
type_ is any of "barNumber", "mark" or "margin", so most of the
combinations are already documented. For example, barNumberDirection
determines if the bar numbers are printed above (\up) or below (\down)
the staff. barNumberScriptPadding determines the distance between the
bar number and the staff lines. The HangOnClef properties are (hopefully)
a temporary solution and means that the bar number, \mark or margin text,
respectively, is connected to the clef symbol instead of the bar line at
the beginning of staffs.
/Mats
