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

Time separator is also numbering system dependent? #108

Closed
anba opened this issue Jul 26, 2022 · 1 comment · Fixed by #133
Closed

Time separator is also numbering system dependent? #108

anba opened this issue Jul 26, 2022 · 1 comment · Fixed by #133
Labels
consensus We reached a consensus in a discussion meeting, through email or the issue discussion editorial needs-tg1

Comments

@anba
Copy link
Contributor

anba commented Jul 26, 2022

CLDR defines a numbering system dependent time separator in ldml/numbers/symbols/timeSeparator.

For example, da-u-nu-latn uses the time separator ".", whereas da-u-nu-arabext falls back to the root time separator "٫".

But when reading the timeSeparator definition in https://unicode.org/reports/tr35/tr35-59/tr35-numbers.html#Number_Symbols, it's not clear to me when ldml/numbers/symbols/timeSeparator should actually be used resp. if we should include the numbering system when looking up the time separator. UTS 35 has this note:

No CLDR locales are known to have a need to specify timeSeparator symbols that depend on number system; [...]. In the meantime, since CLDR data consumers can still request the timeSeparator symbol. it should match the symbol actually used in the timeFormats and availableFormats items.

The default (= "latn" numbering system [1]) time separator seems to match what's used in <timeFormats> and <availableFormats>, except for fr-CA:

fr-CA uses separate time separators for each time unit, i.e. "h", "min", and "s".

UTS 35 also defines durationUnit, which uses a single time separator which isn't numbering system dependent.

I'm currently a bit lost due to the conflicting definitions from UTS 35. Can we make this a bit more clear in the spec?


[1] "latn" numbering system and not <defaultNumberingSystem> for cases like ur-IN, which uses "arabext" as its default numbering system, but doesn't override ldml/numbers/symbols[@numberSystem="arabext"]/timeSeparator, so it's using the default from the root locale, which means "٫".

@ryzokuken ryzokuken added the Meeting Discussion Need to be discussed in one of the upcoming meetings label Sep 13, 2022
@romulocintra romulocintra added editorial and removed Meeting Discussion Need to be discussed in one of the upcoming meetings labels Nov 28, 2022
@ryzokuken ryzokuken added the consensus We reached a consensus in a discussion meeting, through email or the issue discussion label Feb 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
consensus We reached a consensus in a discussion meeting, through email or the issue discussion editorial needs-tg1
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants