From 4955cc666484fd45b135935c3474d9925824042f Mon Sep 17 00:00:00 2001 From: Ron Petrusha Date: Mon, 10 Dec 2018 16:23:06 -0800 Subject: [PATCH 1/2] Added information on next Japanese calendar era --- docs/standard/datetime/working-with-calendars.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/standard/datetime/working-with-calendars.md b/docs/standard/datetime/working-with-calendars.md index b615fc08eccfe..955b16ae43df4 100644 --- a/docs/standard/datetime/working-with-calendars.md +++ b/docs/standard/datetime/working-with-calendars.md @@ -131,6 +131,9 @@ However, there is one important exception. The default (uninitialized) value of Calendars typically divide dates into eras. However, the classes in .NET do not support every era defined by a calendar, and most of the classes support only a single era. Only the and classes support multiple eras. +> [!IMPORTANT] +> A new era in the and begins on May 1, 2019. This change affects all applications that use these calendars. See [Handling a new era in the Japanese calendar in .NET](https://blogs.msdn.microsoft.com/dotnet/2018/11/14/handling-a-new-era-in-the-japanese-calendar-in-net/) for more information and to determine whether your applications are affected. See [Prepare your application for the Japanese era change](~/windows/uwp/design/globalizing/japanese-era-change) for information on testing your applications to ensure their readiness for the era change. + ### Eras and era names In .NET, integers that represent the eras supported by a particular calendar implementation are stored in reverse order in the array. The current era is at index zero, and for classes that support multiple eras, each successive index reflects the previous era. The static property defines the index of the current era in the array; it is a constant whose value is always zero. Individual classes also include static fields that return the value of the current era. They are listed in the following table. From 97ed992da4161eaea56ff3d94fe7232512d381a7 Mon Sep 17 00:00:00 2001 From: Ron Petrusha Date: Tue, 11 Dec 2018 08:29:19 -0800 Subject: [PATCH 2/2] Noted testing is for Windows only --- docs/standard/datetime/working-with-calendars.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/standard/datetime/working-with-calendars.md b/docs/standard/datetime/working-with-calendars.md index 955b16ae43df4..5a0604837a89b 100644 --- a/docs/standard/datetime/working-with-calendars.md +++ b/docs/standard/datetime/working-with-calendars.md @@ -132,7 +132,7 @@ However, there is one important exception. The default (uninitialized) value of Calendars typically divide dates into eras. However, the classes in .NET do not support every era defined by a calendar, and most of the classes support only a single era. Only the and classes support multiple eras. > [!IMPORTANT] -> A new era in the and begins on May 1, 2019. This change affects all applications that use these calendars. See [Handling a new era in the Japanese calendar in .NET](https://blogs.msdn.microsoft.com/dotnet/2018/11/14/handling-a-new-era-in-the-japanese-calendar-in-net/) for more information and to determine whether your applications are affected. See [Prepare your application for the Japanese era change](~/windows/uwp/design/globalizing/japanese-era-change) for information on testing your applications to ensure their readiness for the era change. +> A new era in the and begins on May 1, 2019. This change affects all applications that use these calendars. See [Handling a new era in the Japanese calendar in .NET](https://blogs.msdn.microsoft.com/dotnet/2018/11/14/handling-a-new-era-in-the-japanese-calendar-in-net/) for more information and to determine whether your applications are affected. See [Prepare your application for the Japanese era change](~/windows/uwp/design/globalizing/japanese-era-change) for information on testing your applications on Windows to ensure their readiness for the era change. ### Eras and era names