How do you translate ISO 286 H7/g6 machining fits and tolerances without changing what the original document actually requires? The practical answer begins with a distinction that fluent prose alone cannot supply: the exact technical identifier must remain tied to its measurement or decision field. When a standard, product mark, inspection sheet or certificate crosses languages, the goal is not to make its figures look familiar. It is to help a reader in another language make the same defensible interpretation of the evidence. An ISO 286 fit is not merely a descriptive adjective such as ‘close’ or ‘loose’. It is an encoded pair of dimensional zones that can be checked by calculation and inspection.
Readers searching for translate ISO 286 H7/g6 machining fits and tolerances are often handling a real quotation, engineering document, quality-control record, specification or supplier dispute. They want to know what each symbol means, which numbers must survive translation, what can safely be explained in ordinary language and which judgments require technical authority. This guide addresses that precise search intent. It avoids pretending that a word-for-word substitution, a machine-translated table or a polished marketing summary can replace the controlling technical evidence.
In this worked guide, we preserve the source notation, examine realistic reporting mistakes, build a review process and show how to explain the same facts to purchasers, students, technicians and decision-makers. ISO 286-2:2010 remains current and was confirmed by ISO in 2026. A translated explanation can be more accessible than the source while remaining narrower than a professional certification. The examples are educational and illustrative: they do not replace the issued standard, the original contract, a qualified inspection decision or local regulatory requirements.
The fast answer: identify the code, the object, the conditions and the decision
Start with the controlled document rather than a search-engine snippet. Find the identifier, what physical object or decision it belongs to, the exact numbers and units, any test or measurement conditions, and the status of the observation. Then translate the explanatory prose while preserving critical symbols. The reader should be able to move from the target-language sentence back to the original record without guessing which field was paraphrased. That traceability is the central skill in specialised translation.
The fastest wrong approach is to replace an unfamiliar code with a confident adjective. ‘Strong’, ‘high quality’, ‘safe’, ‘acceptable’, ‘precision’ and ‘compliant’ sound reassuring, but none automatically reproduces a documented test method or dimensional limit. If the original gives a categorical class, translate it as a categorical class. If the original provides a measured value, preserve its unit, qualifier, sampling context and uncertainty. If the original records a decision, separate that decision from the measurements on which it relied.
A practical source-to-target workflow
- Make a read-only transcription of all codes, symbols, numbers, edition years, dates and revision identifiers before translating explanatory sentences.
- Identify each property’s name, the object tested or specified, the unit or categorical scale, and the actual reporting conditions.
- Read the surrounding table headers and footnotes; the same numeral can mean a different thing in another column.
- Build a controlled glossary that distinguishes terms which sound alike but produce different practical decisions.
- Use examples as teaching aids, never as replacements for the source document’s actual data.
- Keep a bilingual audit trail showing the source phrase, the target rendering, reviewer and unresolved technical query.
- Have a competent subject specialist review any translation that will control manufacture, purchase, safety or regulatory acceptance.
Why make this checklist before translating? Because the English sentence is only one layer of a technical record. A test result also carries provenance, procedure, edition and authority. In ordinary reading, the audience can infer missing context from conversation. In international procurement or laboratory reporting, the absence of a small qualifier can redirect a purchase, reject acceptable goods or release inappropriate goods. The workflow above protects the underlying knowledge while allowing the final explanation to feel natural rather than robotic.
Field-by-field explanatory guide
1. The complete H7/g6 expression
Start with what the entry actually describes. H7 designates the hole’s tolerance class and g6 the shaft’s. It is a pair, not an optional decorative suffix. This is a useful place to distinguish a controlled label from a general-language impression. Two expressions may be close enough for casual conversation but not close enough for procurement or technical acceptance. A good translation names the property before describing its implications. It also keeps the reader aware of whether the source is specifying a required value, recording an observed result or offering an explanatory note. Those are different speech acts with different consequences. If the source is silent about a condition, the translation must remain silent about that condition too.
Read a realistic source situation: Source ‘Ø25 H7/g6’ describes the intended relationship of a 25 mm hole and mating shaft, not a single component’s dimension. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: Rendering both as ‘H7 precision’ deletes the shaft and makes assembly verification impossible. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Keep the slash, both cases, the nominal diameter, and the drawing revision together. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
2. Uppercase H and lowercase g
Here is the technical distinction. Capital letters identify hole tolerance zones; lowercase letters identify shaft tolerance zones in the ISO code. In translation work, interpretation should follow the evidence rather than the other way round. The first question is not ‘What is a natural-sounding phrase for this term?’ but ‘What exactly would someone be entitled to conclude from the original?’ Preserve the original notation because it anchors future checking. Explain it in everyday words only after you have located its column heading, unit, edition and surrounding conditions. This protects both expert readers who need precision and newer readers who need a clear first explanation.
Read a realistic source situation: A scanned supplier sheet may show H7/G6; the capital G is not a harmless typographic variant of g. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: Automatic case normalisation can alter the actual feature represented by the code. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Compare the translated file visually with the controlled drawing rather than trusting spell-check. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
3. Nominal diameter
This part of the record often looks smaller than it is. The basic size locates the zero line from which upper and lower deviations are calculated; it is not necessarily the measured final dimension. The field may be only a code or a short phrase, yet that small string can influence a purchase, a drawing, an acceptance decision or a technical discussion. A useful educational translation says what the field controls and what it does not establish. It avoids adding a promise about strength, quality, safety, performance or conformity unless that promise already appears in the source and has an appropriate basis. Short explanatory wording is possible, but only after the underlying distinction is understood.
Read a realistic source situation: A nominal 25 mm feature can lawfully measure slightly above or below that figure according to its class. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: Saying ‘exactly 25 mm’ wrongly abolishes the permitted tolerance interval. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Include the diameter symbol and nominal size in the same line as its tolerance class. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
4. The H hole zero deviation
Start with what the entry actually describes. For an H hole, the lower deviation sits at zero relative to nominal size; positive variation is determined by the IT grade and size band. This is a useful place to distinguish a controlled label from a general-language impression. Two expressions may be close enough for casual conversation but not close enough for procurement or technical acceptance. A good translation names the property before describing its implications. It also keeps the reader aware of whether the source is specifying a required value, recording an observed result or offering an explanatory note. Those are different speech acts with different consequences. If the source is silent about a condition, the translation must remain silent about that condition too.
Read a realistic source situation: An illustrative 25 H7 bore has a lower limit of 25.000 mm and an upper limit of 25.021 mm. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: A target-language sentence claiming both sides are symmetric would change the acceptable hole range. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Preserve signed deviations and identify which deviation belongs to which limit. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
5. The g shaft below the zero line
Here is the technical distinction. A g shaft tolerance zone lies below nominal size, producing positive clearance with an H hole in a typical H7/g6 pairing. In translation work, interpretation should follow the evidence rather than the other way round. The first question is not ‘What is a natural-sounding phrase for this term?’ but ‘What exactly would someone be entitled to conclude from the original?’ Preserve the original notation because it anchors future checking. Explain it in everyday words only after you have located its column heading, unit, edition and surrounding conditions. This protects both expert readers who need precision and newer readers who need a clear first explanation.
Read a realistic source situation: At 25 mm, a commonly referenced g6 interval is 24.980 to 24.993 mm, subject to the governing ISO tables. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: A translation that describes g6 as a positive oversize shaft reverses the assembly consequence. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Look up both the fundamental deviation and grade width for the exact nominal size band. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
6. The number as IT grade
This part of the record often looks smaller than it is. The numeral denotes a tolerance grade and controls interval width; it is not a serial number, hardness code or quality certificate. The field may be only a code or a short phrase, yet that small string can influence a purchase, a drawing, an acceptance decision or a technical discussion. A useful educational translation says what the field controls and what it does not establish. It avoids adding a promise about strength, quality, safety, performance or conformity unless that promise already appears in the source and has an appropriate basis. Short explanatory wording is possible, but only after the underlying distinction is understood.
Read a realistic source situation: H7 and H8 can use the same basic-position letter while allowing different dimensional spreads. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: Converting 7 to ‘quality level seven’ invites unsupported ranking comparisons. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Explain ‘grade’ as dimensional tolerance width and retain the original alphanumeric identifier. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
7. Fundamental deviation versus width
Start with what the entry actually describes. The letter primarily positions a tolerance zone; the numeral chiefly sets its width within the relevant diameter band. This is a useful place to distinguish a controlled label from a general-language impression. Two expressions may be close enough for casual conversation but not close enough for procurement or technical acceptance. A good translation names the property before describing its implications. It also keeps the reader aware of whether the source is specifying a required value, recording an observed result or offering an explanatory note. Those are different speech acts with different consequences. If the source is silent about a condition, the translation must remain silent about that condition too.
Read a realistic source situation: Changing g6 to h6 shifts the shaft tolerance position even though both carry the numeral 6. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: A translator may preserve the word ‘six’ while losing the change in position. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Check letter and digit independently before declaring two fits equivalent. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
8. Nominal-size bands
Here is the technical distinction. ISO limit deviation tables are stratified by basic-size ranges, so the same code can allow different micrometre limits at different diameters. In translation work, interpretation should follow the evidence rather than the other way round. The first question is not ‘What is a natural-sounding phrase for this term?’ but ‘What exactly would someone be entitled to conclude from the original?’ Preserve the original notation because it anchors future checking. Explain it in everyday words only after you have located its column heading, unit, edition and surrounding conditions. This protects both expert readers who need precision and newer readers who need a clear first explanation.
Read a realistic source situation: A 10 mm H7 feature is not assigned the same interval as a 100 mm H7 feature. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: Copying the numerical limits from an unrelated size-band example is not technical translation. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Use the exact dimension range stated in the governing published table. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
9. Micrometres and millimetres
This part of the record often looks smaller than it is. One micrometre is 0.001 millimetre, so conversion requires moving three decimal places while retaining sign and precision. The field may be only a code or a short phrase, yet that small string can influence a purchase, a drawing, an acceptance decision or a technical discussion. A useful educational translation says what the field controls and what it does not establish. It avoids adding a promise about strength, quality, safety, performance or conformity unless that promise already appears in the source and has an appropriate basis. Short explanatory wording is possible, but only after the underlying distinction is understood.
Read a realistic source situation: A deviation of +21 µm corresponds to +0.021 mm, not +0.21 mm. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: OCR can drop µ or a decimal zero, creating a tenfold or thousandfold error. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Verify signed values with an independent unit-conversion check and the original table. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
10. Signed upper and lower limits
Start with what the entry actually describes. A dimension may be supplied as nominal plus upper and lower signed deviations rather than as explicit minimum and maximum sizes. This is a useful place to distinguish a controlled label from a general-language impression. Two expressions may be close enough for casual conversation but not close enough for procurement or technical acceptance. A good translation names the property before describing its implications. It also keeps the reader aware of whether the source is specifying a required value, recording an observed result or offering an explanatory note. Those are different speech acts with different consequences. If the source is silent about a condition, the translation must remain silent about that condition too.
Read a realistic source situation: A hole 25 +0.021/0 is a bounded interval, not permission for any positive oversize. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: Some localisations reverse stacked notation or omit the lower zero. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Write a plain-language limit statement beside the preserved callout when clarity is needed. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
11. Maximum and minimum clearance
Here is the technical distinction. Clearance is the hole diameter minus shaft diameter, evaluated at both extreme permitted combinations. In translation work, interpretation should follow the evidence rather than the other way round. The first question is not ‘What is a natural-sounding phrase for this term?’ but ‘What exactly would someone be entitled to conclude from the original?’ Preserve the original notation because it anchors future checking. Explain it in everyday words only after you have located its column heading, unit, edition and surrounding conditions. This protects both expert readers who need precision and newer readers who need a clear first explanation.
Read a realistic source situation: For illustrative 25 H7/g6 values, minimum clearance is 25.000 minus 24.993, or 0.007 mm. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: Calling the pair a ‘0.021 mm clearance fit’ mistakes the hole’s upper deviation for an assembly gap. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Calculate extreme pairs separately, with assumptions visible, instead of copying a single number. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
12. Hole-basis and shaft-basis systems
This part of the record often looks smaller than it is. A hole-basis design commonly holds an H hole zone while different shaft zones establish clearance, transition or interference. The field may be only a code or a short phrase, yet that small string can influence a purchase, a drawing, an acceptance decision or a technical discussion. A useful educational translation says what the field controls and what it does not establish. It avoids adding a promise about strength, quality, safety, performance or conformity unless that promise already appears in the source and has an appropriate basis. Short explanatory wording is possible, but only after the underlying distinction is understood.
Read a realistic source situation: A purchasing document may specify H7 with alternate shaft classes for distinct bearing seats. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: Translating every fit as ‘hole tolerance’ conceals the design choice of the mating part. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Identify the reference feature and check whether the drawing uses H or h as its basis. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
13. Clearance versus transition
Start with what the entry actually describes. Clearance fits allow a nonnegative dimensional gap in their specified extreme combinations; transition fits can allow either slight clearance or interference. This is a useful place to distinguish a controlled label from a general-language impression. Two expressions may be close enough for casual conversation but not close enough for procurement or technical acceptance. A good translation names the property before describing its implications. It also keeps the reader aware of whether the source is specifying a required value, recording an observed result or offering an explanatory note. Those are different speech acts with different consequences. If the source is silent about a condition, the translation must remain silent about that condition too.
Read a realistic source situation: A notation with k6 may behave differently from g6 even when both appear in a list of preferred fits. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: Language such as ‘snug’ is too imprecise to determine whether force is needed to assemble parts. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Describe the mathematical ranges and avoid promising an assembly feel. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
14. Interference fits
Here is the technical distinction. An interference fit is not simply a smaller clearance; the shaft can exceed the hole within the specified limits. In translation work, interpretation should follow the evidence rather than the other way round. The first question is not ‘What is a natural-sounding phrase for this term?’ but ‘What exactly would someone be entitled to conclude from the original?’ Preserve the original notation because it anchors future checking. Explain it in everyday words only after you have located its column heading, unit, edition and surrounding conditions. This protects both expert readers who need precision and newer readers who need a clear first explanation.
Read a realistic source situation: A translated maintenance manual may refer to H7/p6 or another press-fit pairing. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: Replacing ‘interference’ with ‘tight’ hides whether disassembly or press equipment may be relevant. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Preserve the actual class and verify resulting minimum and maximum interference from the drawing. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
15. GD&T is a separate layer
This part of the record often looks smaller than it is. Size tolerance does not automatically specify roundness, coaxiality, surface texture or positional relationship to other features. The field may be only a code or a short phrase, yet that small string can influence a purchase, a drawing, an acceptance decision or a technical discussion. A useful educational translation says what the field controls and what it does not establish. It avoids adding a promise about strength, quality, safety, performance or conformity unless that promise already appears in the source and has an appropriate basis. Short explanatory wording is possible, but only after the underlying distinction is understood.
Read a realistic source situation: A shaft may satisfy diameter limits but fail a geometric tolerance placed in a nearby feature-control frame. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: A translation that interprets the fit code as proof of alignment adds an unsupported quality claim. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Inspect adjacent geometric symbols, datum references and notes independently. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
16. Surface finish and fit
Start with what the entry actually describes. Surface roughness affects friction, wear and practical assembly but should not be silently substituted for a dimensional fit requirement. This is a useful place to distinguish a controlled label from a general-language impression. Two expressions may be close enough for casual conversation but not close enough for procurement or technical acceptance. A good translation names the property before describing its implications. It also keeps the reader aware of whether the source is specifying a required value, recording an observed result or offering an explanatory note. Those are different speech acts with different consequences. If the source is silent about a condition, the translation must remain silent about that condition too.
Read a realistic source situation: A drawing might specify H7/g6 and a separate Ra requirement for the mating surfaces. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: Calling the tolerance a ‘polished sliding finish’ merges unrelated instructions. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Preserve Ra and dimensional codes as separate acceptance questions. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
17. Thermal expansion
Here is the technical distinction. Measurement and assembly conditions can affect size, especially when components and instruments differ in temperature. In translation work, interpretation should follow the evidence rather than the other way round. The first question is not ‘What is a natural-sounding phrase for this term?’ but ‘What exactly would someone be entitled to conclude from the original?’ Preserve the original notation because it anchors future checking. Explain it in everyday words only after you have located its column heading, unit, edition and surrounding conditions. This protects both expert readers who need precision and newer readers who need a clear first explanation.
Read a realistic source situation: A drawing may reference standard temperature or include a special inspection note for a heated component. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: A target-language ‘room temperature’ assumption can be wrong when the source specifies conditions. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Keep temperature qualifiers and material context rather than inferring operating clearance. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
18. Metrology uncertainty
This part of the record often looks smaller than it is. The difference between measured value and specified limit can be comparable to measurement uncertainty. The field may be only a code or a short phrase, yet that small string can influence a purchase, a drawing, an acceptance decision or a technical discussion. A useful educational translation says what the field controls and what it does not establish. It avoids adding a promise about strength, quality, safety, performance or conformity unless that promise already appears in the source and has an appropriate basis. Short explanatory wording is possible, but only after the underlying distinction is understood.
Read a realistic source situation: A gauge reading 25.020 mm for a 25 H7 bore is not a complete decision record without measurement context. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: Treating a rounded measurement as perfectly exact may overstate compliance. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Copy the method, calibration context, units, uncertainty and decision rule when available. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
19. OCR and drawing exports
Start with what the entry actually describes. PDF extraction can replace Ø with O, µ with u, slash with punctuation or a lowercase letter with uppercase. This is a useful place to distinguish a controlled label from a general-language impression. Two expressions may be close enough for casual conversation but not close enough for procurement or technical acceptance. A good translation names the property before describing its implications. It also keeps the reader aware of whether the source is specifying a required value, recording an observed result or offering an explanatory note. Those are different speech acts with different consequences. If the source is silent about a condition, the translation must remain silent about that condition too.
Read a realistic source situation: A callout ‘Ø25 H7/g6’ might emerge from OCR as ‘O25 H7/G6’. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: A linguistically fluent translation can still be mechanically incorrect due to corrupted symbols. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Reinspect the raster drawing or CAD export character by character. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
20. Part identity and revision
Here is the technical distinction. Fit requirements apply to particular interfaces and part revisions, not to every component that shares a family name. In translation work, interpretation should follow the evidence rather than the other way round. The first question is not ‘What is a natural-sounding phrase for this term?’ but ‘What exactly would someone be entitled to conclude from the original?’ Preserve the original notation because it anchors future checking. Explain it in everyday words only after you have located its column heading, unit, edition and surrounding conditions. This protects both expert readers who need precision and newer readers who need a clear first explanation.
Read a realistic source situation: A receiving-inspection sheet may report a shaft dimension for revision C while the assembly drawing calls for revision D. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: A translation that omits the revision identifier can direct inspection to an obsolete specification. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Preserve drawing number, revision, quantity, feature identifier and issue date. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
21. Supplier equivalence claims
This part of the record often looks smaller than it is. A supplier may suggest a local fit notation or machining convention as equivalent to ISO 286. The field may be only a code or a short phrase, yet that small string can influence a purchase, a drawing, an acceptance decision or a technical discussion. A useful educational translation says what the field controls and what it does not establish. It avoids adding a promise about strength, quality, safety, performance or conformity unless that promise already appears in the source and has an appropriate basis. Short explanatory wording is possible, but only after the underlying distinction is understood.
Read a realistic source situation: An alternative national or company standard might appear on a translated quotation. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: Language equivalence does not by itself demonstrate dimensional equivalence across standards. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Ask for explicit limit values and a documented crosswalk reviewed by a competent engineer. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
22. Assembly troubleshooting
Start with what the entry actually describes. An overly tight assembled fit may be caused by geometry, coatings, thermal effects or tolerance errors, not by wording alone. This is a useful place to distinguish a controlled label from a general-language impression. Two expressions may be close enough for casual conversation but not close enough for procurement or technical acceptance. A good translation names the property before describing its implications. It also keeps the reader aware of whether the source is specifying a required value, recording an observed result or offering an explanatory note. Those are different speech acts with different consequences. If the source is silent about a condition, the translation must remain silent about that condition too.
Read a realistic source situation: When an inspection report says ‘shaft in tolerance’, it may not settle the full interference problem. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: Publishing a translated diagnosis as proof of a single cause overreaches the evidence. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Separate observation, hypothesis, dimension calculation and corrective decision. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
23. Acceptance language
Here is the technical distinction. ‘Measured’, ‘within tolerance’, ‘released’ and ‘approved for assembly’ describe different administrative steps. In translation work, interpretation should follow the evidence rather than the other way round. The first question is not ‘What is a natural-sounding phrase for this term?’ but ‘What exactly would someone be entitled to conclude from the original?’ Preserve the original notation because it anchors future checking. Explain it in everyday words only after you have located its column heading, unit, edition and surrounding conditions. This protects both expert readers who need precision and newer readers who need a clear first explanation.
Read a realistic source situation: A bilingual inspection certificate may show an in-range result but also a hold note for another characteristic. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: Using ‘approved’ to translate ‘inspected’ can prematurely release goods. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Keep the issuer’s actual status wording and cross-check the authorised sign-off field. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
24. Educational explanation versus redesign
This part of the record often looks smaller than it is. A good translation can teach readers how a fit code works without substituting a different class or recommending an engineering change. The field may be only a code or a short phrase, yet that small string can influence a purchase, a drawing, an acceptance decision or a technical discussion. A useful educational translation says what the field controls and what it does not establish. It avoids adding a promise about strength, quality, safety, performance or conformity unless that promise already appears in the source and has an appropriate basis. Short explanatory wording is possible, but only after the underlying distinction is understood.
Read a realistic source situation: A learner may ask why a 25 H7/g6 design has clearance; the explanation belongs beside, not inside, the callout. Ask what a colleague would do after reading this line in another language. Would they order a component, inspect a sample, compare a result, approve a certificate or ask a follow-up question? The translation should support precisely the action justified by the source, not a stronger or weaker action invented by the editor. When the field is a coded expression, retain the code beside the expanded explanation. When it is a measurement, keep its original sign, decimal precision and unit. When it is a categorical observation, do not turn it into a continuous quantity merely because that sounds easier to compare.
The predictable failure mode is this: Rewriting g6 as h6 to make an example ‘easier’ would alter the requirements. A translator should pause at this point and test the sentence in reverse. If a reader translated the target text back into the source language, would the same technical fact, limit and uncertainty emerge? An attractive sentence that returns a different answer has not preserved meaning. This is why translation quality assurance needs more than spelling and grammar review. It needs a comparison of the technical object, property, conditions, identifiers and decision status. The governing standard and the contract may also set different roles: do not collapse a method’s test result into a customer’s final acceptance.
A useful verification action is: Clearly mark worked examples as illustrative and keep controlled drawings unchanged. Record this check in a small comparison ledger: source field, target wording, reason for the chosen wording, and supporting reference. If the reader is a beginner, add a short explanation after the unchanged notation rather than replacing it. If the reader is a technical buyer, supply the source table or certificate link. If the reader is a reviewer, make any unresolved ambiguity visible. The same core facts can be presented at several reading levels, but they should not change with the audience. Accuracy is a property of the evidence relationship, not a matter of sounding impressive.
Ten practical translation situations, with a decision pathway
Situation 1: A purchasing order with the shaft class removed
Imagine this exact problem arriving as a short email with an attachment: A purchasing order with the shaft class removed. The tempting response is to smooth over the ambiguity in one sentence so that the bilingual document appears finished. Resist that temptation. First identify the original field or passage where the ambiguity arose. Then write down the two interpretations that a competent reader could reasonably take from it. The problem is resolved only when the target text supports the same interpretation as the source, or when the issuer supplies a correction. A translator may flag the issue but should not silently choose a new engineering or commercial requirement. This separation is particularly important when an international team treats the translated report as its only working copy.
A practical review would compare the line with its table heading, surrounding notes, source standard, version and any specimen or part identifier. Preserve the exact token that anchors the issue, and put the explanatory sentence immediately after it. Ask for confirmation from the issuer if the document is internally inconsistent. In the final handover, identify what was translated, what was copied unchanged and which matter still needs a specialist’s decision. A helpful reader-facing summary might state that the reported information cannot by itself justify a particular conclusion. That is not evasive writing: it tells readers exactly what the evidence can bear. The lesson also transfers to other fields, where notation may remain unchanged but its surrounding vocabulary must be carefully localised.
Situation 2: An OCR export that capitalises every letter
Imagine this exact problem arriving as a short email with an attachment: An OCR export that capitalises every letter. The tempting response is to smooth over the ambiguity in one sentence so that the bilingual document appears finished. Resist that temptation. First identify the original field or passage where the ambiguity arose. Then write down the two interpretations that a competent reader could reasonably take from it. The problem is resolved only when the target text supports the same interpretation as the source, or when the issuer supplies a correction. A translator may flag the issue but should not silently choose a new engineering or commercial requirement. This separation is particularly important when an international team treats the translated report as its only working copy.
A practical review would compare the line with its table heading, surrounding notes, source standard, version and any specimen or part identifier. Preserve the exact token that anchors the issue, and put the explanatory sentence immediately after it. Ask for confirmation from the issuer if the document is internally inconsistent. In the final handover, identify what was translated, what was copied unchanged and which matter still needs a specialist’s decision. A helpful reader-facing summary might state that the reported information cannot by itself justify a particular conclusion. That is not evasive writing: it tells readers exactly what the evidence can bear. The lesson also transfers to other fields, where notation may remain unchanged but its surrounding vocabulary must be carefully localised.
Situation 3: A micrometre-to-millimetre decimal error
Imagine this exact problem arriving as a short email with an attachment: A micrometre-to-millimetre decimal error. The tempting response is to smooth over the ambiguity in one sentence so that the bilingual document appears finished. Resist that temptation. First identify the original field or passage where the ambiguity arose. Then write down the two interpretations that a competent reader could reasonably take from it. The problem is resolved only when the target text supports the same interpretation as the source, or when the issuer supplies a correction. A translator may flag the issue but should not silently choose a new engineering or commercial requirement. This separation is particularly important when an international team treats the translated report as its only working copy.
A practical review would compare the line with its table heading, surrounding notes, source standard, version and any specimen or part identifier. Preserve the exact token that anchors the issue, and put the explanatory sentence immediately after it. Ask for confirmation from the issuer if the document is internally inconsistent. In the final handover, identify what was translated, what was copied unchanged and which matter still needs a specialist’s decision. A helpful reader-facing summary might state that the reported information cannot by itself justify a particular conclusion. That is not evasive writing: it tells readers exactly what the evidence can bear. The lesson also transfers to other fields, where notation may remain unchanged but its surrounding vocabulary must be carefully localised.
Situation 4: A supplier promising a ‘close fit’ without numerical limits
Imagine this exact problem arriving as a short email with an attachment: A supplier promising a ‘close fit’ without numerical limits. The tempting response is to smooth over the ambiguity in one sentence so that the bilingual document appears finished. Resist that temptation. First identify the original field or passage where the ambiguity arose. Then write down the two interpretations that a competent reader could reasonably take from it. The problem is resolved only when the target text supports the same interpretation as the source, or when the issuer supplies a correction. A translator may flag the issue but should not silently choose a new engineering or commercial requirement. This separation is particularly important when an international team treats the translated report as its only working copy.
A practical review would compare the line with its table heading, surrounding notes, source standard, version and any specimen or part identifier. Preserve the exact token that anchors the issue, and put the explanatory sentence immediately after it. Ask for confirmation from the issuer if the document is internally inconsistent. In the final handover, identify what was translated, what was copied unchanged and which matter still needs a specialist’s decision. A helpful reader-facing summary might state that the reported information cannot by itself justify a particular conclusion. That is not evasive writing: it tells readers exactly what the evidence can bear. The lesson also transfers to other fields, where notation may remain unchanged but its surrounding vocabulary must be carefully localised.
Situation 5: A receiving inspection with missing temperature notes
Imagine this exact problem arriving as a short email with an attachment: A receiving inspection with missing temperature notes. The tempting response is to smooth over the ambiguity in one sentence so that the bilingual document appears finished. Resist that temptation. First identify the original field or passage where the ambiguity arose. Then write down the two interpretations that a competent reader could reasonably take from it. The problem is resolved only when the target text supports the same interpretation as the source, or when the issuer supplies a correction. A translator may flag the issue but should not silently choose a new engineering or commercial requirement. This separation is particularly important when an international team treats the translated report as its only working copy.
A practical review would compare the line with its table heading, surrounding notes, source standard, version and any specimen or part identifier. Preserve the exact token that anchors the issue, and put the explanatory sentence immediately after it. Ask for confirmation from the issuer if the document is internally inconsistent. In the final handover, identify what was translated, what was copied unchanged and which matter still needs a specialist’s decision. A helpful reader-facing summary might state that the reported information cannot by itself justify a particular conclusion. That is not evasive writing: it tells readers exactly what the evidence can bear. The lesson also transfers to other fields, where notation may remain unchanged but its surrounding vocabulary must be carefully localised.
Situation 6: A drawing that combines diameter limits and a separate datum tolerance
Imagine this exact problem arriving as a short email with an attachment: A drawing that combines diameter limits and a separate datum tolerance. The tempting response is to smooth over the ambiguity in one sentence so that the bilingual document appears finished. Resist that temptation. First identify the original field or passage where the ambiguity arose. Then write down the two interpretations that a competent reader could reasonably take from it. The problem is resolved only when the target text supports the same interpretation as the source, or when the issuer supplies a correction. A translator may flag the issue but should not silently choose a new engineering or commercial requirement. This separation is particularly important when an international team treats the translated report as its only working copy.
A practical review would compare the line with its table heading, surrounding notes, source standard, version and any specimen or part identifier. Preserve the exact token that anchors the issue, and put the explanatory sentence immediately after it. Ask for confirmation from the issuer if the document is internally inconsistent. In the final handover, identify what was translated, what was copied unchanged and which matter still needs a specialist’s decision. A helpful reader-facing summary might state that the reported information cannot by itself justify a particular conclusion. That is not evasive writing: it tells readers exactly what the evidence can bear. The lesson also transfers to other fields, where notation may remain unchanged but its surrounding vocabulary must be carefully localised.
Situation 7: Two design revisions arriving in the same shipment
Imagine this exact problem arriving as a short email with an attachment: Two design revisions arriving in the same shipment. The tempting response is to smooth over the ambiguity in one sentence so that the bilingual document appears finished. Resist that temptation. First identify the original field or passage where the ambiguity arose. Then write down the two interpretations that a competent reader could reasonably take from it. The problem is resolved only when the target text supports the same interpretation as the source, or when the issuer supplies a correction. A translator may flag the issue but should not silently choose a new engineering or commercial requirement. This separation is particularly important when an international team treats the translated report as its only working copy.
A practical review would compare the line with its table heading, surrounding notes, source standard, version and any specimen or part identifier. Preserve the exact token that anchors the issue, and put the explanatory sentence immediately after it. Ask for confirmation from the issuer if the document is internally inconsistent. In the final handover, identify what was translated, what was copied unchanged and which matter still needs a specialist’s decision. A helpful reader-facing summary might state that the reported information cannot by itself justify a particular conclusion. That is not evasive writing: it tells readers exactly what the evidence can bear. The lesson also transfers to other fields, where notation may remain unchanged but its surrounding vocabulary must be carefully localised.
Situation 8: A machine operator confusing nominal size with exact size
Imagine this exact problem arriving as a short email with an attachment: A machine operator confusing nominal size with exact size. The tempting response is to smooth over the ambiguity in one sentence so that the bilingual document appears finished. Resist that temptation. First identify the original field or passage where the ambiguity arose. Then write down the two interpretations that a competent reader could reasonably take from it. The problem is resolved only when the target text supports the same interpretation as the source, or when the issuer supplies a correction. A translator may flag the issue but should not silently choose a new engineering or commercial requirement. This separation is particularly important when an international team treats the translated report as its only working copy.
A practical review would compare the line with its table heading, surrounding notes, source standard, version and any specimen or part identifier. Preserve the exact token that anchors the issue, and put the explanatory sentence immediately after it. Ask for confirmation from the issuer if the document is internally inconsistent. In the final handover, identify what was translated, what was copied unchanged and which matter still needs a specialist’s decision. A helpful reader-facing summary might state that the reported information cannot by itself justify a particular conclusion. That is not evasive writing: it tells readers exactly what the evidence can bear. The lesson also transfers to other fields, where notation may remain unchanged but its surrounding vocabulary must be carefully localised.
Situation 9: A technician reporting only mean clearance
Imagine this exact problem arriving as a short email with an attachment: A technician reporting only mean clearance. The tempting response is to smooth over the ambiguity in one sentence so that the bilingual document appears finished. Resist that temptation. First identify the original field or passage where the ambiguity arose. Then write down the two interpretations that a competent reader could reasonably take from it. The problem is resolved only when the target text supports the same interpretation as the source, or when the issuer supplies a correction. A translator may flag the issue but should not silently choose a new engineering or commercial requirement. This separation is particularly important when an international team treats the translated report as its only working copy.
A practical review would compare the line with its table heading, surrounding notes, source standard, version and any specimen or part identifier. Preserve the exact token that anchors the issue, and put the explanatory sentence immediately after it. Ask for confirmation from the issuer if the document is internally inconsistent. In the final handover, identify what was translated, what was copied unchanged and which matter still needs a specialist’s decision. A helpful reader-facing summary might state that the reported information cannot by itself justify a particular conclusion. That is not evasive writing: it tells readers exactly what the evidence can bear. The lesson also transfers to other fields, where notation may remain unchanged but its surrounding vocabulary must be carefully localised.
Situation 10: A translated factory acceptance certificate claiming release too early
Imagine this exact problem arriving as a short email with an attachment: A translated factory acceptance certificate claiming release too early. The tempting response is to smooth over the ambiguity in one sentence so that the bilingual document appears finished. Resist that temptation. First identify the original field or passage where the ambiguity arose. Then write down the two interpretations that a competent reader could reasonably take from it. The problem is resolved only when the target text supports the same interpretation as the source, or when the issuer supplies a correction. A translator may flag the issue but should not silently choose a new engineering or commercial requirement. This separation is particularly important when an international team treats the translated report as its only working copy.
A practical review would compare the line with its table heading, surrounding notes, source standard, version and any specimen or part identifier. Preserve the exact token that anchors the issue, and put the explanatory sentence immediately after it. Ask for confirmation from the issuer if the document is internally inconsistent. In the final handover, identify what was translated, what was copied unchanged and which matter still needs a specialist’s decision. A helpful reader-facing summary might state that the reported information cannot by itself justify a particular conclusion. That is not evasive writing: it tells readers exactly what the evidence can bear. The lesson also transfers to other fields, where notation may remain unchanged but its surrounding vocabulary must be carefully localised.
A bilingual quality-control worksheet
Use the following headings for an actual review sheet: document title; issuer; document identifier; edition; original language; target language; original technical code; translated explanatory label; physical object or lot; units; limits or class; observations; assumptions; source page; decision status; reviewer; unresolved queries. This is intentionally smaller than a complete translation management system. It can be used in a spreadsheet, email handover or project notebook, while the master process and broader language-learning foundations remain in their existing canonical homes.
The worksheet should not become a second independent source of truth. If a supplier issues a corrected report, note the new revision and preserve the earlier version in an appropriate audit record. If a translation contains a mistake, state what changed and why. Avoid rewriting historical results after the fact merely to make documents agree. A reader should always know whether they are looking at an original observation, a revision, a translation, an explanatory commentary or a later approval decision. That distinction is the foundation of reliable multilingual technical communication.
Frequently asked questions
Does H7/g6 itself specify a single clearance value?
Begin with the exact wording and the document’s function, not with an isolated number found in an online summary. For this question, the reliable answer is to preserve the controlling notation and determine what property, procedure or decision the source actually describes. H7 designates the hole’s tolerance class and g6 the shaft’s. It is a pair, not an optional decorative suffix. If the question is about equivalence, do not assume two apparently similar labels are interchangeable; use the relevant standard and evidence. If it is about an acceptance result, distinguish observation from approval. If it concerns an actual purchase, installation, test or safety decision, the issuer or an appropriately qualified reviewer should confirm the requirement before it is acted upon.
Why must H and g keep their letter case?
Begin with the exact wording and the document’s function, not with an isolated number found in an online summary. For this question, the reliable answer is to preserve the controlling notation and determine what property, procedure or decision the source actually describes. For an H hole, the lower deviation sits at zero relative to nominal size; positive variation is determined by the IT grade and size band. If the question is about equivalence, do not assume two apparently similar labels are interchangeable; use the relevant standard and evidence. If it is about an acceptance result, distinguish observation from approval. If it concerns an actual purchase, installation, test or safety decision, the issuer or an appropriately qualified reviewer should confirm the requirement before it is acted upon.
May a translated drawing use only micrometres?
Begin with the exact wording and the document’s function, not with an isolated number found in an online summary. For this question, the reliable answer is to preserve the controlling notation and determine what property, procedure or decision the source actually describes. The letter primarily positions a tolerance zone; the numeral chiefly sets its width within the relevant diameter band. If the question is about equivalence, do not assume two apparently similar labels are interchangeable; use the relevant standard and evidence. If it is about an acceptance result, distinguish observation from approval. If it concerns an actual purchase, installation, test or safety decision, the issuer or an appropriately qualified reviewer should confirm the requirement before it is acted upon.
Does a clearance fit guarantee smooth operation?
Begin with the exact wording and the document’s function, not with an isolated number found in an online summary. For this question, the reliable answer is to preserve the controlling notation and determine what property, procedure or decision the source actually describes. A dimension may be supplied as nominal plus upper and lower signed deviations rather than as explicit minimum and maximum sizes. If the question is about equivalence, do not assume two apparently similar labels are interchangeable; use the relevant standard and evidence. If it is about an acceptance result, distinguish observation from approval. If it concerns an actual purchase, installation, test or safety decision, the issuer or an appropriately qualified reviewer should confirm the requirement before it is acted upon.
Can tolerance grades be translated as product quality grades?
Begin with the exact wording and the document’s function, not with an isolated number found in an online summary. For this question, the reliable answer is to preserve the controlling notation and determine what property, procedure or decision the source actually describes. Clearance fits allow a nonnegative dimensional gap in their specified extreme combinations; transition fits can allow either slight clearance or interference. If the question is about equivalence, do not assume two apparently similar labels are interchangeable; use the relevant standard and evidence. If it is about an acceptance result, distinguish observation from approval. If it concerns an actual purchase, installation, test or safety decision, the issuer or an appropriately qualified reviewer should confirm the requirement before it is acted upon.
Is ISO 286-2:2010 still a current standard?
Begin with the exact wording and the document’s function, not with an isolated number found in an online summary. For this question, the reliable answer is to preserve the controlling notation and determine what property, procedure or decision the source actually describes. Surface roughness affects friction, wear and practical assembly but should not be silently substituted for a dimensional fit requirement. If the question is about equivalence, do not assume two apparently similar labels are interchangeable; use the relevant standard and evidence. If it is about an acceptance result, distinguish observation from approval. If it concerns an actual purchase, installation, test or safety decision, the issuer or an appropriately qualified reviewer should confirm the requirement before it is acted upon.
How this specialist guide connects to better language learning
Specialised translation is easier to learn when the writer has already mastered the difference between a term, its definition, its operational context and its consequences. A vocabulary glossary explains how words are used; it does not manufacture technical evidence. A reading framework helps learners ask what the sentence establishes and what remains uncertain. A broad translation architecture can coordinate terminology, references and review roles. This article deliberately stays at the level of translate ISO 286 H7/g6 machining fits and tolerances so that it solves a single high-intent reader problem rather than competing with more general hubs.
- Vocabulary Learning Hub
- How English Works: Translation and Meaning Across Languages
- Master Art of Translation: The Scientific Research and Scholarly Publishing Translation System
Primary references and further verification
The cited source descriptions are starting points for verification, not substitutes for licensed normative tables or the full original documents. All numerical illustrations and situations here are teaching examples unless expressly identified as actual source results. Consult the applicable edition and governing contract before using a translation to release goods, certify a test, alter a drawing or decide suitability for a safety-critical use.
Conclusion: fluent language must preserve the same technical decision
The strongest translation does two jobs at once. It makes unfamiliar information readable and stops readers making a decision the evidence never authorised. For translate ISO 286 H7/g6 machining fits and tolerances, that means matching the technical code to its original object, test or specification, then carrying over the units, qualifiers, method, edition and decision status intact. A skilled translator is not only asking whether the sentences sound natural. They are asking whether an engineer, inspector, student or buyer would reach the same justified understanding from both language versions.
A simple final test is to hide the original and ask a colleague to identify the exact requirement, the observations, the evidence source, what is still unknown and who may approve the outcome. If the colleague cannot answer, the document needs a clearer explanation or additional source information. If the colleague confidently answers something the original never said, the translation needs correction. Keep the language conversational, the structure navigable and the proof traceable. Then the article becomes useful knowledge rather than a long string of plausible words.