Localization and Multilingual Content

International Date and Number Check

Validate localized dates, time zones, currencies, units, decimal and thousands separators, numerical ranges, plural forms, and conversion precision.

Free editable Markdown · Localization reviewers, editors, and QA teams · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Value record

String or field ID: [Stable identifier]
Target locale: [Locale code and region]
Content surface: [Page, form, email, chart, PDF, export]
Value type: [Date, time, currency, unit, percentage, range, count]
Source value: [Unformatted original]
Source unit/currency/zone: [Exact]
Effective date or period: [If relevant]
Required precision: [Decimals or significant figures]
Authoritative owner: [Product, finance, data, policy, other]

Localized display

Displayed value: [Exact rendered output]
Format rule: [Date order, separators, symbol placement]
Conversion factor: [Source and date or None]
Rounding method: [Rule]
Plural or grammatical form: [Full phrase]
Ambiguity risk: [Symbol, date order, range, negative, zone]
Boundary tests: [0, 1, fraction, negative, large, transition]
Decision: [Approve, revise, escalate]

QA checks

Underlying values were verified before formatting.
Dates avoid ambiguous numeric presentation where risk matters.
Time zones and daylight-saving behavior are explicit.
Currency code, billing basis, and tax assumptions are clear.
Conversions preserve justified precision.
Separators and ranges remain clear in inputs and exports.
Plural and agreement rules are tested in complete strings.
Web, email, document, chart, and assistive text agree.

How to use this template

Inventory every localized date, time, duration, currency, measurement, percentage, range, and quantity.
Capture authoritative source value, unit, zone, currency, period, and precision.
Verify conversion, rounding, separators, ordering, plural grammar, and labels for the target locale.
Test boundaries plus every rendered and downloadable surface.
Resolve discrepancies with qualified owners and document ongoing update triggers.

Separate value from presentation

Record the source value, type, unit, currency, time zone, precision, and effective date before reviewing localized display. A date such as 03/04/2026 is ambiguous without a defined format. A timestamp needs to distinguish event time from publication or system-entry time. A price needs currency code, billing basis, tax treatment, and region. Verify the underlying value first, then evaluate whether locale rules display it in a familiar, unambiguous form.

Check transformations and grammar

Document exchange rate source and date, physical-unit conversion factor, rounding, negative-number treatment, ranges, and significant figures. Converted measurements should not gain false precision. Ensure decimal and thousands separators cannot be confused in tables, input fields, exports, or copied text. Check plural categories, grammatical agreement, ordinal forms, compact notation, and digit systems in full sentences. A number placeholder may require different surrounding words depending on its value.

Test boundaries and interfaces

Include zero, one, fractions, negative values, very large values, start and end of month or year, daylight-saving changes, and unavailable data. Verify form inputs accept or explain expected separators without corrupting values. In bilingual contexts, use labels or currency codes when symbols could refer to several currencies. Recheck emails, PDFs, charts, alt text, API-derived content, and downloadable files. Assign update triggers for rate, price, tax, policy, or timezone-rule changes.

See the fields in context

Fictional example: international workshop booking

Open Loom is an invented workshop service; all prices and dates are illustrative.

Source: Fictional event starts at `2026-11-02T17:00:00Z` and costs EUR 1,250.50 before local tax.
Locale display: German version uses “2. November 2026, 18:00 MEZ” after the invented zone check.
Price: “1.250,50 EUR zzgl. anwendbarer Steuer” is reviewed by qualified fictional owners rather than translated automatically.
Input test: The form explains accepted decimal format and stores the normalized value without changing it.
Boundary: No exchange-rate conversion is displayed because no approved rate source or billing option exists.

Frequently asked questions

Is locale-aware formatting enough?

No. It can format a value but cannot verify the underlying amount, unit, billing rule, event meaning, or correct time zone.

Should currencies use symbols or codes?

Use the form clearest for the audience and context. Add a currency code when a symbol could refer to several currencies.

How should converted units be rounded?

Use precision supported by the original measurement and relevant convention. Do not add decimals that imply greater accuracy.

What requires retesting after a release?

Retest affected formats when locale libraries, time-zone data, prices, rates, taxes, product rules, or content surfaces change.