Date Format Locale Order Lookup

Resolve runtime locale Gregorian numeric date-part order with fixed UTC/Latin-digit unambiguous probe, not the locale’s preferred calendar, actual date parsing or current-clock dependence.

Description

Numeric date order can be inspected independently of the current clock.

Numeric date order can be inspected independently of the current clock. Fixing Gregorian calendar, UTC and Latin digits makes the probe unambiguous.^{[1, 2]}

Enter supported locale tag≤128 characters. Use runtime Intl.DateTimeFormat with forced Gregorian calendar and Latin digits; return three-letter order and probe display.

When to use Date Format Locale Order Lookup

Use Date Format Locale Order Lookup when you need to evaluate the supplied records under the calculation and evidence rules below. This does not identify the locale’s preferred calendar or parse real dates. Runtime locale data affects display.

Prepare explicit text tokens, annotated language observations, caller mappings or a supported locale as requested. Preserve source evidence and the stated Unicode counting convention.

How to use Date Format Locale Order Lookup and understand its results

Prepare explicit text tokens, annotated language observations, caller mappings or a supported locale as requested. Preserve source evidence and the stated Unicode counting convention.
Enter localeTag using the field table and calculation rules, then run the tool.
Read gregorianDatePartOrder, fixedUtcGregorianProbeDisplay. The explanation below defines the units, signs, ordering and any flags or placeholder values.
If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.

Input field	Meaning	Value type; see rules below	Requirement
localeTag	Locale tag	string	Required

Enter supported locale tag≤128 characters. Use runtime Intl.DateTimeFormat with forced Gregorian calendar and Latin digits; return three-letter order and probe display.

format 2001-11-22 UTC; concatenate Y/M/D part types in display order

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
gregorianDatePartOrder	Gregorian date part order	string
fixedUtcGregorianProbeDisplay	Fixed utc gregorian probe display	string

json

{
  "input": {
    "localeTag": "en-US"
  },
  "output": {
    "gregorianDatePartOrder": "MDY",
    "fixedUtcGregorianProbeDisplay": "11/22/2001"
  }
}

Limitations and assumptions

This does not identify the locale’s preferred calendar or parse real dates. Runtime locale data affects display.

Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Extremely large text inputs are rejected. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use Decimal Comma vs Point Region Lookup: A locale’s decimal separator need not be a comma or point. Runtime internationalization data determines the observed formatting. For a complementary task, use Number Grouping Locale Format Lookup: Integer grouping varies by locale and runtime locale data. Exact decimal text avoids loss of large integers before formatting.

Further background: ECMAScript Internationalization API.

References

Date Format Locale Order Lookup — tool.io
ECMAScript Internationalization API — Ecma International

Similar or alternative tools

Decimal Comma vs Point Region Lookup
A locale’s decimal separator need not be a comma or point. Runtime internationalization data determines the observed formatting.
Number Grouping Locale Format Lookup
Integer grouping varies by locale and runtime locale data. Exact decimal text avoids loss of large integers before formatting.