Skip to content

Conversation

@ben-allen
Copy link
Collaborator

Added wording specifying that Japanese Imperial era names are defined by the Japanese government.

See The Historical Background of How Japan Chooses Its Era Names. Key quote:

The Era Name Law is Japan’s shortest law, consisting of just two sentences: “1. The era name shall be determined by cabinet ordinance. 2. The era name shall be changed only in the case of a succession to the imperial throne.”

Also see description of the Japanese Imperial calendar system used in documentation for Java's JapaneseEra class:

The Japanese government defines the official name and start date of each era.

spec.emu Outdated
<tr>
<td>*"japanese"*</td>
<td>Japanese Imperial calendar, era system hybridised with *"gregory"*. Month numbers, month codes, and days are the same as in the ISO 8601 calendar, extended proleptically before their introduction in ISO year 1873. Imperial era names only extend as far back as the Meiji period (starting in ISO year 1868) during which calendar reforms took place. The arithmetic year, and the years and eras before ISO year 1868, are identical to *"gregory"*.</td>
<td>Japanese Imperial calendar, era system hybridised with *"gregory"*. Month numbers, month codes, and days are the same as in the ISO 8601 calendar, extended proleptically before their introduction in ISO year 1873. Imperial era names only extend as far back as the Meiji period (starting in ISO year 1868) during which calendar reforms took place. All era names are defined by the Japanese government. The arithmetic year, and the years and eras before ISO year 1868, are identical to *"gregory"*.</td>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe "Modern era names are defined..."? (The decision to use era names only since 1868 is JS's concession to practical implementation concerns, and bce/ce are not defined by the Japanese government)

spec.emu Outdated
<tr>
<td>*"japanese"*</td>
<td>Japanese Imperial calendar, era system hybridised with *"gregory"*. Month numbers, month codes, and days are the same as in the ISO 8601 calendar, extended proleptically before their introduction in ISO year 1873. Imperial era names only extend as far back as the Meiji period (starting in ISO year 1868) during which calendar reforms took place. The arithmetic year, and the years and eras before ISO year 1868, are identical to *"gregory"*.</td>
<td>Japanese Imperial calendar, era system hybridised with *"gregory"*. Month numbers, month codes, and days are the same as in the ISO 8601 calendar, extended proleptically before their introduction in ISO year 1873. Imperial era names only extend as far back as the Meiji period (starting in ISO year 1868) during which calendar reforms took place. All era names are defined by the Japanese government. The arithmetic year, and the years and eras before ISO year 1868, are identical to *"gregory"*.</td>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CLDR defines the era names, which are transliterations of the ones defined by the government of Japan, which defines both the eras and their cutoff dates.

@ben-allen ben-allen changed the title Normative: Add calendar authority for Japanese Imperial era names Editorial: Add calendar authority for Japanese Imperial era names Oct 1, 2025
@ben-allen
Copy link
Collaborator Author

Updated to reflect that CLDR, rather than the Japanese government, is the authority for era name transliterations. Retitled as editorial, since I believe t doesn't change any observable requirements.

@hsivonen
Copy link
Member

hsivonen commented Oct 8, 2025

Filed #86 as a follow-up, since it would be scope creep in this already-reviewed PR.

@ben-allen
Copy link
Collaborator Author

Updated to reflect outcome of discussion in 2025-10-09 TG2

@sffc
Copy link
Collaborator

sffc commented Oct 13, 2025

@ptomato ptomato merged commit ddf6fa2 into tc39:main Oct 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants