Skip to content

Commit d6496ad

Browse files
committed
make floating point string formatting a MUST
Although readers may be ready to handle other formats.
1 parent fe45608 commit d6496ad

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

tagging.md

+7-4
Original file line numberDiff line numberDiff line change
@@ -107,15 +107,18 @@ To store a specific day such as May 1st, 2003, one would use "2003-05-01".
107107

108108
#### Number Tags Formatting
109109

110-
`TagString` fields that require a floating-point number **SHOULD** use the "." mark instead of the "," mark.
111-
Only ASCII numbers "0" to "9" and the "." character **SHOULD** be used.
110+
`TagString` fields that require a floating-point number **MUST** use the "." mark instead of the "," mark.
111+
Only ASCII numbers "0" to "9" and the "." character **MUST** be used.
112112
The "." separator represents the boundary between the integer value and the decimal parts.
113113
If the string doesn't contain the "." separator, the value is an integer value.
114-
Thousandths separators **SHOULD NOT** be used.
114+
Thousandths separators **MUST NOT** be used.
115115

116-
To display it differently for another local, applications **SHOULD** support auto
116+
To display it differently for another local, applications **MUST** support auto
117117
replacement on display.
118118

119+
For legacy reasons, it is possible that the "," separator **MAY** have been used
120+
or that thousandths separators **MAY** have been used.
121+
119122
#### Country Code Tags Formatting
120123

121124
`TagString` fields that use a Country Code **SHOULD** use the Matroska countries form defined in [@!RFC9559, section 13],

0 commit comments

Comments
 (0)