Gonville - version 2.2 OFL, my proposition, and question
So... - in annex Gonville font in version 2.2 (without additional symbols). Why did you resign from Gonville font?
If you are interested this font, please send me information which symbols to be added. I suggest all symbols from the palette.
Copyright:
Designed by Grzegorz Pruchniakowski. This font is licensed under the SIL Open Font License (http://scripts.sil.org/OFL).
As I wrote - this is a new font - only the name is the same. So - if you don't agree to embed this font in the program - I can change the font name to another name.
And my proposition:
Jazz font - clefs, note flags, etc. Font will be under the SIL OFL. I've only one condition - access to the repository because I'll be added fixes and new symbols until the font will be completed.
So... - these are only suggestions.
Greetings,
Gootector
| Attachment | Size |
|---|---|
| Gonville-20.zip | 22.05 KB |
Comments
It got dropped because of the move to SMuFL and Bravura. Guess if someone converts Gonville to be compatible with SMuFL, it could find its way back into MuseScore.
Access to the repository is possible in an indirect way: via a pull request.
In reply to It got dropped because of the by Jojo-Schmitz
It's no problem for me - Gonville will be compatible with SMuFL, but will no longer be named Gonville - I change the font name.
"Access to the repository is possible in an indirect way" - W H Y ? ? ? Why I can't get access? So... it's no open source program...
I want to help in the development of the program. ...I see, it's your skills in designing fonts are rather meager... Your choice :D
In reply to W H Y by Gootector
Not sure what you mean. The need for a core team to manage access to the main release is standard practice. It's completely open source in that you can create your own fork, build from it, and push to it any time you like. But someone has to be in charge of deciding when release happen, which features make it in, etc. So, you push your change to your own fork, then issue a pull request for it to be merged into the master. Click the Development link at right of this page and find the Git Workflow page - it describes the process in detail.
As for skills in designing fonts, I don't know that anyone on the team professes to be experts at this - that's why they rely on fonts from LilyPond, Steinberg, and other respected providers of open source music fonts.
A SMuFL-compatible "jazz" font would be most appreciated by many, I'm sure, so if you're volunteering to create one, that would be wonderful!
In reply to Not sure what you mean. The by Marc Sabatella
"A SMuFL-compatible "jazz" font would be most appreciated by many, I'm sure, so if you're volunteering to create one, that would be wonderful!" - access to repository and jazz font will be done - this is my condition.
At the moment -- I move Gonville font to SMuFL and add a new glyphs - ornaments, dynamics, clefs, etc. - all symbols which are in palettes.
Gootector
In reply to "A SMuFL-compatible "jazz" by Gootector
I'm not sure if you are not understanding or what - I gather English is not your native language - so let me try again:
You *can* access the repository. Like any of the many other contributors to the MuseScore projec - like myself - you can fork the main repository in GitHub, clone that fork to your own computer, make your changes, build against your local repository, push to your fork on GitHub, and then issue a pull request so the core team can merge your changes into the master when appropriate. That would probably post-2.0, since 2.0 is pretty much feature-frozen at this point, but that is for the core team to decide.
So if you have an account on GitHub, you already have all the access you need to contribute to MuseScore. You don't need any additional access permissions, although you will need to sign the CLA (as explained on the Development page I mentioned) in order for your changes to be considered.
In reply to I'm not sure if you are not by Marc Sabatella
Don't be nervous, Marc :D I signed the CLA when source code was in (on?) SVN repository. I haven't account on GitHub and I don't know how does this work.
In reply to Don't be nervous, Marc :D I by Gootector
Great! Signing up for an account on GitHub is simple. Once you've done that, here's the page that explains the basic workflow:
http://musescore.org/en/developers-handbook/git-workflow
If you haven't used Git before, I might suggest you start by trying your best to forget anything you know about SVN or other systems. I like the idea behind Git a lot, but it's very different from anything else I've used, and I still struggle with it sometimes.
In reply to W H Y by Gootector
I meant write access to the repository to be somewhat indirect. Read access is fully available at https://github.com/musescore/MuseScore. Sorry for the confusion.