summaryrefslogtreecommitdiff
path: root/tests
diff options
context:
space:
mode:
authorTarek Mahmoud Sayed <tarekms@microsoft.com>2018-05-31 10:31:11 -0700
committerGitHub <noreply@github.com>2018-05-31 10:31:11 -0700
commit378b666a30c07937ef19ecead82e353359090245 (patch)
tree25bd14662d3f14fe6309152608f0ffcf809418ad /tests
parent5d8cdfe45b8f3c68f6a9f1c0679f941b506f6757 (diff)
downloadcoreclr-378b666a30c07937ef19ecead82e353359090245.tar.gz
coreclr-378b666a30c07937ef19ecead82e353359090245.tar.bz2
coreclr-378b666a30c07937ef19ecead82e353359090245.zip
Support new Japanese calendar eras (#18209)
Japan is going to introduce the new era next year 2019, this new era will be added to the Japanese calendar. This new era would affect anyone converting, formatting or parsing dates using the Japanese calendar. Users who formatted future dates before introducing the new era and then try to parse these dates after introducing the new era will fail and get parsing exception. The reason is the year number will not be valid in the old era anymore because the new era set a year limit to the old era. Here is an example: Format a date like "平成 32年2月1日" which saying year 32 in the era "平成". after we introduce the new era, the old era "平成" will be limited up to and including year 31 so year 32 is exceeding the era end. The fix is to allow the parser succeeds with such dates and have a config switch which can be used to for anyone want the old behavior.
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions