Second percussion instrument that is added is placed in incorrect position

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

1. Start with an empty score using the "Symphony Orchestra" template using all defaults
2. Add a percussion istrument such as "Suspended Cymbal"

It is placed in a sensible position, though the span setting of the percussion brace is not updated automatically to include it.

3. Add a second percussion instrument such as "Triangle".

This second percussion instrument is now incorrectly placed right below the Flutes and above the Oboes.

Moreover, the barlines continue from the Flutes, but do not extend to the Oboes.

This might possibly be related to the system language, which in this case is set to German. Note that while the template instruments are named in English, the newly added instruments are named in the system language.

I haven't been able to find a setting for the score language to influence this, so if I, say, wanted to write a score with all labels in Italian, I would have to rename every instrument inherited from the template from English to Italian, and then every subsequently added instrument from the system Language to Italian. Then I would manually have to move them to the correct place using the Layout panel.
Similarly, if I wanted to create an English score for an international ensemble, I would have to manually rename all instruments that were added to the score later unless I remember to change my entire OS language when working on it and adding instruments.

Supporting files, videos and screenshots

What is the latest version of MuseScore Studio where this issue is present?

macOS 12.7, Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.2-251141402, revision: github-musescore-musescore-ac9d3bc

Regression

I was unable to check

Operating system

macOS 12.7.6

Additional context

No response

Checklist

• This report follows the guidelines for reporting bugs and issues
• I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
• I have attached all requested files and information to this report
• I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible