Relax fmtp requirement for whitespace after semicolon #272
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.
ST 2110-20 requires whitespace after the semicolon within format-specific parameters:
However, RFC 4566 (and RFC 8866) doesn't specify this syntax, and many examples, in both RFCs and SMPTE specs, show semicolon used as separator with no following whitespace.
We relaxed the SDPoker check some time ago... AMWA-TV/sdpoker#6.
Note that this does not accept whitespace preceding the semicolon, partly because I'm lazy and handling trailing whitespace after the last parameter (with no semicolon) is a harder change, and because ST 2110-20 also says no whitespace within the name or value.