Localizing a page is more than translating its words. Dates, times, numbers, measurements, and currencies can change meaning when they cross borders. This guide explains how to format these values for different languages and countries, how to estimate the review effort for a multilingual project, and how to build a repeatable process for websites, invoices, product pages, emails, and spreadsheets.
Overview
A format that looks clear in one market may be ambiguous or unfamiliar in another. For example, 03/04/2026 can mean March 4 in one locale and April 3 in another. A price such as 1,234.50 may be read correctly by an English-speaking audience but appear inconsistent in a market that uses a comma as the decimal separator.
Good multilingual content localization treats formatting as part of the user experience. The goal is not simply to replace symbols. It is to make every value easy to interpret, appropriate to the target locale, and consistent across the full customer journey.
Use these principles as a starting point:
- Store dates, times, and numeric values in structured fields rather than as uneditable text whenever possible.
- Display values according to the audience’s locale, language, time zone, and currency.
- Show enough context to remove ambiguity, especially for dates, deadlines, appointments, and prices.
- Separate translation, formatting, and legal or financial review instead of assuming one replaces the others.
- Test long month names, large numbers, negative values, zero values, and missing data before publication.
Quick locale comparison
The examples below are illustrative formatting patterns, not a substitute for checking the exact locale selected in your content management system or application.
| Locale pattern | Date example | Time example | Number example | Currency example |
|---|---|---|---|---|
| United States English | 12/31/2026 | 2:30 PM | 1,234.56 | $1,234.56 |
| United Kingdom English | 31/12/2026 | 14:30 or 2:30 pm | 1,234.56 | £1,234.56 |
| German | 31.12.2026 | 14:30 | 1.234,56 | 1.234,56 € |
| French | 31/12/2026 | 14:30 | 1 234,56 | 1 234,56 € |
| Japanese | 2026/12/31 | 14:30 | 1,234.56 | ¥1,234.56 |
Country, language, platform, and audience conventions can differ. For production systems, use a locale-aware date and number formatter instead of manually inserting punctuation. Also decide whether the product should follow the visitor’s browser locale, an account setting, a billing address, or a market-specific site version.
How to estimate the localization and review effort
Before launching multilingual content, estimate the number of values that need formatting review. This helps editors plan work without assigning a price or time estimate based only on word count.
Use this simple formula:
Review units = number of locale versions × number of value types × complexity factor
Count a value type separately when it has different rules or failure risks. Typical types include dates, times, time zones, decimal numbers, percentages, measurements, currencies, phone numbers, addresses, and spreadsheet formulas.
For the complexity factor, use a consistent internal scale:
- 1 — Low: static copy with a few obvious examples, such as a publication date.
- 2 — Medium: repeated values, responsive layouts, or basic currency and measurement conversion.
- 3 — High: dynamic data, recurring billing, time-zone conversion, accounting rules, tax-sensitive displays, or spreadsheet calculations.
For example, a product page translated into three locale versions may include four value types: delivery date, price, percentage discount, and product weight. If the page uses dynamic prices and date calculations, assign a complexity factor of 2. The estimate is therefore 3 × 4 × 2 = 24 review units. The number is not a quote; it is a way to compare projects and identify where additional testing is needed.
Increase the estimate when values appear in multiple places, such as a product page, checkout, confirmation email, invoice, account dashboard, and downloadable document. A translated interface can be linguistically correct while still showing inconsistent values across those surfaces.
Inputs and assumptions
Dates and calendars
Do not rely on a numeric date alone when the date affects a purchase, deadline, appointment, or legal document. Prefer a month name, an unambiguous order, or both. For example, “31 December 2026” is clearer across many audiences than “12/31/2026.” When space is limited, add a tooltip, accessible label, or localized long-date version.
Confirm whether your system stores a date only or a date-and-time value. A birthday, invoice date, and event starting time should not necessarily be processed in the same way. If a date is tied to a moment, store it consistently and convert it for display only at the final user-facing stage.
Times and time zones
Decide whether the time is shown in the visitor’s time zone, the event’s time zone, or the organization’s time zone. State the zone when an appointment, webinar, delivery window, or deadline involves people in different regions. “09:00 UTC,” “9:00 AM Eastern Time,” and “09:00 in Berlin” are more useful than an unexplained time.
Test daylight-saving transitions where relevant, as well as midnight, noon, and times near a date boundary. A conversion that moves an event to the next calendar day can change the meaning of an email or booking confirmation.
Numbers, measurements, and percentages
Check the decimal separator, thousands separator, grouping pattern, negative sign, percentage placement, and spacing. Also decide whether measurements are converted or simply displayed in the original unit. A product advertised in kilograms, centimeters, or liters may require a different presentation for another market, but conversion can introduce rounding choices.
Keep the underlying value at sufficient precision and round only for display unless a business rule requires otherwise. Document whether “10%” is calculated before or after a discount, tax, shipping charge, or currency conversion. This prevents translated labels from hiding inconsistent calculations.
Currencies and prices
Currency localization involves more than changing a symbol. Confirm the currency code, symbol placement, decimal precision, spacing, grouping, rounding behavior, and whether the price is a total, an installment, or a starting amount. A symbol such as “$” may represent more than one currency, so include a code or market context when the audience could be uncertain.
Separate the displayed currency from the transaction currency. A website may show a localized estimate while charging in a different currency. If so, explain the distinction near the price and repeat it at checkout or on the invoice.
Worked examples
Example 1: Product launch date
Suppose the source value is a structured date: 2026-12-31. For a US English page, display “December 31, 2026.” For a UK English page, display “31 December 2026.” For a Japanese page, use a Japanese date pattern appropriate to the product’s locale settings. Avoid placing the raw ISO-style value in prominent marketing copy unless the audience is expected to recognize it.
For technical systems, an ISO 8601-style value can remain useful in metadata, APIs, or machine-readable fields while the visible page uses a localized format. This allows search engines, software, and users to receive the form each one needs.
Example 2: Price and discount
A source record contains a base price of 1234.56 and a discount rate of 0.15. The interface should calculate the result from numeric fields, then format the price for each locale. Do not translate a preformatted string such as “$1,234.56” and expect punctuation or symbol placement to update reliably.
Before publishing, check the original price, discounted price, discount label, currency code, and rounding result together. A reviewer should also confirm that the same values appear consistently in product cards, the product detail page, the cart, confirmation email, and invoice.
Example 3: Spreadsheet and document delivery
When translating a spreadsheet or document, preserve the distinction between a stored date or number and its visible format. A spreadsheet may interpret “04/05/2026” differently depending on regional settings. Use explicit date formatting, document the intended locale, and inspect exported PDFs because a correct source formula can still produce a confusing final layout.
For a practical review, select one small, one large, one negative, one zero, and one missing value. Then test a long translated label beside each value. This reveals both formatting errors and layout problems before a full content review.
When to recalculate or revisit the format
Revisit your localization rules whenever you add a market, change a payment or commerce platform, alter a CMS locale configuration, introduce a new currency, or redesign a responsive component. Recalculate the review-unit estimate when the number of locales, value types, or dynamic data sources changes.
Run a focused audit before:
- launching a new language or country version;
- changing prices, discounts, subscription intervals, or measurement units;
- publishing a seasonal campaign with dates and deadlines;
- migrating a website, spreadsheet, checkout, or invoicing system;
- adding automated translation or AI-assisted content workflows;
- receiving reports that users misunderstand dates, prices, or appointment times.
Finish with a locale-specific checklist: date order, month and weekday names, time zone, 12-hour or 24-hour display, decimal and grouping separators, currency code and symbol, rounding, units, accessible labels, metadata, and exported files. Record the chosen conventions in your translation glossary or style guide, then link the rule to the structured field that generates the value. That combination—documented assumptions, locale-aware formatting, and repeatable QA—keeps multilingual content clear as markets, platforms, and campaign inputs change.
For related workflows, see the website translation and localization checklist, the multilingual content QA checklist, and the translation glossary and style guide template.