1. MobileSheets explicitly has code to apply the transpose offset to the repeated chorus section, so I'm not sure why that's not working based on your description. I just tested this on my Android, Windows and iPad devices and it worked perfectly fine. If you go to Settings->About, what version are you running and is this with the Android, Windows, or iOS version?
Windows and the latest version of MobileSheets. I don't know what to say. I added {transpose:+2} (or whatever) and then when we were playing it, I discovered that everything transposed *except* the choruses I repeated by {chorus}.
2. Metadata isn't parsed if you just edit the file,
Ok, this is an interesting reply. So ... I never "import" .cho files. I create a new file and paste my .cho document and then I add meta data. I think title populates from the file title, eg. "America.cho" will fill "America" into the Title field. Artist will populate from {artist:John Lennon} and Composer will populate from {composer:John Lennon}. Year will populate from {year:1966} and key will populate from {key:G}. Notably, these will also update if I make later edits to the chordpro directives. So, I naturally assumed Tempos would populate from {tempo:80}.
So I'm definitely surprised to find out this "won't work". (lol)
3. {textsize} to revert isn't currently supported. There was another forum post about that. It's on my list for the next major update which is including a lot of chord pro features and fixes. {textcolor} is also not supported currently.
That was probably my thread as well, although someone did tell me that {textsize} revert should work, but it doesn't. So, of course I can repeat the earlier {textsize:14} or whatever, but the problem with that is my tablets don't all have the same default textsize. So, I abandoned "textsize" for "textfont", since I have all the tablets formatted with the same fonts.I know that "textcolor" is not implemented -- so I included these comments for two reasons. First is so that other people searching for the same solutions I am will find this info, just as I find solutions in MobileSheets via web searches. Second is that I'm just throwing out tools I would like to have. But, I'm not explicitly asking to have it implemented. I would consider my "requests" (or observations) as pretty much on the low end of priorities for you.Well, third might be that I have a solution others might find useful -- as is my surprise to find meta data is not parsed! So I didn't accurately present my concern because in my experience the meta data is parsing and working well for me. It would be more time consuming to edit and (re-)import a .cho file than to just update the Fields, since I either type the .cho file in the MobileSheets editor as a "new file" or I cut and paste a file from the online converter. So, I'm happy it works for me, even if it isn't actually "implemented."As always, thank you for your attention to all these details!
Windows and the latest version of MobileSheets. I don't know what to say. I added {transpose:+2} (or whatever) and then when we were playing it, I discovered that everything transposed *except* the choruses I repeated by {chorus}.
2. Metadata isn't parsed if you just edit the file,
Ok, this is an interesting reply. So ... I never "import" .cho files. I create a new file and paste my .cho document and then I add meta data. I think title populates from the file title, eg. "America.cho" will fill "America" into the Title field. Artist will populate from {artist:John Lennon} and Composer will populate from {composer:John Lennon}. Year will populate from {year:1966} and key will populate from {key:G}. Notably, these will also update if I make later edits to the chordpro directives. So, I naturally assumed Tempos would populate from {tempo:80}.
So I'm definitely surprised to find out this "won't work". (lol)
3. {textsize} to revert isn't currently supported. There was another forum post about that. It's on my list for the next major update which is including a lot of chord pro features and fixes. {textcolor} is also not supported currently.
That was probably my thread as well, although someone did tell me that {textsize} revert should work, but it doesn't. So, of course I can repeat the earlier {textsize:14} or whatever, but the problem with that is my tablets don't all have the same default textsize. So, I abandoned "textsize" for "textfont", since I have all the tablets formatted with the same fonts.I know that "textcolor" is not implemented -- so I included these comments for two reasons. First is so that other people searching for the same solutions I am will find this info, just as I find solutions in MobileSheets via web searches. Second is that I'm just throwing out tools I would like to have. But, I'm not explicitly asking to have it implemented. I would consider my "requests" (or observations) as pretty much on the low end of priorities for you.Well, third might be that I have a solution others might find useful -- as is my surprise to find meta data is not parsed! So I didn't accurately present my concern because in my experience the meta data is parsing and working well for me. It would be more time consuming to edit and (re-)import a .cho file than to just update the Fields, since I either type the .cho file in the MobileSheets editor as a "new file" or I cut and paste a file from the online converter. So, I'm happy it works for me, even if it isn't actually "implemented."As always, thank you for your attention to all these details!