Patch

Fixes and Features

• locale-data/json/*.json files were removed from npm package.
• Fixes #190: add support for single configuration option on Intl.DataTimeFormat
• Fixes #152 & #179: Improving support for best bit on Intl.DataTimeFormat
• Improvements for Intl.NumberFormat.prototype.formatToParts() (thanks to @zbraniecki)
• Improvements for Intl.DateTimeFormat.prototype.formatToParts() (thanks to @zbraniecki )
• Improvements for Intl.getCanonicalLocales() (thanks to @zbraniecki )
• Fix defineProperty detection to work with Java7 Rhino JS (#207) (thanks to @xkr47)
• Locale en is now the default locale instead of ar. (thanks to @osela)
• Improve reg exp restore mechanism, and new option to opt-out when needed. #201 (thanks to @mtlewis)

Other changes

• npm package clean up. the package is considerable smaller now. (issue #199)
• updated test262 (thanks to @zbraniecki )

Pending Fixes

• IE8 still report some issues via travis (issue #189)
• localeData fails to register if your app is using requirejs (issue #218)

Big thanks for everyone who helped by reporting bugs, issues, and testing this new version.

Patch

• Fixed issues with Samsung and Safari browsers reported via FT Polyfill Service. Forcing window.Intl to be defined if it is not defined yet.
• Fixed issues with duplicate output for number and datetime formats

Major Release - Ecma 402 4rd Edition

Fixes and Features

This new feature aligns with Ecma-402 2016 which is about to be signed by Ecma as the 3rd edition of the EcmaScript Intl Specification: https://tc39.github.io/ecma402/2016/

It also introduce all proposals from 402 that are stage 3 or above: https://github.com/tc39/ecma402#current-proposals

• Intl.getCanonicalLocales() new feature in Ecma-402 2016 (thanks to @zbraniecki )
• Intl.NumberFormat.prototype.formatToParts() (thanks to @stasm)
• Intl.DateTimeFormat.prototype.formatToParts() (thanks to @zbraniecki )
• ToRawFixed abstract aligned with spec text (thanks to @watilde)

Other changes

• better alignment with CLDR symbols (thanks to @stasm)
• splitting internals into individual sections to match 402 organization
• revamp of the build system to use rollup and babel (stollen from @ericf )
• revamp BestFit for datetime format (diverging from spec to match browsers)
• fix wrapper to define polyfill correctly as the global Intl when needed (thanks to @jimf)
• travis unit tests are now running again (thanks to @watilde) and we have updated to the latest test262

Big thanks for everyone who helped by reporting bugs, issues, and testing this new version.

Minor Release

Fixes and Features:

• Updated to CLDR 28.0.0 from 25.0.1: PR #141, enabling a dozen new locales, and fixing multiple localization issues.
• Refactor CLDR for dates: PR #146 - This fix helps to consolidate the output format for DateTimeFormat instance to match the output of Chrome, FF and IE by taking into consideration the options provided when creating a new instance.

This release fixes the following issues: #109, #117, #125, #145 and #128.

This major release includes collaboration from @mdehoog and @ianhk, thank you guys!

Major Release

Fixes and Features:

• consolidates 1.0.0-rc-1, 2 3 and 4.
• supports for webpack/browserify bundling.
• fixes the traversing locale ancestor path.
• uses cldr nodejs packages instead of the json distro.
• improves bower configuration.

This major release includes collaborations from @Turbo87, @ollym, @okuryu, @kate2753 @mweibel and @juandopazo, thank you guys!

Release Candidate 4

• Fix the minute key name #112
• Add base formats for date and time to complement the custom available formats #111
• Take in consideration hour12 default value from each cldr date format patterns #110

Release Candidate

Features:

• new build process using ES6 modules, and other goodies.
• updated cldr (expanding the number of supported locales)
• no more intermedium step to build a subset of date formats, we now support everything that is in cldr

Bugfixes:

• #94 Fix Object.defineProperty feature detection
• #93 Use correct width for weekday names
• #91 Always include latn numeric system in locale data
• #85 supporting short month format in most cases to match browser's behavior
• #76 Unicode CLDR Version 26
• #67: massive refactor to use ES6 modules under the hood

Regression fix

Quick fix for regression introduced in v0.1.3, where some data arrays were accidentally sorted.

Data changes, bug fixes and more

Important: please use v0.1.4, which fixes a breaking regression introduced by this release.

This release brings a few noteworthy changes to the polyfill, including:

• .toLocaleString() functions are no longer overridden if the environment already supports ECMA-402.
  • The polyfill versions can still be found at IntlPolyfill.__localeSensitiveProtos and can be applied using IntlPolyfill.__applyLocaleSensitivePrototypes().
• Intl is now defined globally where it does not already exist.
• An important bug related to NumberFormat maxSignificantDigits was fixed.
• A new algorithm for finding the best matching date format was implemented.
• Data is now built with long month names instead of short ones by default.
• Tests and build tools were updated.

Note: although the build is still failing, this is due to a bug in v8 and an issue with one of the tests in IE 8.

More ES3 improvements, plus other fixes

This release contains fixes for several ES3 bugs, bringing IE 8 up to a better standard and passing all possible tests. There's also a fix for #38, an annoying Firefox issue that affected formatted number precision.