To translate ISO 80000-1:2022 quantity and unit terminology accurately, you must distinguish the physical quantity, its numerical value, its unit, its symbol and the context in which a number becomes meaningful. People searching for scientific measurement translation, engineering unit symbols, decimal comma conversion, bilingual laboratory reports and international specification wording usually need more than a dictionary. They need the translated record to describe exactly the same measurement.
ISO 80000-1:2022 is the general part of the quantities-and-units series. Its publicly stated scope covers quantities, systems of quantities, units, quantity and unit symbols, coherent unit systems and general concepts relevant to the International System of Quantities. It does not independently define every specialist measurement procedure, validate an instrument or authorize a conversion that changes a product requirement.
Accurate technical translation starts by asking: What was measured? In what unit? Under which conditions? With what uncertainty and acceptance rule? A misplaced prefix, an unreviewed unit conversion or a decimal separator interpreted under the wrong locale can change a harmless number into a dangerous instruction. This guide presents a structured method with original examples from engineering, science, laboratories, manufacturing, energy and international documentation.
Quick answer: what should a translator preserve?
Keep the quantity kind, numeric value, unit, unit symbol, scale factor, precision, uncertainty and acceptance context together. Translate descriptive labels into the target language, preserve technical symbols according to the applicable notation convention, and validate every numerical transformation independently. A translated label is not evidence that the underlying measurement was made or that equipment passed a test.
- Translate ‘mass’, ‘length’, ‘area’, ‘volume’, ‘power’ and ‘energy’ according to their measured meanings, not a generic word for size.
- Do not confuse a quantity symbol with a unit symbol; a letter can mean different things in different technical contexts.
- Prefixes change magnitude: µ, m, k and M are not ornamental characters.
- Convert values only with an approved policy, and calculate significant digits and uncertainty rather than silently rounding.
- Check decimal comma, decimal point, thousands grouping and scientific notation in every locale.
- ‘Measured’, ‘estimated’, ‘specified’, ‘maximum’ and ‘passed’ communicate different evidence and authority.
Contents
- What this standard does and does not do
- The meaning decisions that matter
- Worked translation cases
- Practical review workflow
- Four-week practice plan
- Frequently asked questions
- Sources and further reading
What ISO 80000-1:2022 covers, and where translation decisions begin
The ISO catalogue describes ISO 80000-1:2022 as general information and definitions about quantities, units, symbols and coherent unit systems, especially the International System of Quantities. It is an introduction to other parts of the ISO/IEC 80000 series. This article is an independent translation tutorial informed by that public description, not a reproduction of the text of the standard. For specialist units and symbols, users need the appropriate discipline-specific source and any governing contract.
Imagine a product sheet reading ‘mass 2.5 kg, length 120 mm, power 800 W, daily energy 4.8 kWh’. Translating all four as ‘size’ would lose what each number measures. The customer may need mass to plan lifting, length to assess fit, power to select an electrical connection and energy to estimate consumption over time. Keeping unit tokens but mistranslating the measured quantity is still a substantive error.
Numbers can also be transformed by layout. A decimal comma used in one language must not be mistaken for a thousands separator in another; ‘1,250’ might mean one and one-quarter or one thousand two hundred fifty depending on declared convention. A reliable multilingual system stores numeric values in an unambiguous structured representation and formats them for viewers, rather than asking a translator to guess from a screenshot.
Quantity symbols, unit symbols, variable names and ordinary abbreviations should be inventoried separately. A lowercase m may denote metre as a unit, but in equations an italic m may denote a mass variable. A case change in prefix symbols can move a number by orders of magnitude. A reviewer must see both the expression and its surrounding sentence before deciding whether a character belongs to language or measurement notation.
Another crucial distinction is between measured results and specifications. An instrument reading of 24.9 °C, a permitted maximum of 25 °C, a nominal operating condition of 25 °C and a calibration reference at 25 °C are not equivalent. Translation should preserve the claim’s function and the organization that approved it. Any safety, compliance or acceptance conclusion must be grounded in the source evidence, not reverse-engineered from a single translated number.
The meaning decisions that matter
1. Quantity is not merely a number
A numerical value becomes useful when paired with what it measures. Three ‘meters’ of cable, three square metres of floor and three cubic metres of water use different dimensions even if the number is the same. The translated field name must lead the reader to the correct operational decision. On international forms, treat the quantity kind as an independent database concept so changes in language cannot turn mass into weight, energy into power or concentration into count.
2. Unit identity and representation
The unit’s conventional symbol may remain unchanged across languages even as the unit’s full name changes grammatically. Do not translate technical symbol letters into visually similar characters or invent local alternatives. Preserve the difference between a standard symbol, a variable name and a product code. For critical values, compare the source and target character by character and test that downstream software interprets them identically.
3. Scale factors and prefixes
Prefixes are mathematical multipliers. A microgram, milligram, gram and kilogram cannot be substituted casually; the wrong prefix changes magnitude by hundreds or thousands of times. Case matters: the symbol for mega is not the same as that for milli. If a PDF copy or OCR process loses the micro sign or turns a superscript into an ordinary digit, the translator must flag the source corruption before rewriting the value.
4. Engineering area and volume
Length, area and volume are different dimensions, often distinguished by superscripts. A drawing may use mm for length, mm² for area and mm³ for volume. When translating labels on an engineering drawing, test whether fonts preserve superscripts and whether numbers remain attached to the correct axis and dimension. An understated exponent can change material estimates and specifications beyond ordinary proofreading errors.
5. Decimal grouping and locale
Some documents group thousands with a space or punctuation and use a comma for decimals. The target style can change how numbers look, but the underlying numerical value must remain the same. Avoid copying a formatted string from an unknown locale into a spreadsheet that interprets separators differently. Keep a canonical number and output rules for each locale, and inspect samples such as 1.234, 1,234, and 0,001.
6. Rounding, significant figures and uncertainty
A source value of 0.00480 has a precision story that ‘0.005’ may not communicate. A translator should not round to make text shorter. If a unit conversion is required, document the factor, rounding rule and treatment of measurement uncertainty. The reviewer should be able to reconstruct the source within the approved tolerance. Where contractual precision is unclear, flag the issue rather than inventing a significant-digit policy.
7. Specified maximum versus observed result
Terms like maximum permitted, target value, measured average, estimated consumption and declared nominal rating must survive translation. A displayed value of 20 may be a limit, test result or design target. If the source states ‘limit 20 mg/L’, translating it as ‘measured 20 mg/L’ creates false evidence. Always pair a translated number with its evidence status.
8. Absolute temperature and temperature difference
Temperature units require special care because absolute readings and differences are mathematically different objects. A difference of one degree Celsius corresponds to one kelvin in size, but an absolute Celsius reading cannot be changed to kelvins by simply replacing its unit label. Translators must ask whether the expression is an observed temperature, change, range or tolerance, then refer any conversions to a documented calculation.
9. Power, energy and time
A watt is a rate of energy transfer; a watt-hour or kilowatt-hour is a quantity of energy. A machine’s 2 kW power rating does not automatically mean it consumes 2 kWh per day. Translators of electricity bills, equipment labels and sustainability reports must retain the measured concept, observation interval and any operating assumptions. This distinction is operationally important even when the symbols look closely related.
10. Reference conditions and methods
A quantity may depend on reference temperature, pressure, instrument calibration, sampling procedure or data processing. Translating the unit correctly does not validate the comparison if those conditions are dropped. In scientific reports, keep notes such as ‘dry basis’, ‘standard conditions’, ‘at rest’, ‘estimated’ and ‘instrument uncertainty’ with the relevant value. Let the subject expert decide whether transformed numbers can be compared.
11. Tables, axes and diagrams
Tables and charts compress meaning into headings, footnotes, legends, units and visual placement. The target language may use longer labels, but it cannot move a unit from one column to another or detach an exponent from the measured quantity. Review images after export, particularly small axis labels, reversed text direction, decimal separators and minus signs that can resemble dashes.
12. Bilingual numerical traceability
Create a two-column audit table linking source line, source value, source unit, target rendering, transformation, reviewer and approval. Translators should not certify an instrument merely because the textual description is well translated. A numerical reviewer can confirm scale and symbols; a subject owner can confirm whether claims such as ‘safe’, ‘within specification’ or ‘passed’ are supported by actual evidence.
Worked translation cases: source, misleading shortcut, safer rendering and verification
The following are invented teaching examples, not quotations from the ISO document or certified translations. Their purpose is to show how a translator, editor or subject specialist can keep quantities, obligations, uncertainty, exclusions, audiences and evidence intact. The safest final wording depends on the real source file, the target language, the governing jurisdiction and the person responsible for approving the message.
Case 1: Milligram versus microgram
Source situation: A laboratory result states a concentration of 7 µg/L. A rushed rendering might say: “The result is 7 mg/L.”. A more faithful English explanatory rendering would be: “Measured concentration: 7 micrograms per litre, with the original symbol µg/L retained.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: The milli-to-micro difference is a factor of one thousand. The source’s magnitude cannot be guessed from the surrounding clinical or environmental context. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Confirm the unit against the originating laboratory data and check that the exported font preserves µ. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 2: Kilogram versus gram
Source situation: A shipping specification says net mass 0.75 kg. A rushed rendering might say: “Net mass 0.75 grams.”. A more faithful English explanatory rendering would be: “Net mass 0.75 kilograms, equivalent to 750 grams only if conversion is intended.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: The same numerals with a different mass unit produce an entirely different handling estimate. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Match package mass, unit conversion and final displayed precision. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 3: Area superscript
Source situation: A construction schedule states usable floor area 82 m². A rushed rendering might say: “Usable floor length 82 m.”. A more faithful English explanatory rendering would be: “Usable floor area 82 square metres.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: The exponent encodes dimension, not decoration. Removing it changes the meaning of both the value and the planning decision. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Check the original drawing legend and verify superscript rendering after publication. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 4: Volume superscript
Source situation: A tank record lists internal volume 2.4 m³. A rushed rendering might say: “Tank length is 2.4 metres.”. A more faithful English explanatory rendering would be: “Tank internal volume is 2.4 cubic metres.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: Volume requires three-dimensional units, and a planning decision based on length would be nonsensical. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Inspect the source unit glyph and the technical calculation note. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 5: Metre versus minute
Source situation: A maintenance note uses m for distance and min for elapsed time. A rushed rendering might say: “Both entries mean minutes.”. A more faithful English explanatory rendering would be: “Distance is recorded in metres (m); duration is recorded in minutes (min).”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: A translated abbreviation needs context; one-letter and multi-letter forms are not interchangeable. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: List all column headings and verify the meaning with the asset owner. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 6: Decimal comma
Source situation: A supplier sheet from a decimal-comma locale shows 1,25 kg. A rushed rendering might say: “The package weighs 1250 kg.”. A more faithful English explanatory rendering would be: “The package mass is one point two five kilograms.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: A parser trained on a different locale may treat the punctuation as grouping and inflate the mass. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Read the original locale settings and compare with a secondary numerical source. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 7: Thousands grouping
Source situation: A report displays 1 250 mL. A rushed rendering might say: “Volume 1.250 mL.”. A more faithful English explanatory rendering would be: “Volume 1,250 millilitres, using an unambiguous grouping style for the audience.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: A narrow or nonbreaking space can group thousands; replacing it with a decimal separator changes the quantity. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Review numeric export values separately from visual punctuation. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 8: Scientific notation
Source situation: A sensor result is 4.8 × 10^-3 A. A rushed rendering might say: “Current is 4.8 A.”. A more faithful English explanatory rendering would be: “Current is 0.0048 amperes, equivalent to 4.8 × 10^-3 A.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: An omitted exponent is a three-order-of-magnitude error; the minus sign matters. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Check exponent formatting and compare converted values using independent arithmetic. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 9: Mega versus milli
Source situation: A component sheet distinguishes 3 MW and 3 mW. A rushed rendering might say: “Both refer to three watts.”. A more faithful English explanatory rendering would be: “One rating is three megawatts; the other is three milliwatts.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: Letter case represents scale; converting typography to all caps can destroy the measurement. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Audit the exact symbols rather than relying on spell-check. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 10: Power versus energy
Source situation: An appliance has a rated power of 1.5 kW. A rushed rendering might say: “The appliance uses 1.5 kWh every day.”. A more faithful English explanatory rendering would be: “Rated power: 1.5 kilowatts; energy consumption depends on operating time and use.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: Power describes a rate, while energy accumulates over time. A daily energy claim needs actual run time. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Retain the word ‘rated’ and ask for energy-use evidence if a consumption figure is required. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 11: Energy billing period
Source situation: An invoice states consumption 320 kWh for October. A rushed rendering might say: “The meter power is 320 kW.”. A more faithful English explanatory rendering would be: “Energy consumed during October: 320 kilowatt-hours.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: The time period is part of a billed energy quantity, not an instantaneous rating. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Match the billing start and end dates and the meter reading units. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 12: Celsius temperature
Source situation: A storage instruction gives 20 °C as an absolute temperature. A rushed rendering might say: “Store at 20 kelvins.”. A more faithful English explanatory rendering would be: “Storage temperature: 20 degrees Celsius.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: Changing the unit name without mathematical conversion could turn an ordinary environment into an impossible instruction. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Check whether the source is an absolute temperature, difference, limit or tolerance. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 13: Temperature difference
Source situation: A process note says the temperature rose by 5 °C. A rushed rendering might say: “Final temperature is 5 °C.”. A more faithful English explanatory rendering would be: “Temperature increase: 5 degrees Celsius; final temperature not supplied.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: A change is not an absolute final reading. Translating ‘rise’ as ‘result’ invents a datum. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Compare start and end readings if the final temperature must be reported. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 14: Tolerance sign
Source situation: A drawing states 50.0 ± 0.2 mm. A rushed rendering might say: “Dimension must be exactly 50.0 mm.”. A more faithful English explanatory rendering would be: “Specified dimension: 50.0 millimetres with a tolerance of plus or minus 0.2 millimetres.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: Dropping the tolerance turns an acceptable manufacturing range into a single value. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Check the plus-minus glyph and acceptance criteria with the drawing revision. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 15: Maximum versus reading
Source situation: A water test sheet has ‘limit 10 mg/L’, but no sample measurement. A rushed rendering might say: “Sample contains 10 mg/L.”. A more faithful English explanatory rendering would be: “Specified limit: 10 milligrams per litre; sample result not shown.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: A limit is not evidence that the sample has been tested or passed. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Locate the measurement row and obtain an authorized conclusion separately. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 16: Measured versus estimated
Source situation: An energy audit lists an estimated 18,000 kWh per year. A rushed rendering might say: “Exact annual consumption is 18,000 kWh.”. A more faithful English explanatory rendering would be: “Estimated annual energy use: 18,000 kilowatt-hours.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: The qualifier signals uncertainty or a model, which matters to procurement decisions. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Look for the calculation assumptions and avoid removing the estimate label. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 17: Mass versus weight
Source situation: A product note says mass 18 kg. A rushed rendering might say: “Weight is exactly 18 newtons.”. A more faithful English explanatory rendering would be: “Mass is 18 kilograms.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: Mass and force are different quantities; the everyday word ‘weight’ can mislead technical audiences. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Check whether a force measurement exists before replacing the quantity name. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 18: Speed versus distance
Source situation: A test records 12 m/s. A rushed rendering might say: “The distance travelled was 12 metres.”. A more faithful English explanatory rendering would be: “Measured speed: 12 metres per second.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: A quotient involving seconds is a rate, not a distance. Field labels must preserve dimensions. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Verify the time denominator and sensor output heading. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 19: Count per volume
Source situation: A filter report lists 900 particles/m³. A rushed rendering might say: “The filter contains 900 particles total.”. A more faithful English explanatory rendering would be: “Reported number concentration: 900 particles per cubic metre.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: A concentration has a denominator; losing it destroys comparability across sampling volumes. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Check the reference volume, detection threshold and sample method notes. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 20: Percent versus percentage points
Source situation: A project reports a defect rate moving from 2% to 3%. A rushed rendering might say: “The rate increased by one percent.”. A more faithful English explanatory rendering would be: “The defect rate increased by one percentage point, from 2% to 3%.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: A percentage-point change differs from a relative percent increase. Translation must reflect the source calculation. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Confirm whether the analyst reports absolute or relative change and retain the base. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 21: Specific rate
Source situation: A medicine label contains mg/kg, but no actual patient calculation. A rushed rendering might say: “Take this many milligrams regardless of body mass.”. A more faithful English explanatory rendering would be: “The amount is stated per kilogram and requires an authorized individual calculation.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: A per-body-mass expression is not a ready-to-administer dose. Translators must not turn a ratio into patient advice. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Escalate to a licensed clinical reviewer and retain the full denominator. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 22: Torque notation
Source situation: A mechanical worksheet records torque 12 N·m. A rushed rendering might say: “Force equals 12 newtons.”. A more faithful English explanatory rendering would be: “Torque: 12 newton metres.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: The product of force and distance expresses torque in this context; a unit alone may be ambiguous without a quantity label. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Read the drawing callout and confirm the equipment operation. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 23: Pressure sign
Source situation: A vessel report states gauge pressure -2 kPa. A rushed rendering might say: “The pressure is positive two kilopascals.”. A more faithful English explanatory rendering would be: “Reported gauge pressure: negative two kilopascals.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: Minus signs may be lost in typographic conversions, reversing an operating condition. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Compare source/target characters with a numeric QA script. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 24: Reference conditions
Source situation: A gas flow measurement is noted ‘at specified reference conditions’. A rushed rendering might say: “The same value applies at all temperatures and pressures.”. A more faithful English explanatory rendering would be: “Gas flow as reported at the stated reference conditions.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: A measured volume or rate may not be comparable without condition metadata. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Keep the reference note adjacent to the reported value. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 25: Graph axis
Source situation: A plot labels y-axis ‘mass concentration (mg/m³)’. A rushed rendering might say: “The graph shows total mass in milligrams.”. A more faithful English explanatory rendering would be: “Vertical axis: mass concentration in milligrams per cubic metre.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: A chart reader may act on the axis label without examining the prose. The denominator and quantity name both matter. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Review the final rasterized and mobile chart, not only the editable file. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 26: Measurement uncertainty
Source situation: A certificate reports 25.0 ± 0.5 °C. A rushed rendering might say: “Temperature confirmed as exactly 25 °C.”. A more faithful English explanatory rendering would be: “Reported temperature: 25.0 °C with stated uncertainty of ±0.5 °C.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: An uncertainty statement cannot be treated as decorative detail when comparing results or acceptance limits. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Preserve the uncertainty’s form and check whether it is standard or expanded uncertainty in the source. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 27: Nominal capacity
Source situation: A product advertises nominal volume 500 mL. A rushed rendering might say: “Every container was measured to hold exactly 500 mL.”. A more faithful English explanatory rendering would be: “Declared nominal volume: 500 millilitres.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: A nominal label is a specification category, not a certificate for each individual item. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Check the regulatory label wording and underlying tolerance requirements. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
Case 28: Significant digits after conversion
Source situation: A length is 2.50 m and the target display uses centimetres. A rushed rendering might say: “Length is exactly 250.000000 cm.”. A more faithful English explanatory rendering would be: “Length is 250 cm, with the original 2.50 m retained when precision matters.”. These are teaching paraphrases, not mandatory word-for-word translations; an actual target-language version must be natural without quietly changing the facts.
Why the distinction matters: Conversion can create trailing zeros that imply unsupported resolution. A transformation must respect the measurement’s reporting conventions. The translator should preserve the decision being communicated, not replace a complicated original with an attractive claim. Reading the message without the source should not lead a customer, colleague, technician or auditor to infer a permission, date, quantity, performance level or legal conclusion that nobody authorized.
Verification before release: Document the conversion factor and reviewed rounding policy. Record who owns the source evidence, which wording was approved and which facts remain unknown. If the source is internally contradictory, mark a query for the author rather than choosing whichever version looks easiest to translate. A second reviewer can then reproduce the decision without guessing what the first translator intended.
A practical, auditable translation workflow
Step 1: Name the measured quantity
Identify whether each number is a mass, length, area, concentration, force, energy or another quantity. A common failure is using a generic translation for every measurement heading. This step matters because multilingual communication is not only about lexical equivalents; it determines how the recipient interprets an action, a number or a restriction.
Create a bilingual field glossary with definitions and sample values. Keep the smallest useful proof with the work: an approved source sentence, a screenshot of a field, the relevant owner’s answer, or a test showing that the target display still means the same thing. Do not call an unverified translation compliant merely because it looks professional.
Step 2: Preserve original numeric evidence
Save the source number and its units in a non-destructive working table. A common failure is editing the only copy during localization. This step matters because multilingual communication is not only about lexical equivalents; it determines how the recipient interprets an action, a number or a restriction.
Keep an immutable source export and version identifier. Keep the smallest useful proof with the work: an approved source sentence, a screenshot of a field, the relevant owner’s answer, or a test showing that the target display still means the same thing. Do not call an unverified translation compliant merely because it looks professional.
Step 3: Audit unit symbols
Check case, prefixes, exponents, signs, multiplication dots and slash denominators. A common failure is letting font substitutions flatten mathematically significant notation. This step matters because multilingual communication is not only about lexical equivalents; it determines how the recipient interprets an action, a number or a restriction.
Use a character-level comparison for high-risk unit strings. Keep the smallest useful proof with the work: an approved source sentence, a screenshot of a field, the relevant owner’s answer, or a test showing that the target display still means the same thing. Do not call an unverified translation compliant merely because it looks professional.
Step 4: Establish locale rules
Document decimal separators, digit grouping, nonbreaking spaces and sign display for target locales. A common failure is copying a formatted number into a parser with different assumptions. This step matters because multilingual communication is not only about lexical equivalents; it determines how the recipient interprets an action, a number or a restriction.
Test ambiguous samples with the target locale formatter. Keep the smallest useful proof with the work: an approved source sentence, a screenshot of a field, the relevant owner’s answer, or a test showing that the target display still means the same thing. Do not call an unverified translation compliant merely because it looks professional.
Step 5: Separate translation from conversion
Translate labels first, and calculate any approved unit changes through a checked formula. A common failure is converting a number by replacing only the unit abbreviation. This step matters because multilingual communication is not only about lexical equivalents; it determines how the recipient interprets an action, a number or a restriction.
Record factors, calculation method and owner approval. Keep the smallest useful proof with the work: an approved source sentence, a screenshot of a field, the relevant owner’s answer, or a test showing that the target display still means the same thing. Do not call an unverified translation compliant merely because it looks professional.
Step 6: Keep qualifiers and conditions
Preserve measured, nominal, estimated, average, maximum, minimum and reference-condition phrases. A common failure is making an observation sound like a guarantee. This step matters because multilingual communication is not only about lexical equivalents; it determines how the recipient interprets an action, a number or a restriction.
Attach the qualification to the same table cell or sentence. Keep the smallest useful proof with the work: an approved source sentence, a screenshot of a field, the relevant owner’s answer, or a test showing that the target display still means the same thing. Do not call an unverified translation compliant merely because it looks professional.
Step 7: Review precision and uncertainty
Confirm rounding, significant digits, confidence language and uncertainty notation with a competent reviewer. A common failure is adding precision for visual consistency. This step matters because multilingual communication is not only about lexical equivalents; it determines how the recipient interprets an action, a number or a restriction.
Use a before-and-after numerical QA table. Keep the smallest useful proof with the work: an approved source sentence, a screenshot of a field, the relevant owner’s answer, or a test showing that the target display still means the same thing. Do not call an unverified translation compliant merely because it looks professional.
Step 8: Inspect exported diagrams
Proofread drawings, graph axes, figure legends and mobile labels after layout. A common failure is assuming editable source text matches rendered artwork. This step matters because multilingual communication is not only about lexical equivalents; it determines how the recipient interprets an action, a number or a restriction.
Compare screenshots with the original technical figure. Keep the smallest useful proof with the work: an approved source sentence, a screenshot of a field, the relevant owner’s answer, or a test showing that the target display still means the same thing. Do not call an unverified translation compliant merely because it looks professional.
Step 9: Challenge acceptance claims
Ask whether any target statement that says safe, passed or within specification comes from approved evidence. A common failure is deriving certification solely from a measured number. This step matters because multilingual communication is not only about lexical equivalents; it determines how the recipient interprets an action, a number or a restriction.
Require a signed source statement for each conclusion. Keep the smallest useful proof with the work: an approved source sentence, a screenshot of a field, the relevant owner’s answer, or a test showing that the target display still means the same thing. Do not call an unverified translation compliant merely because it looks professional.
Step 10: Release an auditable terminology sheet
Preserve unit decisions, accepted equivalents, rejected wording and review owner for future updates. A common failure is rebuilding ambiguous terms from memory every release. This step matters because multilingual communication is not only about lexical equivalents; it determines how the recipient interprets an action, a number or a restriction.
Store the term list with the product or report revision. Keep the smallest useful proof with the work: an approved source sentence, a screenshot of a field, the relevant owner’s answer, or a test showing that the target display still means the same thing. Do not call an unverified translation compliant merely because it looks professional.
Four-week practice plan for translators, editors and subject experts
Week 1: Build a quantities glossary
Collect a set of thirty measurement labels across laboratory, manufacturing, construction and energy records. For each entry, name the quantity kind, unit, symbol, source condition and typical mistranslation. Confirm that the meaning survives in two languages.
Ask a technical reviewer to identify ten random quantities from your labels alone. Resolve confusing terms before translating full paragraphs.
Week 2: Test numeric conversions
Take twenty source values containing prefixes, exponents, decimal separators, signed numbers and tolerances. Translate the labels without changing values, then separately perform only those conversions the brief explicitly approves.
Compare calculations with a second method and document rounding. Include an example whose visually similar symbols represent very different scales.
Week 3: Practise report evidence
Translate one specification, one measured-results table, one graph caption and one customer-facing summary. Annotate source status, measurement conditions and any uncertainty statement.
Have the subject owner mark each outcome claim as supported, unsupported or unclear. Rewrite unsupported claims without making the text less informative.
Week 4: Perform final layout QA
Create a bilingual sample document with figures, tables, units and footnotes. Review both desktop and mobile outputs, then use an independent reader to reconstruct quantities from the translated version.
Archive the source data, transformations, editor answers and final proofs. Reuse the approved terminology as a specialist reference rather than creating a competing general translation hub.
Frequently asked questions
Does ISO 80000-1:2022 tell me how to translate every scientific term?
No. It supplies general quantities-and-units foundations. Specialized disciplines need their own accepted terminology, measurement procedures and applicable standards. This guide focuses on preserving quantitative meaning across languages.
Should I translate unit symbols?
Ordinarily, established symbols are preserved while the surrounding words change, subject to the relevant technical convention. A symbol is not simply an abbreviation of an English word; changing case or script can change its meaning.
Can I replace a decimal comma with a decimal point?
Only when the numeric value has been parsed unambiguously and the target display rules are specified. Never assume what a separator means from appearance alone. Use structured values and locale-aware formatting.
Is a kilowatt the same as a kilowatt-hour?
No. Kilowatt is a unit of power; kilowatt-hour is a unit of energy. Conflating them can corrupt equipment ratings, electricity bills and energy-reporting claims.
Why does µ versus m matter?
Those characters can signal very different scale factors. A mistaken micro-to-milli replacement may change magnitude by a factor of one thousand. Compare exact characters with the source rather than relying on visual similarity.
Should a translator calculate unit conversions?
Only when the scope authorizes them and a technical reviewer can check the calculations and rounding. Translation and conversion are distinct tasks that should be traceable.
What if a measured value exceeds a specification?
Preserve the recorded result and the approved acceptance statement. Do not edit the value, hide the failure or independently certify compliance. Escalate contradictions to the responsible laboratory or engineering owner.
Does a well-translated report mean its measurements are reliable?
No. Linguistic quality does not prove calibration, sample quality, method suitability or compliance. The article separates reading and translation of evidence from validation of the evidence itself.
How do I check bilingual graphs efficiently?
Read each axis name, unit, scale, legend, exponent, footnote and qualifier. Then compare the final rendered graph with the source. Many errors arise in charts and screenshots rather than ordinary prose.
Sources, scope note and connected learning
Primary catalogue source: ISO 80000-1:2022, quantities and units, Part 1: general definitions and principles. The ISO catalogue describes the standard’s public scope; this article supplies independent language-learning examples and does not reproduce the standard, grant certification or replace a licensed copy and professional review.
Official ISO catalogue and scope | Master Art of Translation — established world translation architecture | Vocabulary Learning Hub | How English Works: Translation and Meaning Across Languages
This specialist guide is a practical companion to the existing translation architecture, not a replacement hub. Readers seeking wider language-learning methods should use those canonical resources. Before adopting any illustrative phrasing in a regulated document, obtain the exact source text and confirm current local requirements with the responsible subject expert.