Handle <forward> elements without <voice>
#1030
Merged
Conversation
This file contains hidden or 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
mscuthbert
approved these changes
Jun 19, 2021
Member
mscuthbert
left a comment
mscuthbert
left a comment
There was a problem hiding this comment.
Wonderful. Thanks for this dirty work!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
After #1008 I've got MuseScore files emitting dozens of warnings:
Turns out they don't write
<voice>tags on<forward>elements and just expect readers to infer the voice context. So extended a workaround already present for an issue with Sibelius.The spec says
<voice>tags are optional on forward tags but also that "The forward element is generally used within voices and staves."