If you are searching for how to translate dates between calendar systems, how to translate historical eras, or how to preserve BCE/CE, regnal years, lunar calendars and local year numbering across languages, treat the calendar as part of the factual content. A date is not just a string of numbers. It belongs to a system for counting years, months and days, and the same-looking year number can refer to a completely different point in time under another calendar.
Calendar translation becomes especially important in historical documents, legal records, certificates, archives, religious texts, academic writing and international forms. The translator may need to preserve an original era label, provide a target-calendar equivalent, or explain that the source uses a lunar, solar or lunisolar system. A silent conversion can help readers, but an unverified conversion can corrupt evidence.
This guide gives a practical method for translating calendar systems, historical dates and era names without changing chronology. It explains when to retain the source date, when to convert it, how to handle BCE/CE and local era systems, how to avoid false year offsets, and how to document uncertainty when the source calendar cannot be converted safely from context alone.
Why calendar translation is more than changing a date format
A calendar is a rule system for organising days into months and years. Different calendars can use different starting points, month structures, leap rules and era labels. Translation must therefore distinguish the visible notation from the underlying date.
The source may also mix systems. A modern historical article might give an ancient era name followed by a Gregorian equivalent in parentheses. A legal certificate might preserve the official local-calendar year even when an international reader expects another system. A museum label might need both because the original notation is part of the object’s provenance.
Date order is a separate issue from calendar conversion. Day-month-year, month-day-year and year-month-day conventions can be localised without changing the calendar itself. Translators should not confuse formatting with conversion.
The safest principle is evidence first. If the original calendar is part of the document’s identity, preserve it. If conversion materially helps the target reader, add a verified equivalent. If the exact conversion depends on specialised rules, location, observation or historical convention, do not improvise.
A reliable translation method
1. Identify the calendar system
Determine which calendar the source actually uses before touching the numbers. Look for era names, month names, institutional context, religious context and document origin.
2. Separate calendar conversion from date formatting
Changing 18 September to September 18 is formatting. Converting a year from one calendar to another is a factual transformation. Keep those operations conceptually separate.
3. Preserve the source notation when evidence matters
Historical, legal and archival documents often require the original date to remain visible. A translated equivalent can be added, but the source notation should not disappear if it is evidentiary.
4. Use verified conversion methods
Calendar conversion should rely on authoritative tables, institutional guidance or reliable specialised tools. Never apply a remembered year offset as a universal rule.
5. Keep era labels attached to the correct year
Era labels such as BCE/CE or named reign eras are part of the date. Do not drop them, because the same number without its era can become ambiguous or wrong.
6. Handle month names carefully
Some calendars have month names that do not map one-to-one onto Gregorian months. Translate or transliterate according to convention, and avoid substituting a Gregorian month unless a verified conversion is intended.
7. Document dual dating clearly
When both source and converted dates are useful, make the relationship explicit with parentheses, a note or a consistent style such as “source-calendar date (Gregorian equivalent).”
8. Audit chronology after translation
Check that converted dates still preserve event order, ages, reign sequences, anniversaries and durations. Chronological contradictions are strong evidence that something has gone wrong.
Twenty recurring calendar and era translation problems
1. BCE and CE
This problem appears when a historical source uses an era system based on years before and within the Common Era. A source expression such as 312 BCE may contain several layers at once: the underlying day, the calendar system, the era label, the local order of year/month/day, and assumptions about what the reader already knows. A literal transfer can preserve the digits while changing the date, or preserve the date while hiding which system produced it.
Use the target language’s established equivalent for the era label and preserve the year. Do not drop the era marker. The translator should decide whether the task is to preserve the original calendar notation, convert it for target readers, or present both. Conversion is not a stylistic rewrite; it is a factual operation that must be verified. When historical or legal evidence matters, the original notation may need to remain visible even when a target-calendar equivalent is added.
For quality assurance, verify that references to earlier and later events retain correct chronological order. Then check the date against the document’s chronology. A single wrong year offset or era boundary can make later events impossible. Where a reliable conversion cannot be verified, preserve the source notation and explain the calendar rather than guessing.
2. BC and AD conventions
This problem appears when the source uses a different English-era labeling convention. A source expression such as AD 1066 may contain several layers at once: the underlying day, the calendar system, the era label, the local order of year/month/day, and assumptions about what the reader already knows. A literal transfer can preserve the digits while changing the date, or preserve the date while hiding which system produced it.
Follow the target publication’s style while preserving the same historical year. Style conversion between AD/BC and CE/BCE should not alter chronology. The translator should decide whether the task is to preserve the original calendar notation, convert it for target readers, or present both. Conversion is not a stylistic rewrite; it is a factual operation that must be verified. When historical or legal evidence matters, the original notation may need to remain visible even when a target-calendar equivalent is added.
For quality assurance, check whether the target style guide requires the era label before or after the year. Then check the date against the document’s chronology. A single wrong year offset or era boundary can make later events impossible. Where a reliable conversion cannot be verified, preserve the source notation and explain the calendar rather than guessing.
3. Regnal years
This problem appears when a date is expressed as a year within a ruler’s reign. A source expression such as the fifth year of a monarch’s reign may contain several layers at once: the underlying day, the calendar system, the era label, the local order of year/month/day, and assumptions about what the reader already knows. A literal transfer can preserve the digits while changing the date, or preserve the date while hiding which system produced it.
Preserve the regnal form when historically important and add a verified calendar equivalent only if useful. The translator should decide whether the task is to preserve the original calendar notation, convert it for target readers, or present both. Conversion is not a stylistic rewrite; it is a factual operation that must be verified. When historical or legal evidence matters, the original notation may need to remain visible even when a target-calendar equivalent is added.
For quality assurance, confirm the ruler, accession convention and exact regnal-year counting from reliable historical sources. Then check the date against the document’s chronology. A single wrong year offset or era boundary can make later events impossible. Where a reliable conversion cannot be verified, preserve the source notation and explain the calendar rather than guessing.
4. Named national eras
This problem appears when years are counted within named eras that can change with political or dynastic transitions. A source expression such as Era X, Year 12 may contain several layers at once: the underlying day, the calendar system, the era label, the local order of year/month/day, and assumptions about what the reader already knows. A literal transfer can preserve the digits while changing the date, or preserve the date while hiding which system produced it.
Retain or translate the official era name according to target convention and verify the equivalent calendar year if one is added. The translator should decide whether the task is to preserve the original calendar notation, convert it for target readers, or present both. Conversion is not a stylistic rewrite; it is a factual operation that must be verified. When historical or legal evidence matters, the original notation may need to remain visible even when a target-calendar equivalent is added.
For quality assurance, check the exact era boundaries rather than using a generic offset. Then check the date against the document’s chronology. A single wrong year offset or era boundary can make later events impossible. Where a reliable conversion cannot be verified, preserve the source notation and explain the calendar rather than guessing.
5. Lunar calendars
This problem appears when months follow lunar cycles and do not align permanently with Gregorian months. A source expression such as the first day of a named lunar month may contain several layers at once: the underlying day, the calendar system, the era label, the local order of year/month/day, and assumptions about what the reader already knows. A literal transfer can preserve the digits while changing the date, or preserve the date while hiding which system produced it.
Keep the source lunar date unless a verified conversion is required, because month alignment changes across years. The translator should decide whether the task is to preserve the original calendar notation, convert it for target readers, or present both. Conversion is not a stylistic rewrite; it is a factual operation that must be verified. When historical or legal evidence matters, the original notation may need to remain visible even when a target-calendar equivalent is added.
For quality assurance, use a calendar-specific conversion source rather than assuming a fixed month correspondence. Then check the date against the document’s chronology. A single wrong year offset or era boundary can make later events impossible. Where a reliable conversion cannot be verified, preserve the source notation and explain the calendar rather than guessing.
6. Lunisolar calendars
This problem appears when the calendar combines lunar months with leap adjustments to track the solar year. A source expression such as an intercalary or leap month date may contain several layers at once: the underlying day, the calendar system, the era label, the local order of year/month/day, and assumptions about what the reader already knows. A literal transfer can preserve the digits while changing the date, or preserve the date while hiding which system produced it.
Preserve leap-month information explicitly; omitting it can shift the date to a different month entirely. The translator should decide whether the task is to preserve the original calendar notation, convert it for target readers, or present both. Conversion is not a stylistic rewrite; it is a factual operation that must be verified. When historical or legal evidence matters, the original notation may need to remain visible even when a target-calendar equivalent is added.
For quality assurance, confirm whether the year contains an intercalary month and how it is named. Then check the date against the document’s chronology. A single wrong year offset or era boundary can make later events impossible. Where a reliable conversion cannot be verified, preserve the source notation and explain the calendar rather than guessing.
7. Solar calendars with different year numbering
This problem appears when the calendar tracks the solar year but starts counting years from a different epoch. A source expression such as Year 2569 in a Buddhist-era system may contain several layers at once: the underlying day, the calendar system, the era label, the local order of year/month/day, and assumptions about what the reader already knows. A literal transfer can preserve the digits while changing the date, or preserve the date while hiding which system produced it.
Keep the original year or add a verified Gregorian equivalent; do not rely on a memorised offset without checking local convention. The translator should decide whether the task is to preserve the original calendar notation, convert it for target readers, or present both. Conversion is not a stylistic rewrite; it is a factual operation that must be verified. When historical or legal evidence matters, the original notation may need to remain visible even when a target-calendar equivalent is added.
For quality assurance, verify the specific national or institutional convention because year offsets can be applied differently by context. Then check the date against the document’s chronology. A single wrong year offset or era boundary can make later events impossible. Where a reliable conversion cannot be verified, preserve the source notation and explain the calendar rather than guessing.
8. Religious feast dates
This problem appears when a recurring observance is tied to a non-Gregorian calendar. A source expression such as a festival on the tenth day of a named month may contain several layers at once: the underlying day, the calendar system, the era label, the local order of year/month/day, and assumptions about what the reader already knows. A literal transfer can preserve the digits while changing the date, or preserve the date while hiding which system produced it.
Translate the festival and calendar date without pretending it always falls on the same Gregorian day. The translator should decide whether the task is to preserve the original calendar notation, convert it for target readers, or present both. Conversion is not a stylistic rewrite; it is a factual operation that must be verified. When historical or legal evidence matters, the original notation may need to remain visible even when a target-calendar equivalent is added.
For quality assurance, if a Gregorian date is supplied, verify it for the specific year. Then check the date against the document’s chronology. A single wrong year offset or era boundary can make later events impossible. Where a reliable conversion cannot be verified, preserve the source notation and explain the calendar rather than guessing.
9. Historical double dating
This problem appears when sources record dates under two calendar conventions. A source expression such as a date written with two year numbers separated by a slash may contain several layers at once: the underlying day, the calendar system, the era label, the local order of year/month/day, and assumptions about what the reader already knows. A literal transfer can preserve the digits while changing the date, or preserve the date while hiding which system produced it.
Preserve the double-date structure and explain the systems rather than collapsing to one unexplained number. The translator should decide whether the task is to preserve the original calendar notation, convert it for target readers, or present both. Conversion is not a stylistic rewrite; it is a factual operation that must be verified. When historical or legal evidence matters, the original notation may need to remain visible even when a target-calendar equivalent is added.
For quality assurance, confirm which convention each number represents. Then check the date against the document’s chronology. A single wrong year offset or era boundary can make later events impossible. Where a reliable conversion cannot be verified, preserve the source notation and explain the calendar rather than guessing.
10. Old-style and new-style dates
This problem appears when historical sources span calendar reforms. A source expression such as a date labelled Old Style may contain several layers at once: the underlying day, the calendar system, the era label, the local order of year/month/day, and assumptions about what the reader already knows. A literal transfer can preserve the digits while changing the date, or preserve the date while hiding which system produced it.
Keep the style designation or provide a clear converted equivalent with a note. The translator should decide whether the task is to preserve the original calendar notation, convert it for target readers, or present both. Conversion is not a stylistic rewrite; it is a factual operation that must be verified. When historical or legal evidence matters, the original notation may need to remain visible even when a target-calendar equivalent is added.
For quality assurance, verify which calendar reform and jurisdiction the document refers to. Then check the date against the document’s chronology. A single wrong year offset or era boundary can make later events impossible. Where a reliable conversion cannot be verified, preserve the source notation and explain the calendar rather than guessing.
11. Month-name transliteration
This problem appears when the source month name has no conventional translated form. A source expression such as a local month name in another script may contain several layers at once: the underlying day, the calendar system, the era label, the local order of year/month/day, and assumptions about what the reader already knows. A literal transfer can preserve the digits while changing the date, or preserve the date while hiding which system produced it.
Use an established transliteration and, if needed, add the calendar system or converted date for clarity. The translator should decide whether the task is to preserve the original calendar notation, convert it for target readers, or present both. Conversion is not a stylistic rewrite; it is a factual operation that must be verified. When historical or legal evidence matters, the original notation may need to remain visible even when a target-calendar equivalent is added.
For quality assurance, check official or scholarly spelling conventions. Then check the date against the document’s chronology. A single wrong year offset or era boundary can make later events impossible. Where a reliable conversion cannot be verified, preserve the source notation and explain the calendar rather than guessing.
12. Numeric-only dates
This problem appears when the source shows only digits and separators. A source expression such as 03/04/2026 may contain several layers at once: the underlying day, the calendar system, the era label, the local order of year/month/day, and assumptions about what the reader already knows. A literal transfer can preserve the digits while changing the date, or preserve the date while hiding which system produced it.
Determine source locale before reformatting. The string may mean 3 April or March 4. The translator should decide whether the task is to preserve the original calendar notation, convert it for target readers, or present both. Conversion is not a stylistic rewrite; it is a factual operation that must be verified. When historical or legal evidence matters, the original notation may need to remain visible even when a target-calendar equivalent is added.
For quality assurance, use document origin and surrounding dates to resolve order; do not guess from target convention. Then check the date against the document’s chronology. A single wrong year offset or era boundary can make later events impossible. Where a reliable conversion cannot be verified, preserve the source notation and explain the calendar rather than guessing.
13. Year-first dates
This problem appears when the source uses year-month-day order. A source expression such as 2026-09-18 may contain several layers at once: the underlying day, the calendar system, the era label, the local order of year/month/day, and assumptions about what the reader already knows. A literal transfer can preserve the digits while changing the date, or preserve the date while hiding which system produced it.
Retain ISO-like order when technical consistency matters or localise presentation according to project style. The translator should decide whether the task is to preserve the original calendar notation, convert it for target readers, or present both. Conversion is not a stylistic rewrite; it is a factual operation that must be verified. When historical or legal evidence matters, the original notation may need to remain visible even when a target-calendar equivalent is added.
For quality assurance, ensure reformatting does not swap month and day. Then check the date against the document’s chronology. A single wrong year offset or era boundary can make later events impossible. Where a reliable conversion cannot be verified, preserve the source notation and explain the calendar rather than guessing.
14. Academic historical dates
This problem appears when a scholarly article compares multiple chronologies. A source expression such as a local era date followed by a Gregorian date may contain several layers at once: the underlying day, the calendar system, the era label, the local order of year/month/day, and assumptions about what the reader already knows. A literal transfer can preserve the digits while changing the date, or preserve the date while hiding which system produced it.
Preserve both when the comparison is analytically useful and apply one consistent dual-date style. The translator should decide whether the task is to preserve the original calendar notation, convert it for target readers, or present both. Conversion is not a stylistic rewrite; it is a factual operation that must be verified. When historical or legal evidence matters, the original notation may need to remain visible even when a target-calendar equivalent is added.
For quality assurance, check all equivalents against the cited scholarly source. Then check the date against the document’s chronology. A single wrong year offset or era boundary can make later events impossible. Where a reliable conversion cannot be verified, preserve the source notation and explain the calendar rather than guessing.
15. Museum object dates
This problem appears when the source date is part of provenance and may use historical notation. A source expression such as dated to Year X of Era Y may contain several layers at once: the underlying day, the calendar system, the era label, the local order of year/month/day, and assumptions about what the reader already knows. A literal transfer can preserve the digits while changing the date, or preserve the date while hiding which system produced it.
Keep the original historical dating system visible and add a modern equivalent only as supplementary information. The translator should decide whether the task is to preserve the original calendar notation, convert it for target readers, or present both. Conversion is not a stylistic rewrite; it is a factual operation that must be verified. When historical or legal evidence matters, the original notation may need to remain visible even when a target-calendar equivalent is added.
For quality assurance, avoid replacing the object’s source-era identity with only a modern date. Then check the date against the document’s chronology. A single wrong year offset or era boundary can make later events impossible. Where a reliable conversion cannot be verified, preserve the source notation and explain the calendar rather than guessing.
16. Birth certificates
This problem appears when official records use the issuing jurisdiction’s calendar and date format. A source expression such as a civil record with a local-calendar year may contain several layers at once: the underlying day, the calendar system, the era label, the local order of year/month/day, and assumptions about what the reader already knows. A literal transfer can preserve the digits while changing the date, or preserve the date while hiding which system produced it.
Translate the labels while preserving the official recorded date; add conversion only if the receiving authority requires it. The translator should decide whether the task is to preserve the original calendar notation, convert it for target readers, or present both. Conversion is not a stylistic rewrite; it is a factual operation that must be verified. When historical or legal evidence matters, the original notation may need to remain visible even when a target-calendar equivalent is added.
For quality assurance, follow the receiving institution’s certified-translation requirements. Then check the date against the document’s chronology. A single wrong year offset or era boundary can make later events impossible. Where a reliable conversion cannot be verified, preserve the source notation and explain the calendar rather than guessing.
17. Legal deadlines
This problem appears when a date controls rights, filings or obligations. A source expression such as within 30 days of 15 MonthName Year X may contain several layers at once: the underlying day, the calendar system, the era label, the local order of year/month/day, and assumptions about what the reader already knows. A literal transfer can preserve the digits while changing the date, or preserve the date while hiding which system produced it.
Preserve the official date and convert only with verified legal guidance. A calendar error can change the deadline. The translator should decide whether the task is to preserve the original calendar notation, convert it for target readers, or present both. Conversion is not a stylistic rewrite; it is a factual operation that must be verified. When historical or legal evidence matters, the original notation may need to remain visible even when a target-calendar equivalent is added.
For quality assurance, cross-check the issuing authority’s calendar and date computation rules. Then check the date against the document’s chronology. A single wrong year offset or era boundary can make later events impossible. Where a reliable conversion cannot be verified, preserve the source notation and explain the calendar rather than guessing.
18. Anniversaries and ages
This problem appears when age or elapsed time depends on the translated date. A source expression such as turned 50 on the converted date may contain several layers at once: the underlying day, the calendar system, the era label, the local order of year/month/day, and assumptions about what the reader already knows. A literal transfer can preserve the digits while changing the date, or preserve the date while hiding which system produced it.
Verify that the conversion preserves the same birthday and year count. The translator should decide whether the task is to preserve the original calendar notation, convert it for target readers, or present both. Conversion is not a stylistic rewrite; it is a factual operation that must be verified. When historical or legal evidence matters, the original notation may need to remain visible even when a target-calendar equivalent is added.
For quality assurance, recalculate age independently after conversion. Then check the date against the document’s chronology. A single wrong year offset or era boundary can make later events impossible. Where a reliable conversion cannot be verified, preserve the source notation and explain the calendar rather than guessing.
19. Approximate historical dates
This problem appears when the source uses circa or another uncertainty marker. A source expression such as c. 1450 may contain several layers at once: the underlying day, the calendar system, the era label, the local order of year/month/day, and assumptions about what the reader already knows. A literal transfer can preserve the digits while changing the date, or preserve the date while hiding which system produced it.
Preserve the uncertainty marker. Conversion should not make an approximate source look exact. The translator should decide whether the task is to preserve the original calendar notation, convert it for target readers, or present both. Conversion is not a stylistic rewrite; it is a factual operation that must be verified. When historical or legal evidence matters, the original notation may need to remain visible even when a target-calendar equivalent is added.
For quality assurance, keep circa, approximate, before/after or range language attached to the date. Then check the date against the document’s chronology. A single wrong year offset or era boundary can make later events impossible. Where a reliable conversion cannot be verified, preserve the source notation and explain the calendar rather than guessing.
20. Unknown calendar context
This problem appears when a number looks like a year but the calendar cannot be confidently identified. A source expression such as Year 1385 in an isolated inscription may contain several layers at once: the underlying day, the calendar system, the era label, the local order of year/month/day, and assumptions about what the reader already knows. A literal transfer can preserve the digits while changing the date, or preserve the date while hiding which system produced it.
Do not silently convert. Retain the source notation and state the uncertainty or calendar identification if known. The translator should decide whether the task is to preserve the original calendar notation, convert it for target readers, or present both. Conversion is not a stylistic rewrite; it is a factual operation that must be verified. When historical or legal evidence matters, the original notation may need to remain visible even when a target-calendar equivalent is added.
For quality assurance, seek contextual or specialist evidence before adding an equivalent. Then check the date against the document’s chronology. A single wrong year offset or era boundary can make later events impossible. Where a reliable conversion cannot be verified, preserve the source notation and explain the calendar rather than guessing.
Common failure modes
1. Using a fixed year offset for every date
Offsets can depend on era boundaries, new-year conventions and historical context. Verify rather than memorise.
2. Confusing formatting with conversion
Changing order or month names is not the same as changing calendars. Treat them as separate operations.
3. Dropping era labels
A bare year can become ambiguous or historically wrong without BCE/CE, regnal or named-era information.
4. Replacing evidence with a modern date
Historical and legal sources may require the original notation to remain visible even when a conversion is added.
5. Guessing ambiguous numeric dates
03/04 can represent different dates across locales. Resolve source convention first.
6. Assuming lunar months match Gregorian months
They do not align permanently. A specific year must be verified.
7. Making approximate dates exact
Preserve circa, ranges and uncertainty instead of manufacturing precision through conversion.
8. Failing to audit chronology
A conversion can look plausible in isolation while breaking event order, age or reign sequence. Check the timeline.
Worked practice
Practice 1: A historical article
Situation: The source gives a regnal year and a modern equivalent.
Reasoning: Preserve the regnal form because it is historically meaningful and verify the equivalent against a reliable historical source.
Practice 2: An ambiguous numeric date
Situation: A certificate says 04/05/2026 with no month name.
Reasoning: Determine the issuing locale and document convention before reformatting. Do not infer from the target reader’s habits.
Practice 3: A lunar festival
Situation: The event occurs on a named lunar date.
Reasoning: Keep the lunar date and convert only for the specific year if a verified equivalent is useful.
Practice 4: A museum label
Situation: An object is dated by a named national era.
Reasoning: Retain the era date as provenance and add a modern-calendar equivalent in parentheses if the museum style calls for it.
Practice 5: A legal deadline
Situation: A filing date uses the local official calendar.
Reasoning: Preserve the official date and use only verified institutional conversion because rights can depend on the exact day.
Practice 6: An approximate ancient date
Situation: The source says c. 300 BCE.
Reasoning: Keep both circa and the era label. Do not turn the approximation into an exact target date.
Practice 7: A dual-dated archive
Situation: The source prints two dates under old and new calendar styles.
Reasoning: Keep both with clear labels rather than selecting one and erasing the documentary evidence.
Practice 8: A local year-numbering system
Situation: The year is expressed using a national era rather than Gregorian numbering.
Reasoning: Translate or transliterate the era name consistently and verify any Gregorian equivalent with an authoritative conversion source.
Conversion tools, archives and AI
Reliable calendar conversion requires specialised evidence. Institutional archives, official calendar authorities, scholarly chronologies and well-documented conversion tools are stronger than general search snippets. For high-stakes documents, record the source used for conversion.
AI can explain calendar systems and suggest likely equivalents, but it should not be trusted as the final arithmetic authority for historical or legal dates. Ask it to state assumptions, then verify independently.
A timeline is a powerful QA tool. List the translated dates in order and compare them with ages, reigns, durations and events. Chronological contradictions often reveal conversion mistakes faster than line-by-line proofreading.
How this fits the wider eduKate translation system
Calendar translation sits where language meets factual integrity. The broader method is developed in Master Art of Translation | The Complete System for Moving Meaning Between Languages. Vocabulary depth connects to the Vocabulary Learning Hub, while temporal expressions, deixis and event order connect to How English Works. Calendar work adds one more discipline: verify the chronology, not just the wording.
FAQ
Should I always convert dates into the Gregorian calendar?
No. Preserve the source calendar when it is legally, historically or culturally important. Add a Gregorian equivalent only when useful and verified.
Is changing day-month-year to month-day-year a calendar conversion?
No. That is date formatting. The underlying calendar date remains the same.
Can I use a fixed offset to convert calendar years?
Not safely as a universal rule. Era boundaries, new-year conventions and historical systems can make simple offsets wrong.
How should BCE/CE be translated?
Use the target language’s established era labels and keep the year and chronology unchanged.
What if the source uses a lunar calendar?
Preserve the lunar date unless a conversion is required, then verify the exact year with an appropriate conversion source.
How should regnal years be handled?
Keep the regnal form when historically meaningful and add a verified equivalent only if useful.
What if a numeric date is ambiguous?
Determine the source locale or document convention before reformatting. Do not guess.
Can AI convert historical calendars reliably?
It can assist, but high-stakes conversions should be checked against authoritative or specialised sources.
Should approximate dates stay approximate?
Yes. Preserve circa, ranges, before/after markers and other uncertainty.
What is the simplest calendar-translation rule?
Identify the calendar first; convert only with evidence.
Final checklist
- Have I identified the source calendar system?
- Am I formatting a date or actually converting calendars?
- Does the source era label remain attached to the correct year?
- Is the original date evidentiary and therefore worth preserving?
- Have I verified any converted equivalent?
- Did I resolve ambiguous numeric order from source context?
- Have I preserved leap/intercalary month information where relevant?
- Are approximate dates still approximate?
- Does the translated timeline remain chronologically coherent?
- For legal or official records, have I followed the receiving institution’s requirements?
Calendar translation is factual translation. The visible date belongs to a system, and a system cannot be replaced safely by intuition. Identify the calendar, preserve the original notation when evidence matters, separate formatting from conversion, verify every converted equivalent and audit the resulting timeline. When those disciplines are followed, readers can move between calendar traditions without losing the actual day, year or historical sequence the source intended.