Practical framework / 5 MIN READ
Localize dates, quantities and units correctly
Preserve the underlying value while adapting its presentation, and separate formatting from any approved conversion.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
A localized number or date must communicate the same fact to its intended reader. Changing separators, units or time conventions can accidentally alter meaning even when the surrounding sentence is translated well.
What you will leave with: Leave with a value-and-format register and tests for ambiguous or consequential numeric content.
Use this when
- A multilingual page contains dates, dimensions or quantities.
- A regional version changes units or currency presentation.
- Readers interpret the same numeric string in different ways.
This is editorial quality control, not authority to change prices, contractual deadlines, regulated quantities or commercial commitments.
Separate stored meaning from display form
Identify the underlying value and what it represents before editing its appearance. A calendar date, a moment in time and a duration require different handling. A product identifier that contains digits is not a quantity to reformat. Record the source value, unit, timezone where relevant and approved regional display. Avoid copying a visually formatted string back into a system that expects structured data. When the source itself is ambiguous, ask the owner to resolve it instead of choosing whichever interpretation suits the target layout or seems familiar to the translator.
Choose the intended locale deliberately
Unicode CLDR documents locale-sensitive number symbols and regional formatting choices. Use a suitable supported formatter and a clearly identified locale rather than replacing commas and periods manually. Language alone may not determine the reader's expected regional conventions. Ask the local reviewer which presentation is appropriate for the actual audience, especially when a page serves an international group. Keep the displayed unit or currency unambiguous. A currency symbol or abbreviated date can be familiar to one audience and unclear to another, so assess the context in which the value will be read.
Treat conversion as a separate decision
Changing from one measurement unit to another requires an approved conversion and rounding rule, not just a translated label. Decide whether the original value should remain alongside the converted value and which one governs any consequential specification. Preserve meaningful precision without creating false accuracy. Currency conversion is especially distinct from localization because it can imply a new price or commitment. Do not invent an exchange-rate policy or convert a contractual amount editorially. Have the responsible specialist verify regulated, safety-related or contractual quantities before publication, including any tolerance or qualification attached to them.
Test boundary cases and complete messages
Review examples around date boundaries, zero and negative values, large quantities and ranges. Check the complete sentence after formatting so grammar, spacing and units remain understandable. For time-specific events, verify the relevant timezone and the actual event date rather than relying on a generic offset remembered from another season. Compare the rendered value with the authoritative source and inspect exports or copied text where readers may reuse it. Keep the chosen rules with the content model so future editors do not introduce competing formats. Record unresolved ambiguity as a blocker, not a cosmetic exception.
Make the reasoning concrete.
A hypothetical training provider localizes an event page containing a numeric date, start time and a downloadable equipment-size guide.
Surface substitution
Opening: The editor translates the words and swaps separators while leaving the date interpretation and timezone unclear.
Hypothesis: The page looks localized.
Risk: A reader may arrive on the wrong day or treat a converted dimension as the governing specification.
Value-led review
Opening: The team confirms the actual date and timezone, formats them for the audience and separately verifies any unit conversion.
Hypothesis: The page communicates the same intended facts.
Risk: The local reviewer cannot authorize a changed contractual deadline or product tolerance.
The editor checks every consequential value against its source and records formatting and conversion decisions separately.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Meaning
What exact value, unit and temporal meaning are authoritative?
Locale
Which audience-specific formatting convention applies?
Conversion
Is any unit or currency change authorized and checked?
Precision
What rounding and governing-value rule should be preserved?
Tests
Which ambiguous dates, boundaries or ranges need review?
Watch for the wrong conclusion.
- Treating a numeric identifier as a quantity.
- Replacing punctuation without knowing the locale.
- Changing a unit label without converting and checking the value.
- Presenting an editorial conversion as a new commercial commitment.
Your next action
Audit one localized page and record the source value, display rule and conversion authority for every consequential number or date.
Sources & scope
The framework, examples and suggested checks are original editorial synthesis. Hypothetical examples are not measured results. Source checking is not an independent audit or a guarantee of business outcomes. No named human reviewer is claimed.
- Unicode CLDR: Number symbols →Primary publisher guidance · Supports: Supports locale-sensitive numeric symbols and regional formatting choices. It does not authorize currency conversion, unit changes, rounding policy or a changed commercial commitment.