Werner LEMBERG <[email protected]> writes: >>>>> As soon as there are more staves involved, it's rather clear that >>>>> time signatures must always come after key signatures so that >>>>> they can be properly aligned vertically in the score. >>>> >>>> Reminds me of the simple rule to figure out where a mathematical >>>> proof goes wrong. Just look for the first occurence of a phrase >>>> like "it is rather clear", "obviously" or similar. >>> >>> The same. Not related to the algorithm but how music typesetters >>> print scores. >> >> So you did find a relevant example? Can we see it? > > For more staves, it is the Daphnis example in !3224 and the Britten > example in a recent e-mail to this list on which I base my "it's > rather clear".
Which is not a relevant example since the proposed code would not typeset it different in any manner. > If you ask for an example with multiple staves having only a key > signature *or* a time signature and not at least one staff having a > combination of them, I'm out of luck. If it is exists, it is an > extremely rare case. Can we then please stop pretending that "as soon as there are more staves involved, it's rather clear that time signatures must always come after key signatures"? It is neither "clear" by logic, nor has there been any example brought into this discussion that would have demonstrated this principle. With the proposed merge request, all time signatures will be aligned, and all key signatures will be aligned, and there will be no staff in which a key signature would follow a time signature. When there is no staff having both types of signature, literature shows examples of either forcing the (sparse) time signature column to the right of the key signature column when they don't conflict, and also examples where this isn't done. We haven't dug up any relevant example for more than two staves for either choice of typesetting in this situation, and it would be nice if I didn't have to point this out again and again. -- David Kastrup
