-
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
inclinated brace #776
Labels
Comments
I'll work on this, but since this would involve drawing something generically using metapost, I make no promises as to whether it will actually make 4.1. |
Sure, no problem, thanks a lot! |
In modern notation that would be called a slur, and I think it would be far more reasonably called that than "inclined brace" here too. |
henryso
added a commit
to henryso/gregorio
that referenced
this issue
Jan 12, 2016
henryso
added a commit
to henryso/gregorio-test
that referenced
this issue
Jan 12, 2016
This was referenced Jan 12, 2016
rpspringuel
added a commit
to rpspringuel/gregorio
that referenced
this issue
Jan 13, 2016
* develop: Added support for typesetting simple slurs. Fixes gregorio-project#776. Implemented oriscus orientation dependency on the note that follows. Fixes gregorio-project#774. Lengthened the tail of the long-tailed liquescent stropha. Used different glyphs for liquescent stropha on a line. Fixes gregorio-project#773.
rpspringuel
added a commit
to rpspringuel/gregorio-test
that referenced
this issue
Jan 13, 2016
* develop: Added a test to exercise the slurs. Tests gregorio-project/gregorio#776. Added/updated tests/expectations to match oriscus orientation changes. Tests the fix for gregorio-project/gregorio#774. Updated expectations to match the taller liquescent stropha glyphs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
An abbey asked for the ability to do:
it should be extremely rare so I'm not really sure it's worth having a gabc notation for this, it could be just something to put in a
<v>
snippet with hardcoded length values, but it should be possible...If it's possible in 4.1 that would be great, otherwise there's no emergency.
The text was updated successfully, but these errors were encountered: