[itsme]

Oh, sorry, my fault. I added the blank in [B ] when I described the content of the file in the post's text to avoid that [B] is misinterpreted as "bold" by the forum rendering. And forgot to remove the blank when I copied it to the source file.
Next try:
erroneous blank removed from the source file => all chords detected as valid chords
I only changed the defaults in Text File Settings, didn't use "meta notation:"
default source localization is always German
default display localization German:
   
transposed
   
expected: B  H  C  Db

[itsme]

here's what goes wrong with the forum rendering:
marked the chords in brackets [A] and as bold in the forum editor
same text [b][A] and without the blank
    [/b]

[Zubersoft]

That is true - the forum text editor is going to do some funky stuff if it detects a b in brackets.

I believe I've fixed all the localization issues. It would be great to get confirmation after the next update is available.

Thanks,
Mike

[DeArmin]

If you look at my first post on the first page of this thread, I said this:

It is implemented. I followed the OnSong settings for localization as described here: 

• Default displays chords as capital letters from A through G with flat or sharp symbols as needed. Minor chords are denoted by a lowercase "m" to the right of the chord.
  
• Čeština displays chords in a convention familiar with the Czech language. This displays "B" as "H" and "Bb" as "B". In addition, minor chords are denoted by lowercase "mi".
  
• Deutsch displays chords in a convention familiar with German-speaking people. This displays "B" as "H" and "Bb" as "B".
  
• Scandinavian displays chords in a convention familiar with Scandinavian-speaking people. This displays "B" as "H" and "Bb" as "Bb".
  

So that's where I got it from.

Mike

Hello, there is further a Transposing Problem. See attachment.
Some Chords were not transposed. In the Intro only the first chord D was tranposed. Also in the Verse the transposing is not correctly. I use the scandinavian settting.
Armin

[itsme]

It would help if you shared also the source (or at least some relevant snippets) and a screenshot of your Chord Localization settings. Is it text or ChordPro? I recommend using ChordPro.

[DeArmin]

It would help if you shared also the source (or at least some relevant snippets) and a screenshot of your Chord Localization settings. Is it text or ChordPro? I recommend using ChordPro.

The source is a txt-file (s. attachment)

[itsme]

That's not a bug in MobileSheets, it's probably a matter of your chord localization settings. Your source file is in "default" syntax (Bb / B / C). In "Scandinavian" (Bb / H / C) Bm is not a valid chord, so it is not transposed.
With source localization = default and display localization = scandinavian your file is displayed and transposed as expected.
           

[DeArmin]

That's not a bug in MobileSheets, it's probably a matter of your chord localization settings. Your source file is in "default" syntax (Bb / B / C). In "Scandinavian" (Bb / H / C) Bm is not a valid chord, so it is not transposed.
With source localization = default and display localization = scandinavian your file is displayed and transposed as expected.

If you do the tranposing in the library screen it works. If you do this via Edit File (Datei bearbeiten), the transpose will not be carried out correctly (see atachment)

[itsme]

I can confirm that there's a bug when we are in the edit window.
It affects only .txt files, ChordPro is transposed correctly
       
I tested with MobileSheets 3.9.7 on Win10 with SourceLocalization = Default and DisplayLocalization = Scandinavian
Note: in the lyrics and chords section only Bm is not transposed, in the Intro, where there are only chords without lyrics, transposing stops at the Bm so that the following Em and A chords are also not transposed