[Andrew9999]

I'm using 3.9.3 with Windows 11, but this question applies to Android as well.

If I used ABC in a ChordPro file and use the transpose button in MobileSheets, only the ChordPro chords transpose.  The ABC notation appears fixed.  Is this by design?  the test ABC I'm using looks like this:


{start_of_abc}
X:1
M:4/4
K:G
|:GABc dedB|dedB dedB|c2ec B2dB|c2A2 A2BA|
  GABc dedB|dedB dedB|c2ec B2dB|A2F2 G4:|
|:g2gf gdBd|g2f2 e2d2|c2ec B2dB|c2A2 A2df|
  g2gf g2Bd|g2f2 e2d2|c2ec B2dB|A2F2 G4:|
{end_of_abc}

Thanks.

[itsme]

It's definitely not by design. Examples that I posted e.g. in https://www.zubersoft.com/mobilesheets/f...12171.html are transposed just fine.
But anyway your ABC score is not transposed. It's somehow connected with the starting repeats.
Andrew9999_2.pro and Andrew9999_4.pro show the reported bug
       

...

[itsme]

...

Andrew9999_3.pro is transposed correctly
   

Your ABC syntax is probably correct as EasyABC can transpose it without problems
   

@Mike: additionally: in case there's no {keys: ...  statement and no chord in square brackets it seems a good idea to use K: from the first ABC section (if there is one) to initialize the keys field in the database, which is the starting point for the transpose dialog

[Andrew9999]

Great feature by the way:  embed staff notations fragments into chord/lyrics and keep it all in sync and formatted as one.  Neat!

[itsme]

@Mike: Sorry, I was not clear in my first post. 
Andrew9999's ABC code is correct, there's a bug in MobileSheets that has to do with the starting repeats that are handled incorrectly.

[Zubersoft]

I'm deferring all of these issues until I can integrate abc2svg through a javascript engine. It may change a considerable number of things, and will hopefully resolve many potential issues.

Mike