Skip to content

Commit ac99716

Browse files
authored
[SF-0017] Expanded Calendar Support (#1202)
Remove Thai Calendar
1 parent 93e3bac commit ac99716

File tree

1 file changed

+2
-6
lines changed

1 file changed

+2
-6
lines changed

Proposals/0017-expanded-calendar-support.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@
1414

1515

1616

17-
This proposal is for adding expanded support for several calendars used in South Asia, lunisolar and solar calendars used in regions in India, as well as Thai, Vietnamese and Korean calendars based on the Chinese lunisolar calendar. Swift-foundation-icu repository will support these too, so users of Foundation on any platform will get these new calendars.
17+
This proposal is for adding expanded support for several lunisolar and solar calendars used in South Asia, as well as Vietnamese and Korean calendars that based on the Chinese lunisolar calendar. Swift-foundation-icu repository will support these too, so users of Foundation on any platform will get these new calendars.
1818

1919
Some of these calendars are astronomical calendars, which means they are using true positions of sun (solar) or both sun and moon. For that reason, when specific set of events happen, the dates in these calendars can have both leap months and leap days.
2020

@@ -75,10 +75,6 @@ Foundation will add new string constants for new calendar identifiers for NSCale
7575
@available(FoundationPreview 6.2, *)
7676
case vikram
7777

78-
// Thai lunisolar calendar
79-
@available(FoundationPreview 6.2, *)
80-
case thai
81-
8278
// Vietnamese lunisolar calendar
8379
@available(FoundationPreview 6.2, *)
8480
case vietnamese
@@ -106,7 +102,7 @@ public enum Component : Sendable {
106102

107103
## Impact on existing code
108104

109-
Thai, Vietnamese and Korean calendars have no special considerations.
105+
Vietnamese and Korean calendars have no special considerations.
110106

111107
Calendars used in India are introducing the new field for the leap day. Clients using existing calendars won't be affected by this change. For new clients that use these calendars, we will handle the newly added leap day in the following places:
112108

0 commit comments

Comments
 (0)