Laurent Pugin

This is actually not only when duplicating but also when creating a new work. So the real issue is in work creation. Saving a second time fixes it (I think)

One question I have on this topic is the meaning of keySig@sig="mixed". This should be clarified too. When do we expect the attribute value to be used, and what does...

I don't think `data.KEYFIFTHS` is really appropriate for this. I would go back to `data.KEYSIGNATURE` https://music-encoding.org/guidelines/v3/data-types/data.keysignature.html

Could we use LibMEI and have a guidelines output for it?

A good workaround is to change the order of the layers in the MEI ```xml K. 284/01, m34-35 ```

What you are trying to represent is weird. Why would one write a clef change before and after a measure rest? You can achieve it by having two layers: ```xml...

When there is a rendering problem for something that has never been considered and that is such a corner case, I would not label the issue as a `bug`.

It is much more logical to put the clef after the measure rest. That renders correctly ```xml Clef interaction with mRest Klaus Rettinghaus 2023-08-21 ```

This is actually not only when no neume is provided. Text space adjustment is not implemented: ```xml Be (with additional text for testing) ne di ci te ```

Sure. Could you point me to one example and explain a bit more what you expect me to do?