Stage: 2

Champion: Younies Mahmoud, Ujjwal Sharma

Authors: Younies Mahmoud, Ujjwal Sharma

Stage 3 Reviewers

• Michael Ficarra @michaelficarra
• Ron Buckton @rbuckton
• Ross Kirsling @rkirsling

slide

This proposal reached Stage 1 at the 2020 Feb TC39 meeting.

• Time Duration is how long something lasts, from the start to end. It can be represented by a single time unit or multiple ones.
  • For example,
    • 10000 seconds
    • 2 hours 46 minutes 40 seconds
• Every locale has its own way to format duration.
  • For example:
    • en-US: 1 hour, 46 minutes and 40 seconds
    • fr-FR: 1 heure, 46 minutes et 40 secondes
• There are multiple widths for the time duration.
  • For example, wide and short
    • 1 hour, 46 minutes and 40 seconds → Wide
    • 1 hr, 46 min, 40 sec → Short

new Intl.DurationFormat("fr-FR", { style: "long" }).format({
    hours: 1,
    minutes: 46,
    seconds: 40,
});
// "1 heure, 46 minutes et 40 secondes"

Three v8 prototypes (try to use two different possible ICU classes) were made, ALL are

• Sync with "Stage 1 Draft / June 1, 2020" version of spec
• Flag --harmony_intl_duration_format
• Have not implement any changes not yet spec out in https://tc39.es/proposal-intl-duration-format/ such as
  • hideZeroValued
  • smallestUnit / largestUnit

1. Base the implementation on icu::MeasureFormat::formatMeasures()
   • https://chromium-review.googlesource.com/c/v8/v8/+/2762664
   • Not yet implment formatToParts
   • Need solution of ICU-21543 "Add methods to return FormattedValue to MeasureFormat " to implement formatToParts().
2. Based on the support of "-and-" unit in LocalizedNumberFormatter
   • https://chromium-review.googlesource.com/c/v8/v8/+/2775300
   • Not yet implment formatToParts
   • Not yet implement style:"digital"
   • Need solution of the following to implement formatToParts():
     • ICU-21544 "unit format in number formatter return U_INTERNAL_PROGRAM_ERROR with "year-and-" (except month) and "month-and-""
     • ICU-21547 "nextPosition() of FormattedNumber of unit with "-and-" is buggy"
3. Based on icu::ListFormatter and icu::number::LocalizedNumberFormatter w/o depend on the "X-and-Y" units.
   • https://chromium-review.googlesource.com/c/v8/v8/+/2776518
   • Implements formatToParts
   • Not yet implement style:"digital"

• Users need all types of duration format depending on the requirements of their application. For example, to show how long a flight takes, the duration should be in Short or Narrow format
  • 1 hr 40 min 60 sec → Short
  • 1 h 40 m 60 sec → Narrow

In this section, we are going to illustrate each user needs (requirements) and a design for each need (requirement)

• Users need to identify how to input a duration value. For example, if a user needs to format 1000 seconds , how could the user pass the value to the formatting function.

• Input value will be an object of type Temporal.Duration
• Example:
  • const d = new DurationFormat();
  • d.format(Temporal.Duration.from({hours: 3, minutes: 4});

Users want to determine several types of the formatting width as following

• The user can determine the formatting width using a parameter style and the value of this parameter may be one of the following string s:
  • "wide"
  • "short"
  • "narrow"
  • "digital"

• Users need the following fields to be supported
  • Year
  • Month
  • Week
  • Day
  • Hour
  • Minute
  • Second
  • Millisecond
  • Microsecond
  • Nanosecond

• We are going to support the same fields as in Temporal.Duration , which contains:
  • years
  • months
  • weeks
  • days
  • hours
  • minutes
  • seconds
  • milliseconds
  • microseconds
  • nanoseconds

• Users need to determine the time fields,
• For example: 6059 seconds
  • Hours, Minutes, Seconds
    • 1 hours, 40 minutes and 59 seconds
  • Minutes and Seconds
    • 100 minutes and 59 seconds.

• Users can determine the time fields in array.
• Example:

    fields: [
        'hour',
        'minute',
        'second'
    ]

• We are discussing to use largestField and smallestField options to determine the time fields instead of an array.

• Users needs to hide zero-value fields depends in some criteria
  • Hide all zero-value fields
    • Hours, Minutes, Seconds (without the hide option)
      • 1 hours, 0 minutes and 59 seconds.
    • Hours, Minutes, Seconds (with the hide option)
      • 1 hours and 59 seconds.
  • Hide-upper-limit with zero-valued.
    • Hours, Minutes, Seconds, MilliSeconds (without the hide-upper-limit option)
      • 0 hr, 20 min, 0 sec, 100 msec .
    • Hours, Minutes, Seconds MilliSeconds(with the hide-upper-limit option)
      • 20 min, 0 sec, 100 msec.
  • Hide-lower-limit with zero-valued.

• Users can set the hideZeroValues parameter by one of the following values:

  • "all" // Hide all the fields that have a zero-valued.
  • "leadingAndTrailing" // Hide all the zero fields in the leading or the training
  • "leadingOnly"
  • "trailingOnly"
  • "none" // Do not hide any zero-valued fields.

• Default Value: "none"

• Users wants to decide if they are going to round the smallest field or not.
• for example:
  • Without rounding option
    • 1 hour and 30.6 minutes.
  • With rounding option
    • 1 hour and 31 minutes.

• Users could use Temporal.Duration#round function.

• Users needs the formatting to be dependent on the locale
• For example:
  • en-US
    • 1 hour, 46 minutes and 40 seconds
  • fr-FR
    • 1 heure, 46 minutes et 40 secondes

Adding the locale in string format as a first argument.

    const formatter =
        new Intl.DurationFormat('en-US', {
            fields: [
                'hour',
                'minute',
                'second'
            ],
            style: 'short',
            hideZeroValues: 'none',
        });

    const duration =
        Temporal.Duration.from({
            hours: 2,
            minutes: 46,
            seconds: 40
        });

    console.log(formatter.format(duration));
    // output: 2 hr 46 min 40 sec