Intl.DurationFormat

[zbraniecki]

Since there's little progress with deciding on what to do with durations, and ICU's API doesn't seem too defined about it, I'd like to start a discussion about possible choices. It seems to me that we have four:

1. We can add it to NumberFormat
2. We can add it to UnitFormat
3. We can create a separate DurationFormat
4. We can kickstart some RuleBasedNumberFormat

The common use cases are:

1. Timer "05:12:21"
2. Stopwatch "12:21.05"
3. Video/Music player remaining/elapsed time "-04:13"

The formatting differs from time formatter, because the UI will define the range of units to be displayed, like h:m:s, m:s.S and the number of digits per unit (m:ss vs mm:ss or mm:ss.SSS vs mm:ss.SS)

NumberFormat would be convenient for that reason - it would benefit from similar API of defining minimumIntegerDigits and maximumIntegerDigits for each component, and the value itself may be just a number of milliseconds.

Fitting it into UnitFormat seems to be natural fit for CLDR Unit Elements [0] together with compound units, unit sequences and coordinate units, but may be hard and requiring us to bend over backward to accommodate for the options that will be required.

Custom DurationFormat seems to be the easiest choice from the API design perspective, but it increases the number of objects we specify. It's been the choice I made so far for Firefox OS patterns, but I'll be happy to migrate our code once we reach a consensus here.

RuleBasedNumberFormat is what ICU seems to be using now for duration patterns, but it's a pretty big API most similar to Mozilla's proprietary Date.prototype.toLocaleFormat and I'm not sure if we want to go there.

The API I use in DurationFormat looks like this:

var f = Intl.DurationFormat(locales, {
  minUnit: 'second', // millisecond | second | minute | hour
  maxUnit: 'hour' // millisecond | second | minute | hour
});
f.format(i); // 52:34:51

Thougths?

[0] http://www.unicode.org/reports/tr35/tr35-general.html#Unit_Elements

[rxaviers]

Brainstorming... Follow an API variation that is more parallel with DateTimeFormat for picking different field lengths:

var f = Intl.DurationFormat(locales, {
  hour: 'numeric',
  minute: '2-digit'
});
f.format(i); // 8:01

[rxaviers]

CLDR provides data for three combinations: hm (hour and minute), hms (hour, minute, and second), and ms (minute and second). AFAIK, it provides no algo for dynamically including additional fields, e.g., milliseconds. (cc @srl295?)

• http://www.unicode.org/reports/tr35/tr35-general.html#durationUnit
• https://github.com/unicode-cldr/cldr-units-modern/blob/master/main/en/units.json#L2046-L2054

From those skeletons, the default length can be extracted. For example, {hm: "h:mm"} means the default for hour is numeric and the default for minutes is 2-digits.

[zbraniecki]

@srl295 pointed out at this: http://icu-project.org/apiref/icu4c-latest/classicu_1_1MeasureFormat.html#a38ea881ad05c1b81bb5ade8449e44544

[zbraniecki]

Heads up, this has been advanced to Stage 0 as of today.

[zbraniecki]

@srl295 - We will need {mm}:{ss}.{SS} at the very least for all kind of timers. (Android, iPhone timers show milliseconds). Can we get it into CLDR?

Alternatively, we could just encode a single pattern, like {hh}:{mm}:{ss}.{SS} that we "cut out" from the portion that we need.

[zbraniecki]

This proposal has been advanced to Stage 1 as of today.

[srl295]

@zbaniecki see http://apps.icu-project.org/icu4jweb/flexTest.jsp?pat=HmsSS&_=en_US
skeleton HmsSS --> pattern HH:mm:ss.SS --> format 14:02:01.34

and in Polish HH:mm:ss,SS / 14:02:41,67

so the data / algo is there, let me know if this helps

[zbraniecki]

thanks! Where is this skeleton in CLDR?

[zbraniecki]

@srl295 - So I assume that flexTest indicates that it's something around the algo to get from skeleton to pattern using this: http://www.unicode.org/cldr/charts/29/summary/en.html#1746 - but I don't see anything on SS token there :( (and the value for polish is likely wrong, it should be ss.SS, not ss,SS)

[srl295]

@zbraniecki two problems:

1. CLDR spec is unclear AND/OR CLDR data is incomplete.
2. ICU has special behavior AND meta data that's not in CLDR

Filed a CLDR bug here http://unicode.org/cldr/trac/ticket/9352

[jungshik]

@srl295, as you pointed out earlier, CLDR/ICU has support for measure format that can be used for duration format. Then, the thread moved to talk about skeletons for DateTime format.

The input to DateTime format is 'time' while the input for duration format is 'time delta'.

Can skeletons/patterns for the DateTime format be used for measure format?