Special characters: don't suggest that <sp>'y</sp> should work by default
#112
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
as of Gregorio 6 it's not part of the pre-defined default set of special characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The documentation concerning the
<sp>tag is slightly confusing - I would assume that when ý is mentioned as an example of a character hard to type, it would be supported by Gregorio by default, but it is not. This PR removes the confusing mention and adds information about the\gresetspecialGregorioTeX command.In addition to that there are a few not-strictly-related small improvements. Each sits in its own separate commit, so that any of the edits can be reviewed and included/excluded separately. If the PR as a whole is acceptable, it's probably best to squash it.