Shane F. Carr

`calendar: 'indian'` is the [Indian national calendar](https://en.wikipedia.org/wiki/Indian_national_calendar). ECMA-402 doesn't currently support Lunar Hindu calendars, although there has been discussion about supporting them in Temporal. For example, see https://github.com/tc39/proposal-intl-era-monthcode/issues/18

I'm not convinced that this approach works > Did you consider when a time zone changes metazones, thereby messing up the mapping?

I'm pretty sure golden zones are not meant to be stable. But, I'm fine closing this PR and revisiting something like this when we have someone asking for it.

Thanks for the commentary. It is helpful. What is the concrete proposal? I see a few options: 1. Do nothing. The ECMA-402 preferences are in the ICU4X preferences bag, and...

CC @markusicu for feedback on the above options proposals.

I think Intl.DateTimeFormat should handle cases 3 and 4. Not just toLocaleString because (1) this is all part of the same ecosystem and (2) I'd rather not have toLocaleString contain...

It's a strange inconsistency, but I think it's harmless and likely intentional; the Intl.DateTimeFormat simply falls back to the default calendar system for the locale if the provided one is...

TG2 discussion: https://github.com/tc39/ecma402/blob/master/meetings/notes-2023-01-12.md#should-intl-apis-match-temporal-interpretation-of-calendar-and-timezone-options-741 Conclusion: "We are not doing any change at moment; I propose to revisit it after Temporal lands at Stage 4 and decide way to go. Put in...

Hi @johanrd (or anyone else here who wants to get more involved) Thanks for making the proposal repo. If you would like, please email [email protected] and we can start the...

Thank you @kalebpace for bringing this to the TC39-TG2 meeting. Discussion notes: https://github.com/tc39/ecma402/blob/main/meetings/notes-2025-11-06.md#add-kilowatt-hour-unit-to-intlnumberformat-739 It is on the agenda for advancement to Stage 1 at the TC39 meeting this week.