Islamic Dirham Hijri Mint Date Conversion Calculator
Convert a full caller Hijri date under the civil tabular Islamic calendar epoch (16 July 622 Julian); coin year alone and historical lunar observation do not establish an exact mint date.
Description
Convert a full caller Hijri date under the civil tabular Islamic calendar epoch (16 July 622 Julian); coin year alone and historical lunar observation do not establish an exact mint date.
A tabular Islamic calendar conversion is a reproducible arithmetic model, distinct from reconstructing a historically observed mint date. A full year/month/day is needed for a specific day conversion.
When to use this tool
Convert a full caller Hijri date under the civil tabular Islamic calendar epoch (16 July 622 Julian); coin year alone and historical lunar observation do not establish an exact mint date.
- Prepare the supplied hijriYear, hijriMonth, hijriDay fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter hijriYear, hijriMonth, hijriDay. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.prolepticGregorianDate, result.calendar, result.historicalMintDateConfirmed. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Validate the civil tabular calendar's alternating month lengths and thirty-year leap cycle. Count days from the implementation's proleptic Gregorian epoch 0622-07-19 and shift that date, returning the calendar label and historicalMintDateConfirmed false.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| hijriYear | hijri year. | Integer from 1 to 5000 inclusive |
| hijriMonth | hijri month. | Integer from 1 to 12 inclusive |
| hijriDay | hijri day. | Integer from 1 to max inclusive |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.prolepticGregorianDate | The proleptic gregorian date value under the stated formula or text convention. |
| result.calendar | The calendar value under the stated formula or text convention. |
| result.historicalMintDateConfirmed | Always false: an arithmetic calendar conversion does not confirm historical mint practice. |
{
"input": {
"hijriYear": 1,
"hijriMonth": 1,
"hijriDay": 1
},
"output": {
"result": {
"prolepticGregorianDate": "0622-07-19",
"calendar": "arithmetic-civil-tabular-Islamic",
"historicalMintDateConfirmed": false
}
}
}Limitations and assumptions
- The input year is limited to 1–5000. Local observation, historical calendar practice and uncertain coin inscriptions are not resolved; the tool does not infer a day from a year-only inscription.
- Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
- Ordinary string lists have at most 128 entries of at most 128 code units each; numeric lists and matrices have separate bounded size checks. Nonfinite results and excessively large serialized outputs are rejected.
- Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.
Alternative or Complementary methods
Compare a tabular calendar conversion with the inscription, mint context and historical calendar evidence. Arithmetic dates can organize research, while authentication and historical attribution require independent examination.
References
Similar or alternative tools
- seleucid era to bc conversion calculator
Seleucid-era year labels need an epoch convention and a civil-year span.
- umayyad abbasid dirham mint cities geography lookup
A dirham mint attribution depends on the legend, calendar convention, period and mint geography.