From 8633f5a30186bb9278ea6a644e1b473e863b5f91 Mon Sep 17 00:00:00 2001 From: Steve Lhomme Date: Sun, 30 May 2021 09:45:51 +0200 Subject: [PATCH] Remove range attribute from element with a (large) restriction section The restriction mentions the value that are allowed. The range gives the lower and upper limits. But without an indication on what to do with values in the range but with an unknown value we have more confusion than necessary. If the restriction values are later expanded older parser will ignore the new values no matter what. The range is only useful to tell if the value is legit or not, but there's still plenty of changes it is not. --- ebml_matroska.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/ebml_matroska.xml b/ebml_matroska.xml index 86b11a8c4..420feb7de 100644 --- a/ebml_matroska.xml +++ b/ebml_matroska.xml @@ -244,7 +244,7 @@ though the design allows an unlimited number). A unique ID to identify the Track. This **SHOULD** be kept the same when making a direct stream copy of the Track to another file. - + A set of track types coded on 8 bits. @@ -427,7 +427,7 @@ The format depends on the ChapProcessCodecID used; see (#chapprocesscodecid-elem Video settings. - + A flag to declare if the video is known to be progressive, or interlaced, and if applicable to declare details about the interlacement. @@ -438,7 +438,7 @@ or interlaced, and if applicable to declare details about the interlacement. - + Declare the field ordering of the video. If FlagInterlaced is not set to 1, this Element **MUST** be ignored. @@ -778,7 +778,7 @@ in candelas per square meter (cd/m^2^). - + Describes the projection used for this video track. @@ -921,7 +921,7 @@ The decoder/demuxer has to start with the highest order number it finds and work This value has to be unique over all ContentEncodingOrder Elements in the TrackEntry that contains this ContentEncodingOrder element. - + A bit field that describes which Elements have been modified in this way. Values (big-endian) can be OR'ed.