Decimal Comma vs Point Region Lookup

Probe supported caller locale decimal separator through runtime Intl/ICU, retaining non-comma/non-point separators rather than stereotyping a region; no decimal parsing or currency-format alias.

Description

A locale’s decimal separator need not be a comma or point.

A locale’s decimal separator need not be a comma or point. Runtime internationalization data determines the observed formatting.^{[1, 2]}

Enter valid supported locale tag≤128 characters. Format with no grouping and exactly one fractional digit; return separator, comma/point/other family and displayed probe.

When to use Decimal Comma vs Point Region Lookup

Use Decimal Comma vs Point Region Lookup when you need to evaluate the supplied records under the calculation and evidence rules below. No numeric parsing, currency convention or fixed region rule is supplied. Host ICU/CLDR can affect 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.

How to use Decimal Comma vs Point Region 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 observedDecimalSeparator, decimalSeparatorFamily, formattedFractionProbe. 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 valid supported locale tag≤128 characters. Format with no grouping and exactly one fractional digit; return separator, comma/point/other family and displayed probe.

probe=Intl.NumberFormat(locale).formatToParts(1.5)

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

Output field	Meaning	Value type
observedDecimalSeparator	Observed decimal separator	string
decimalSeparatorFamily	Decimal separator family	string
formattedFractionProbe	Formatted fraction probe	string

json

{
  "input": {
    "localeTag": "de-DE"
  },
  "output": {
    "observedDecimalSeparator": ",",
    "decimalSeparatorFamily": "comma",
    "formattedFractionProbe": "1,5"
  }
}

Limitations and assumptions

No numeric parsing, currency convention or fixed region rule is supplied. Host ICU/CLDR can affect results.

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 Number Grouping Locale Format Lookup: Integer grouping varies by locale and runtime locale data. Exact decimal text avoids loss of large integers before formatting. For a complementary task, use Date Format Locale Order Lookup: Numeric date order can be inspected independently of the current clock. Fixing Gregorian calendar, UTC and Latin digits makes the probe unambiguous.

Further background: ECMAScript Internationalization API.

References

Decimal Comma vs Point Region Lookup — tool.io
ECMAScript Internationalization API — Ecma International

Similar or alternative tools

Number Grouping Locale Format Lookup
Integer grouping varies by locale and runtime locale data. Exact decimal text avoids loss of large integers before formatting.
Date Format Locale Order Lookup
Numeric date order can be inspected independently of the current clock. Fixing Gregorian calendar, UTC and Latin digits makes the probe unambiguous.