[itsme]

Currently transposing and chord localization don't cooperate correctly.

In the attached example the chordpro file contains chords in D major, D G Bm A D. It is in default chord spelling, Bm means B natural.
Transposing to G major works fine in default and Scandinavian, Bm is transposed correctly to Em.
In Deutsch and in Cestina Bm is transposed to D#m which is wrong.
The reason is that Bm is interpreted as Bbm and thus transposed to D#m (in addition: the 'b' vs. '#' selection buttons are not respected).

This should not be the case! How chords are written within the file and how they are displayed have to be handled independently. Otherwise changing the localization would require changing ALL existing chordpro files!

Please take a look at my posts from 2019-05-14 in the ChordPro reference implementation thread linked above.
The reference implementation has two independent settings: "Notation" specifies how chords are written within the file, "Transcode to" specifies how the chords are displayed.
IMHO it is not essential to have that "Notation" setting also in MSP. Presuming that chords have to be typed in "Default" chord spelling would be fine for me.
But the setting of "Transcode to" (reference implementation) / "Chord Localization" (MSP) has to be only relevant for how chords are displayed (with or without transposing), it should not have any influence on how the chords from the file are interpreted.