Chord Parenthesis Without Spaces

This problem still exists (in MuseScore 4) and is wrong on at least three counts:

1. There should never be blank spaces between the brackets and the contents, that is a typing error (propagated by the peculiarities of some programming languages, and by people who don't know how to type). This sentence shows precisely how brackets, everywhere, should appear when properly typed (immediately wrapping their contents).

2. If the user wants spaces somewhere, they can type them, deliberately. And indeed they will if they want to type in optional chord progressions, e.g. C (C6 Cma7), though they probably want wider spacing between the two chords, for clarity of reading. And in reality, the chords would usually be aligned above specific notes in the melody, so are much more akin to being tabbed rather than spaced apart.

3. That kind of example is not the only use of brackets, and will still be appearing wrong with spaces inside the brackets. A very common use of bracketed chords is a single optional chord, not just sequences. For example, a bar may be played with an F chord for the whole bar, or be (optionally) enhanced by becoming a sixth on the third beat, and be written as F followed by (F6), leaving it for the player to decide whether on not to bother with it. Or, another example being the implied chord on an anacrusis that's not actually played, but helps to place the lead-in notes into context. There'll be many other examples, too, and adding spaces inside the brackets will be wrong with all of them.

The incorrect spaces make a mess of scores, particularly tightly packed scores where you can't afford to have space wasted by wrongly formatted bracketing. We're long past the point of using badly created fonts that have the wrong amount of tiny spacing inside the brackets, and having to compensate for it with bad techniques of adding in whacking great big blank spaces that don't belong there.