chore(*): Add changelog and mentions of locale.

Author: skrustev

.github/CONTRIBUTING.md

@@ -94,20 +94,31 @@ There are several ways to localize components' string resources:
     1.1. Localize a given instance of component - each component which supports localization has input property `resourceStrings`. Setting a newly instantiated object to this property will localize only that given component's instance.
     1.2. Localize all resources for a component type - each component which supports localization has input property `resourceStrings`. To localize all instances of a given component in the application the following steps should be performed - get the value of the input property `resourceStrings` of the component to be localized; do not create a new instance but replace the existing strings within the object. By default all components of a given type in an application share one instance of the resource strings. Replacing a value in that instance affects all components of that type in the application.
     1.3. Localize all resources for all components - use global method `getCurrentResourceStrings` to get an object containing current resource strings for all components. To provide localized resources just pass an object of type `IResourceStrings` to the global method `changei18n`.
+    1.4 As of 20.1.x the localization has new implementation and you can use the new API `registerI18n` to register resource string for a component or all components for the whole app, as well as which locale it corresponds to. To localize a single component you will need to get is corresponding resource string keys using one of the available resources and provide only those keys.
 
 2. Using npm package:
 We've created new repository which will hold the resource strings for languages different than English:
 https://github.com/IgniteUI/igniteui-angular-i18n 
 
-**NOTE** The localization repo has been moved to live inside the `igniteui-angular` repository under `./projects/igniteui-angular-i18n`  
+**NOTE** The localization repo has been moved to live inside the `igniteui-angular` repository under `./projects/igniteui-angular-i18n`
+**NOTE** As of 20.1.x the localization resource strings have been moved to the [`igniteui-i18n`](https://github.com/IgniteUI/igniteui-i18n) repository under `projects/igniteui-i18n-resources`.
 
 A npm package should be published each time we release new version of Ignite UI for Angular. Its version should correspond to the version of the igniteui-angular npm package.
 One could localize an application by importing the corresponding localized resource strings from the localization package (`igniteui-angular-i18n`) and use the methods described in the previous bullet to localize the whole application or part of it.
-Example:
+
+**Example:**
+
 Inside app.module you can perform:
-_import { IgxResouceStringsJA } from ‘igniteui-angular-i18n’;_
-And then:
-_Changei18n(IgxResouceStringsJA);_
+```ts
+import { IgxResouceStringsJA } from ‘igniteui-angular-i18n’;
+changei18n(IgxResouceStringsJA);
+```
+
+**Example new API:**
+```ts
+import { ResouceStringsJA } from ‘igniteui-i18n-resources’;
+registerI18n(IgxResouceStringsJA, 'ja');
+```
 
 ### Resource strings keys naming convention
 Each key in the `IResourceStrings` (and `IGridResourceStrings`, `ITimePickerResourceStrings`, etc.) is prefixed with components' selector and followed by the resource string key. Having components' selectors as prefixes allows us to have same resource strings keys for more than one component.

CHANGELOG.md

@@ -5,7 +5,12 @@ All notable changes for each version of this project will be documented in this
 
 ## 20.1.0
 ### New Features
-`IgxDateRangePicker`
+- `Internationalization`
+  - Old api is being marked as deprecated but it should remain working the same without any breaking change.
+  - New localization and locale implementation based on Intl. for all components with new public API and package named 'igniteui-i18n-resources' containing now the resources.
+  - With the new implementation locales no longer need to be registered, only language resources for components.
+
+- `IgxDateRangePicker`
   - Added cancel button to the dialog, allowing the user to cancel the selection. 
 
 - `IgxCarousel`