-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gabc-version header #664
Comments
I don't know if gabc-version is the version of the "gabc specification" or if it's the version of Gregorio. Can anyone make a sensible decision on this? |
My impression was that we had decided that they were all one and the same now. Additionally, we've made some modifications that involved changes in the gabc entry, so even if the above isn't true, we still need to update that number. |
Hmm... Checking the issue history, it looks like this wasn't addressed in #87 as I thought it was. So, discuss. I think that having a separate version number is cumbersome and not really necessary. (And that's all I have time to say right now.) |
I honestly have no opinion at all. I was actually asking for guidance as to what to do to fix it. |
Originally there was supposed to be different versions of gabc and gregorio could have compiled them differently, but that's not going to happen, so maybe the best would be to deprecate gabc-version? |
…ation * commit '38aca71f66d829ddefe3c29108cc3423db9ea1a3': 16 new glyphs for nabc notation, small fixes. Deprecated the gabc-version header. Fixes gregorio-project#664. Fixed lost "endgroup" for first letter centering of empty syllables.
If the command line tool is put into verbose mode when compiling a gabc file, it raises an error about the
gabc-version
header if it is not0.9.3
. Either, the command line tool should be updated so that it checks the version number against the current version number (and VersionManager.py changed to keep it up to date) or thegabc-version
header should be deprecated.The text was updated successfully, but these errors were encountered: