"1.2 is supposed to be stable release ... this is going to
change: as
of next week "
Oh dear - I'm *so* close to production status...
Might there be a solution of any sort in 1.2.12 for the
following? (I've been working on too many other things around
autochange staff and horizontal shifts to have had time to try
them all.)
1. will interline instead of staffLineLeading solve the stems
missing heads problem?
2. can the bar-numbering duplication with \StaffContext \consists
Bar_number_engraver; be removed?
3. might articulationScriptPadding (or something else) permit
moving prallers up or down one by one?
4. is there any current way of modifying an individual note stem,
even if indirect and different for beamed and unbeamed notes,
while ensuring that default behaviour is reset after?
5. will putting matching \bar in both staves solve that problem
i.e. will they join up?
Mats: "Of course the meaning [of stemLength] would then be the
average stem length for the whole beam..."
I disagree here - it would be very valuable in tight polyphonic
keyboard music to be able to set the exact lengths of the first
and last notes of a beam, to thread the beam through the
obstacles. I would propose instead that if one stem length is
set, that it be *set* and that the beam slope be unchanged from
default but just go through the specified point; if two are set
then the beam position is completely defined. (Of course, as in
any modification of default behaviour, the user is responsible
for the result!)
"I have some 17th century music ... where the different parts
have repeat signs at different places"
Wow! I've seen that in individual parts, but NEVER in a score!!
Are you sure you don't want to have mercy on the conductor and
rectify it? Urtext doesn't have to mean 'photocopy', after all...
John
