Intl.NumberFormat Unified API Proposal

This proposal adds measurement units, compact decimal notation, and other localized number formatting features to Intl.NumberFormat.

TC39 Stage 2 Proposal

TC39 Stage 3 Proposal

View Spec

Polyfill

** Status **

This proposal has been merged into ECMA-402 and is scheduled for the 2020 edition of the specification.

tc39/ecma402#404

Please file any additional issues on the main ECMA-402 repository.

https://github.com/tc39/ecma402/issues

Background / Motivation

There are many requests for adding number-formatting-related features to ECMA-402 (the JavaScript Intl standard library). These include:

• Expose narrow currency symbol -- Section I
• Clarification on behavior of SetNumberFormatDigitOptions -- Section I
• Add measure unit formatting -- Section II
• Add compact decimal notation -- Section III
• Add scientific notation -- Section III
• Add currency accounting format -- Section IV
• Add option to force sign -- Section IV

These features are important to both end users and to Google. Since most of these features require carrying along large amounts of locale data for proper i18n support, exposing these features via a JavaScript API reduces bandwidth and lowers the barrier to entry for i18n best practices.

Rather than complicate Intl with more constructors with heavilly overlapping functionality, this proposal is to restructure the spec of Intl.NumberFormat to make it more easilly support additional features in a "unified" way.

Additional background: prior discussion

I. Units

Units of measurement can be formatted as follows:

(299792458).toLocaleString("en-US", {
    style: "unit",
    unit: "meter-per-second",
    unitDisplay: "short"
});
// ==> "299,792,458 m/s"

The syntax was discussed in #3.

• style receives the string value "unit"
• unit receives a string core unit identifier, defined in UTS #35, Part 2, Section 6. A subset of units from the full list was selected for use in ECMAScript; see a discussion on the methodology for choosing the subset in #39.
• unitDisplay, named after the corresponding setting for currencies, currencyDisplay, takes either "narrow", "short", or "long".

Feature Detection: Measurement Units

Check for a RangeError when passing style: "unit":

/**
 * Returns an Intl.NumberFormat if the unit is supported,
 * or null if unsupported.
 */
function getIntlNumberFormatWithUnit(unit) {
  try {
    return new Intl.NumberFormat(undefined, {
      style: "unit",
      unit
    });
  } catch (e) {
    if (e.constructor !== RangeError) {
      throw e;
    }
    return null;
  }
}

II. Scientific and Compact Notation

Scientific and compact notation are represented by the new option notation and can be formatted as follows:

(987654321).toLocaleString("en-US", {
    notation: "scientific"
});
// ==> 9.877E8

(987654321).toLocaleString("en-US", {
    notation: "engineering"
});
// ==> 987.7E6

(987654321).toLocaleString("en-US", {
    notation: "compact",
    compactDisplay: "long"
});
// ==> 987.7 million

The syntax was discussed in #5.

• notation takes either "standard" (default), "scientific", "engineering", "compact"
• compactDisplay, used only when notation is "compact", takes either "short" (default) or "long"

Rounding-related settings (min/max integer/fraction digits) are applied after the number is scaled according to the chosen notation.

When notation is "compact" and there are no user-specified rounding options, a special compact notation rounding strategy is used: round to the nearest integer, but always keep 2 significant digits. For example, 123.4K rounds to 123K, and 1.234K rounds to 1.2K. The user can determine that the compact rounding strategy is being used in the resolvedOptions if notation is "compact" and none of the rounding settings are present.

Notation styles are allowed to be combined with other options:

(299792458).toLocaleString("en-US", {
    notation: "scientific",
    minimumFractionDigits: 2,
    maximumFractionDigits: 2,
    style: "unit",
    unit: "meter-per-second"
});
// ==> 3.00E8 m/s

Feature Detection: Notation

Check for the notation in resolvedOptions():

/**
 * Returns an Intl.NumberFormat if the notation is supported,
 * or null if unsupported.
 */
function getIntlNumberFormatWithNotation(notation) {
  let numberFormat = new Intl.NumberFormat("en-US", { notation });
  if (numberFormat.resolvedOptions().hasOwnProperty("notation")) {
    return numberFormat;
  }
  return null;
}

III. Sign Display

The sign can be displayed on positive numbers:

(55).toLocaleString("en-US", {
    signDisplay: "always"
});
// ==> +55

Currency accounting sign display is also supported via a new option. In many locales, accounting format means to wrap the number with parentheses instead of appending a minus sign. For example:

(-100).toLocaleString("bn", {
    style: "currency",
    currency: "EUR",
    currencySign: "accounting"
});
// ==> (১০০.০০€)

The syntax was discussed in #6:

• signDisplay: "auto" (default), "always", "never", "exceptZero"
  • See examples below.
• currencySign: "standard" (default), "accounting"
  • "accounting" enables the accounting format on currency values, as shown in the example above. "standard", the default value, disables accounting formats.

Examples of signDisplay choices with Latin digits:

signDisplay	-1	-0	0	1	NaN
auto	-1	-0	0	1	NaN
always	-1	-0	+0	+1	+NaN
never	1	0	0	1	NaN
exceptZero	-1	0	0	+1	NaN

Examples of signDisplay choices with Latin digits when currencySign is "accounting":

signDisplay	-1	-0	0	1	NaN
auto	($1.00)	($0.00)	$0.00	$1.00	$NaN
always	($1.00)	($0.00)	+$0.00	+$1.00	+$NaN
never	$1.00	$0.00	$0.00	$1.00	$NaN
exceptZero	($1.00)	$0.00	$0.00	+$1.00	$NaN

As usual, this may be combined with other options.

(0.55).toLocaleString("en-US", {
    style: "percent",
    signDisplay: "exceptZero"
});
// ==> +55%

Feature Detection: Sign Display

Check for the signDisplay in resolvedOptions():

/**
 * Returns an Intl.NumberFormat if the signDisplay is supported,
 * or null if unsupported.
 */
function getIntlNumberFormatWithSignDisplay(signDisplay) {
  let numberFormat = new Intl.NumberFormat("en-US", { signDisplay });
  if (numberFormat.resolvedOptions().hasOwnProperty("signDisplay")) {
    return numberFormat;
  }
  return null;
}

IV. Spec Cleanup

Certain sections of the spec have been refactored with the following objectives:

• Fix tc39/ecma402#238 (currency long name has dependency on plural form, and the currency long name pattern has dependency on currencyWidth).
• Move pattern resolution out of the constructor to keep all internal fields of NumberFormat locale-agnostic, making it easier to reason about behavior in the format method.
• Fix #2, to allow minimumIntegerDigits to control integer digit count when significant digits are used.

In addition, one missing option is added to the existing currencyDisplay setting: "narrowSymbol", which uses the CLDR narrow-format symbol:

(100).toLocaleString("en-CA", {
    style: "currency",
    currency: "USD",
    currencyDisplay: "narrowSymbol"
});
// ==> "$100" (rather than "US$100")

Feature Detection: Narrow Currency Symbol

Check for a RangeError when passing currencyDisplay: "narrowSymbol":

/**
 * Returns an Intl.NumberFormat if narrow currency is supported,
 * or null if unsupported.
 */
function getIntlNumberFormatWithNarrowCurrency(currency) {
  try {
    return new Intl.NumberFormat(undefined, {
      style: "currency",
      currency,
      currencyDisplay: "narrowSymbol"
    });
  } catch (e) {
    if (e.constructor !== RangeError) {
      throw e;
    }
    return null;
  }
}