Clarify the use of hyphens in glyph names #1362
Open
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.
Description
Having hyphens at the end of "development" glyph names makes handling ranges correctly in the grammar significantly trickier; the current implementation doesn't attempt to. As there doesn't seem to be a need for them in that location this PR updates the docs to clarify that they can't end a name.
Perhaps more controversially it also states that the special characters can't be used at the start of a name. The spec was ambiguous about this but the
featgram.g
implementation doesn't allow them at the beginning of a name. I agree with that decision—too dicey to allow them there.One additional question is whether we should go farther and restrict the use of more or all of the special characters at the end of a name. The main reason for doing that would be to reserve potential glyph operators for future use, which could be handled the way hyphens are handled now. I leave that up for discussion.
Checklist:
Closes #970