Locale-specific number readouts need both the correct value and an appropriate spoken form. A date, decimal, identifier, and quantity may share similar digits while requiring very different readings. Preserve an unambiguous source value, decide the intended meaning, and have a qualified reviewer approve how that meaning should sound in the target locale.
Classify every numeric string
Create a list of dates, times, measurements, currencies, percentages, version numbers, phone numbers, and identifiers. Do not apply one number-reading rule to all of them. An account code is not a quantity, and a product version is not a decimal measurement.
Record the source meaning in words or structured fields. For an ambiguous date, identify the actual month, day, and year before translation. W3C's date-format discussion explains why numeric dates can be interpreted differently across locales.
Keep illustrative data clearly marked as fictional where appropriate. Do not introduce a currency conversion or unit conversion just to make an example feel local unless the content owner authorizes that change.
For each entry, record where it appears and whether it must match an on-screen label. This reveals cases where a correct spoken adaptation would otherwise disagree with the visual.
Treat ranges and negative values as explicit review items. A dash in a written script might indicate a minus sign, a range, or a separator in an identifier. State the intended meaning in the source record so the target reviewer can select an accurate spoken form.
Approve the target convention
Ask the locale reviewer how the audience would naturally hear the number in this context. A formal announcement, software tutorial, and reference table may use different phrasing even for the same underlying value.
Decide how to state dates, time zones, decimal separators, and units. If a time applies across regions, the intended zone needs to be explicit in the content rather than left to the voice producer's guess.
W3C's locale-based forms examples show that written numeric conventions vary. In audio production, treat the written form and the spoken form as separate decisions connected to the same value.
Keep approved examples in the project glossary. If a reviewer changes a convention, identify all affected occurrences, not only the sentence that exposed the problem. Consistency should follow the intended meaning, not blind search-and-replace.
Write production text that removes ambiguity
Where necessary, spell the intended reading out in the target language in a production field. Keep the standard numeric notation in the public transcript or display text when that is the approved written form.
Read identifiers in the way the audience needs to use them. A confirmation code may require individual characters; a year usually does not. Test a sample with similar-looking or similar-sounding characters if accurate copying is part of the task.
For mixed-direction scripts, use the right-to-left review process to check how digits and labels survive copying between tools. Visual order problems can hide an incorrect production string.
Coordinate on-screen controls through the localized interface narration guide. If a tutorial says a value that the interface displays differently, explain the relationship or correct the mismatch before recording.
Verify the audible value, then the scene
Generate a short sample containing the difficult number in its full sentence. Ask the reviewer to write down the value they hear without looking at the script. Compare that result with the intended source value.
Listen for omitted decimals, confusing unit names, merged identifier characters, and stress that makes a range sound like one number. A fluent sentence can still communicate the wrong quantity.
Include the revised line in bilingual script QA if its wording changed during pronunciation testing. Then verify the final audio beside the visual and subtitle version that will ship.
Test the approved readout in the voice studio and retain the downloaded sample with the numeric glossary. The review is finished when the spoken value, source meaning, and target display all agree for the intended audience.
