Posts: 9,483
Threads: 244
Joined: Apr 2012
Reputation:
124
05-25-2019, 10:12 AM
(This post was last modified: 05-26-2019, 03:33 AM by Zubersoft.)
I've removed the single setting for chord localization, and now when you tap it a dialog is displayed with two options: "Default source localization" and "Default display localization". The settings work as you both described. I've updated the logic and the file now transposes as you would like. I also added support for {meta: notation [src] [display]} so that you can override one or both. Accepted values for those match what I support in the settings, which is:
Default
Čeština
Deutsch
Scandinavian
Hopefully that covers everything.
Thanks,
Mike
Posts: 9,483
Threads: 244
Joined: Apr 2012
Reputation:
124
Sure, I've added parsing for those values as well. Čeština is Czech. I can update the dropdown selections to show Czech and German when English is the current language.
Latin and solfège support would require a lot of changes. I don't currently have any code in place for representing chords as "Do, Re, Mi,..." and not many users have asked for that, so I'll have to add it to the feature request list for later. I get more requests for the Nashville numbering system. Perhaps I can tackle this all at once in a future update and also add support for Roman numerals for chords so that I've covered all bases.
{meta: notation ...} will be parsed out when the document is first opened and applied for the entire document as an override to the default setting. I would not consider it a song setting as it won't show up anywhere in the application. I do not allow the notation to be changed halfway. The last {meta: notation ...} listed will override any others.
Mike