Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make floating point string formatting a MUST #960

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions cellar-tags/tagging.md
Original file line number Diff line number Diff line change
Expand Up @@ -107,15 +107,17 @@ To store a specific day such as May 1st, 2003, one would use "2003-05-01".

#### Number Tags Formatting

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

To display it differently for another locale, applications **SHOULD** support auto
To display it differently for another locale, applications **MUST** support auto
replacement on display.

In legacy media containers, it is possible that the "," separator or the thousandths separators might have been used.

#### Country Code Tags Formatting

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