http://en.wikipedia.org/wiki/Year_2038_problem

formatting date and time values for years >=2038 or <=1901 is now possible also with intl extension is
installed. 32bit systems will fall back to the PHP implementation because intl uses a 32bit UNIX timestamp internally.
On a 64bit system the intl formatter is used in all cases if installed.

fixes #5577

fixes #5503

fixes #6263 and has no problem with PHP Bug:

> it is a PHP bug: https://bugs.php.net/bug.php?id=45543
> Fixed in this commit: php/php-src@22dba2f#diff-7b738accc3d60f74c259da18588ddc5dL2996
>
> Fixed in PHP >5.4.26 and >5.5.10. http://3v4l.org/mlZX7

fixes #5448

fixes #5683

Fixes #5467: Added ability to pass HTML tag options to `asEmail()`, `asImage()` and `asUrl()` methods of `yii\i18n\Formatter`

fixes #5179

close #5261

related to #5128

fixes #4989

Enhances `normalizeDateTimeValue` to return a DateTime object instead of a converted double value, that fails. The DateTime object input is supported by 32 bit, 64 bit, as well as the `IntlDateFormatter` to format all years. (including fixing of the Y2K38 bug). Fixes issue in #4989.

close #5000

use "just now" for empty time difference in Formatter.

fixed wrong language name definition

adding and reworking the conversion of:
- ICU to PHP
- PHP to ICU
- ICU to JUI
- PHP to JUI

This fix ensures the format configured in the formatter class is used in the message instead
of the default ICU format.

fixes #4960

ensure some features that were recently added to formatter keep working after refactoring

exclude parts that have different default values