How can you translate a CNC drawing, roughness specification or surface texture inspection report containing ISO 21920-2:2021, Ra, Rz, Rq, µm and profile-filter settings without changing what an engineer must manufacture or inspect? Searches for ISO 21920 translation, Ra versus Rz meaning, surface finish symbol translation and machining inspection report English usually arise when a buyer and supplier need to agree on the same controlled evidence.
This educational guide distinguishes a drawing requirement from a measured result, explains the three parts of ISO 21920, reviews profile terminology and shows how to protect symbols, units, feature locations, legacy edition references, qualification statements and technical decisions in multilingual documents. It is for translators, mechanical engineers, metrology teams, students and international procurement readers.
The governing principle is to translate the language while preserving the engineering statement. A translator cannot convert Ra into Rz, move a callout to another surface, infer measurement settings that are absent or certify a part that the originating inspection team has not accepted. All examples are teaching examples; actual release requires the controlling drawings, licensed standards and technical authority.
Identify the source document’s legal and technical role
A released customer drawing, an inspection plan, a supplier’s result sheet and a commercial quotation may mention exactly the same roughness parameter. They are not the same kind of evidence. The drawing tells a manufacturer what is required; the inspection plan defines how a requirement is assessed; a measured result records an observation; a quotation may promise future capability.
If a buyer sends a revision-C drawing and a machinist replies with a worksheet marked Ra 0.8 µm, calling the worksheet a compliance certificate adds a decision the source may never have made. Preserve drawing revision, workpiece identifier, inspection date, issuing party and the worksheet’s actual status.
Give the translation a document-control line stating whether it is informational or contractually approved. Keep the responsible source owner and technical approver visible so that a fluent bilingual copy cannot masquerade as a newly authorized drawing.
Before signing off, ask the practical review question: Can another reader tell, from the first page alone, whether this file specifies a requirement, reports a measurement or records a disposition? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
Separate ISO 21920-1, -2 and -3
ISO 21920-1:2021 defines the indication of profile surface texture using graphical symbols in technical product documentation. ISO 21920-2:2021 provides terms and surface texture parameters; ISO 21920-3:2021 deals with specification operators. A translation should use the relevant part rather than treating the entire series as one interchangeable label.
A graphical callout on a bore may need a visual layout check under Part 1, while a column labelled Rq needs parameter terminology and a measurement statement may require Part 3 context. Translating a setting class as product grade shows what happens when these roles are confused.
Make a glossary entry containing exact part number, year, subject and source location. Preserve references as printed. An engineering revision, not a translator’s tidying, determines whether the cited standard is replaced.
The final technical-language check is: Has the translation kept the correct ISO part attached to each technical assertion? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
Ra is not a synonym for shiny
Ra is an arithmetic mean height parameter for a defined roughness profile. Everyday descriptions such as glossy, smooth, polished and fine finish can be useful in conversation, but none automatically conveys the computation or acceptance rule associated with Ra. A visually attractive surface can have texture that affects function.
If the source says Ra ≤ 0.8 µm, leave Ra, the inequality and the unit intact. Rendering the line as excellent polishing discards the numerical acceptance boundary and may imply a manufacturing process the drawing has not specified.
Treat the defined parameter as a protected token. Translate surrounding grammar, explain the meaning for novice readers if appropriate, and ensure any plain-language note cannot override the exact technical criterion.
At the handover stage verify the following: Does the target sentence still tell an inspector which numerical quantity to measure and which limit applies? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
Rq is calculated differently
Rq is a root mean square profile-height parameter. It gives larger height deviations a different mathematical weight from Ra, even when both are expressed in the same unit. Two adjacent spreadsheet columns headed Ra and Rq must remain two separate measured quantities after translation.
An illustrative report shows Ra 0.62 µm and Rq 0.79 µm. The translation should not rename both average roughness, discard one column or calculate one from the other using a borrowed generic ratio. The surface profile influences any relationship between their values.
Use a glossary with the symbol, parameter name, method reference, result and unit. If readers request a conversion, record that as an engineering question rather than an ordinary linguistic substitution.
Before signing off, ask the practical review question: Would a reader still recognize Ra and Rq as separately measured properties rather than alternative spellings of one value? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
Rz requires edition-aware interpretation
Rz refers to a peak-to-valley characteristic, but exact meanings and evaluation arrangements depend on the relevant convention and applicable edition. Old drawings and modern instrument software can use familiar symbols in different historical contexts. Identical letters do not necessarily demonstrate identical operators.
Suppose a 2016 customer drawing cites an older profile standard while a new laboratory report uses ISO 21920. A translator should record both citations and ask whether the approved comparison method supports the acceptance conclusion, not quietly rewrite the old requirement as the new one.
Preserve the original symbol, year, method reference, units and any measurement settings. If equivalence remains unresolved, state that it is unresolved. Engineers must own a change in measurement basis.
The final technical-language check is: Can the reviewer identify the exact governing edition and avoid assuming that matching parameter names always prove comparable test evidence? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
Rt, Rp and Rv have distinct purposes
Technical profiles contain several height-related parameters. A reader may see Rt, Rp and Rv beside Rz, but their symbols identify different defined quantities. Translating all of them as maximum roughness or surface height eliminates the distinctions that made the test record useful.
A quality report may mention a scratch and list an Rt value. The scratch could be a separate visual observation; the parameter is a computed result from a particular trace. A translator must not treat one as definitive proof of the other.
Keep each symbol in its own data column and preserve any limitation on the measurement. Do not claim that a numeric texture result demonstrates freedom from cracks, burrs, dents or damage governed by other inspections.
At the handover stage verify the following: Does every parameter have its own correct symbol and technical context in the bilingual report? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
Do not merge profile and areal methods
ISO 21920 concerns surface texture by profile methods. Areal texture methods examine an area and can use a different parameter family. Both describe surfaces, but the data and processing are not identical, so a translation that treats Sa as Ra can introduce a technical falsehood.
If the laboratory returns an areal map with Sa while the drawing specifies a profile Ra limit, the translation should preserve both statements. It is possible that engineering will request supplementary measurements or evaluate compatibility, but that decision needs evidence.
Record whether the acquisition was a stylus profile, optical profile, areal scan or other method. State what the source establishes without inventing cross-method equivalence.
Before signing off, ask the practical review question: Has the target text retained the measurement geometry and exact symbol instead of using generic average roughness everywhere? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
Roughness and waviness describe different scales
A physical surface can contain fine tool marks and longer-wavelength undulation. Roughness, waviness and primary-profile quantities help describe different components of that geometry. An everyday word like unevenness is too broad to retain all these scales in a technical report.
On a turned shaft, the seal engineer may care about small grooves while the vibration specialist studies broader variations. Collapsing R-, W- and P-parameter notation into one term can make their two concerns appear equivalent when they are not.
Keep the profile family prefixes, related filters and terms describing spatial scale. If the source does not make the category clear, ask the originating laboratory instead of selecting whichever phrase reads most naturally.
The final technical-language check is: Does the translation preserve the scale of variation that the instrument was instructed to report? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
Micrometres are easily corrupted
A micrometre is one thousandth of a millimetre. That makes a misplaced prefix or decimal point particularly consequential when machining limits are fine. Numeric localization is an editorial task, but numerical integrity is an inspection requirement.
The value 0,8 µm may be displayed as 0.8 µm under English decimal conventions. It must not become 8 µm, 0.8 mm or an approximate phrase such as less than a millimetre. Spreadsheet import rules can also split a decimal-comma field unexpectedly.
Maintain a numeric comparison record for source string, normalized display, unit and verified numeric value. Check OCR, CSV imports and PDF conversions independently from grammar review.
At the handover stage verify the following: Have all decimal separators, µ characters and magnitudes survived the transfer unchanged? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
Equality and inequality matter
Symbols such as <, >, ≤ and ≥ determine which region of measurement values satisfies a stated requirement. A maximum and a nominal target cannot be treated as interchangeable simply because they share a numeral. The translator should not infer a tolerance from a friendly-sounding phrase.
Illustratively, Ra ≤ 1.6 µm is an upper-bound statement; Ra = 1.6 µm appears to specify an exact value. Replacing the first with equals or about changes the meaning available to the inspector.
Compare every limit operator against the original visually. Retain tolerance signs, decimals and units alongside parameter symbols. If a required symbol is ambiguous in a scan, label the source as unclear pending technical confirmation.
Before signing off, ask the practical review question: Can the reader distinguish a target value, upper limit, lower limit and observed result? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
Drawing position is part of meaning
Surface texture symbols are positioned on engineering graphics for a reason. A leader line or attached indication can identify the precise face, bore, shoulder, seat or region subject to a requirement. Word-perfect translation is not sufficient when layout shifts the symbol.
A long translated note may be moved beside a neighboring feature to save space. If its arrow now appears to point at another surface, the document can instruct the manufacturer to inspect the wrong geometry.
Compare the source and target rendered drawings at the same scale. Protect arrowheads, section marks, feature identifiers and view orientation. Use keyed note tables when typography would otherwise displace a functional annotation.
The final technical-language check is: Can a machinist locate the same exact surface from the original and the translated document? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
Material-removal instructions are separate
An Ra requirement does not by itself command grinding, polishing or any specific finishing process. Some drawings separately require, prohibit or restrict material removal. The result and the approved manufacturing route are different kinds of instruction.
Turning, honing and grinding may yield overlapping roughness numbers yet create different functional textures. Translating an Ra specification as must be ground invents a process rule, while deleting a no-removal note can violate a real restriction.
Read adjacent manufacturing and procurement notes before choosing verbs. Preserve the difference between a required process, an allowed option and a measured outcome.
At the handover stage verify the following: Has the translation added or removed a machining operation that the source never authorized? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
Lay carries orientation
Surface lay refers to a prevailing texture direction. It can be functionally relevant for a sliding interface, seal, aesthetic region or manufacturing process. A lay symbol should not be translated merely as quality or visual finish.
If a callout describes texture orientation relative to motion, mistranslating parallel as perpendicular can cause an unwanted surface even if the measured Ra is acceptable. The numerical and directional requirements work together.
Preserve directional symbols, relevant axes and the physical frame of reference. If the target language requires a longer description, name the motion direction or specified feature rather than using ambiguous horizontal and vertical adjectives.
Before signing off, ask the practical review question: Would an engineer in the target language orient the machining marks in the same direction? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
Filter and nesting-index language
A profile trace contains variations at several scales, and filters help define the reported parameter. A result is influenced by how the trace is measured and processed. The associated nesting index is therefore part of the specification context rather than an optional detail.
Old documents may refer to cut-off while newer texts use nesting-index terminology. A careless substitution can imply that a setting was retained or changed without evidence. Likewise S- and L-filter references should not be merged into one generic smoothing label.
Preserve filter names, dimensions and any quoted settings. Refer an unclear legacy-to-current mapping to the metrology engineer and keep the original expression in the audit record.
The final technical-language check is: Are the original measurement-processing settings still recoverable from the translated text? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
Setting class is not product quality class
A setting class can establish default measurement conditions within a specification operator. It is not equivalent to a commercial grade of component or an inspection result. Words like class, grade and category are notorious for acquiring unintended meanings across languages.
Sc3 should remain Sc3, accompanied by a plain-language explanation that it concerns settings. Translating it as third-class quality or class-three surface finish falsely ranks the workpiece.
Ask the reviewer to compare the setting class with any explicit exceptions on the drawing or report. Preserve both so the applicable operator can be reconstructed by a competent reader.
At the handover stage verify the following: Does the translated class refer to the measurement arrangement, not to an unsupported quality tier? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
Evaluation length and section length
The evaluation length concerns the profile used to calculate a parameter; section length is another defined measurement concept. Neither should be confused with the overall shaft length, the number of samples or the length of a drawing feature.
One profile may contain several sections. The phrase five sections assessed does not mean five separate workpieces were sampled. Misstating this point exaggerates inspection coverage.
Keep length symbols, units, number of traces, section count and physical specimen count in separate fields. When the laboratory omits an essential setting, report it as missing instead of inserting a guessed default.
Before signing off, ask the practical review question: Could a reader accurately reconstruct how many surfaces, traces and physical parts were inspected? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
Instrument geometry and resolution
A stylus-tip radius, nominal sampling distance, probe configuration or optical acquisition method describes the measuring instrument. The same unit may appear in both instrument details and product texture requirements without meaning the same thing.
If a report states a 2 µm stylus radius, it must not be translated as a 2 µm Ra limit. The number describes the contact geometry, not the workpiece’s allowed texture height.
Keep the instrument model, serial number, scan orientation, measurement configuration and any declared limitation. Preserve the original scope of the reading rather than treating the instrument specification as compliance evidence.
The final technical-language check is: Can the reader distinguish an instrument setting from an inspected surface result? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
Calibration evidence is not product approval
Calibration provides a documented basis for understanding the measuring system under stated conditions. It is different from measuring a manufactured surface and different again from making a product acceptance decision. Translators often encounter all three documents in one inspection pack.
A reference specimen’s calibration certificate cannot be described as the customer’s shaft passing roughness inspection. The records may support each other, but their subject, date and purpose remain separate.
Protect certificate IDs, dates, reference artefacts, instrument identifiers, uncertainty statements and accreditation claims. Never add a certification that the source does not actually document.
At the handover stage verify the following: Does each translated certificate identify the correct object of measurement and the correct claim? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
Sampling scope and lot claims
A laboratory may take multiple traces on one surface, measure several positions on one component or inspect different specimens from a batch. These forms of repetition have different meanings. The English statement several tests is insufficient when a buyer expects lot-level evidence.
Three locations on one shaft are not three shafts. Similarly a sample result is not automatically proof that every item in a production lot meets the same condition.
Translate sample size, item count, measurement positions, repeated readings, excluded areas and final disposition independently. Do not expand a finding beyond the source’s sampling basis.
Before signing off, ask the practical review question: Does the target text preserve exactly which population the evidence covers? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
Specification, result and decision have different owners
An inspection row may include the customer’s required limit, the laboratory’s measured result and an authorized pass or fail statement. The first is a specification, the second an observation and the third a decision under an acceptance process.
An illustrative row shows Ra ≤ 1.6 µm required, Ra 1.2 µm observed and accepted as the source disposition. A translation should not move accepted into the specification column or create the decision if only numbers exist.
Preserve measurement uncertainty and any agreed decision rule when the source provides them. Refer borderline cases to authorized metrology or quality personnel rather than interpreting an undecided result as compliant.
The final technical-language check is: Can the receiving organization identify who specified, who measured and who accepted? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
Legacy drawing references must remain visible
Many controlled drawings still cite standards predating ISO 21920. New laboratory equipment may use current terminology while the contract retains historical acceptance conditions. A translated drawing must not silently replace its standards references to look modern.
An older ISO 4287 citation in a customer drawing and a new ISO 21920 reference in the supplier’s test sheet may require a technical comparison. The translator should flag the discrepancy, not assume automatic equivalence.
Keep the original references, date and edition in every bilingual citation. Record an engineer-approved comparison separately if one is provided.
At the handover stage verify the following: Does the target preserve the historical basis of the product requirement? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
False friends and domain vocabulary
Surface finish, form, flatness, profile, texture, roughness, waviness, tolerance and polish overlap in everyday language. In technical documents they may refer to different product characteristics, processes or measurement classes. Context determines the correct equivalent.
A source-language term resembling finishing might describe a machining operation rather than the resulting Ra measurement. A general dictionary could suggest a plausible but wrong English noun.
Build a technical termbase containing source phrase, approved target term, parameter context, example document and forbidden substitutes. Verify with domain specialists rather than seeking stylistic variety.
Before signing off, ask the practical review question: Would the chosen English term still identify the same operation, quantity or geometric feature? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
Keep sales prose separate from test findings
A brochure calling a product mirror smooth or premium polished is marketing language. A technical certificate containing a parameter and an instrument result is evidence of something more specific. The two should not be joined into a stronger claim during translation.
A quotation may promise a bright appearance but contain no Ra result. Writing compliant with ISO 21920 would create technical evidence that was never supplied.
Label vendor descriptions as vendor claims, and keep contractual acceptance requirements, laboratory measurements and customer decisions in their distinct places.
The final technical-language check is: Can the reader tell which sentences are promises and which are actual measurements? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
Machine translation needs technical verification
Automated translation or OCR may silently confuse Ra and Rq, remove ≤, change µ to m, alter the decimal separator or shift a leader line. The output can sound natural while being dangerous to manufacture from.
A scanned 0.8 µm requirement may be misread as 0.8 mm; the sentence can remain grammatical. Such mistakes are detected by comparing numerical tokens and graphical symbols, not by proofreading style alone.
Run a character-level symbol and number audit, review diagrams visually and label unreadable source areas rather than guessing. For critical drawing release, use qualified engineering sign-off.
At the handover stage verify the following: Did technical verification occur independently of linguistic editing? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
A supplier query should be answerable
An ambiguous callout needs a narrow engineering question. Asking what roughness means may produce an essay without resolving whether a supplier’s method satisfies the customer’s requirement. A useful query identifies feature, drawing revision, parameter, edition and exact mismatch.
Ask whether the Ra callout at feature B follows the cited operator and whether the laboratory applied the corresponding settings. Include a cropped drawing, report excerpt and target-language draft.
Record the respondent, authority, answer date and any approved change. A translation query must not become an invisible product revision.
Before signing off, ask the practical review question: Is the unresolved issue assigned to the person who can actually decide it? Check the answer against the actual drawing or report, not the translator’s memory. Record who checked it, what evidence was used, and whether any exception remains open. A translation should preserve the original decision boundary, even when the sentence would read more smoothly without that qualification.
A bore callout moves in PDF export
A drawing is translated into English and the annotation has shifted from an internal sealing seat to the neighboring shoulder. The words are grammatically correct, but the manufactured feature now appears to be different. The reviewer overlays the two PDFs, restores the leader and checks all callouts before release. This is why layout quality control must be an engineering task whenever text position identifies physical geometry.
A vendor offers Ra while another offers Rz
Two suppliers compete for a component. One quotation states Ra 0.8 µm; the other gives Rz 3.2 µm. A buyer asks which is better. The translator should not claim the numbers are directly comparable. Preserve each offer, state the different reported parameters and request the same technical acceptance basis from both suppliers or a documented engineering evaluation. This prevents a purchasing decision from being driven by a false conversion.
A warning hides below a table
A report lists several acceptable-looking results, but its footnote says the instrument’s calibration review is pending. Omitting the footnote turns qualified evidence into apparently final evidence. Translate the warning beside the affected results and preserve its open status. The authorized quality team can then decide how to handle the pending record rather than discovering it after the part has shipped.
One scratch remains under review
A finished face meets its stated numerical roughness ceiling, yet a visual inspection identifies a scratch crossing a seal path. The source records the roughness test as accepted and the scratch as unresolved. The English version must reproduce both findings. It must not collapse them into surface fully accepted. Different inspection criteria can produce different open issues on the same component.
A decimal comma breaks an export
A European spreadsheet shows Ra 0,76 µm and Rq 0,94 µm. An English CSV import splits or changes the cells. The safe workflow preserves the native file, verifies numeric cell types, normalizes separators according to a documented style rule and checks the exported PDF against the original. Any uncertainty is flagged before the translated report reaches a buyer.
An old drawing meets a new laboratory
The released drawing cites older texture standards, while the current laboratory workflow is built around ISO 21920. A translator cannot decide that the new measurement is automatically compliant. Both editions, methods and numerical results must be shown accurately. Engineering can approve a comparison procedure or ask for additional evidence; the language file records that decision rather than inventing it.
An inspector measures one part five times
A supplier’s report states five profile traces on one workpiece. The English summary says five products inspected. This changes the declared sample size and can mislead quality control. Correct the translation to separate number of traces from number of physical items. Add the sample ID and position references. The basic lesson is that repetition of measurement is not the same as independent sampling of production.
A termbase prevents recurring errors
A translation team starts with informal synonyms for finish, polish, roughness and texture. Several documents later, suppliers appear to disagree even though their underlying data match. A termbase containing the source term, defined parameter, approved target-language expression and an example drawing reduces needless variation. Technical consistency is more important than literary variety in evidence records.
Frequently asked questions
Is Ra the same as polish?
No. Ra identifies a defined numerical roughness quantity. A polishing operation and its measured results must be established separately.
Can Rz be converted to Ra with one universal ratio?
No. Any comparison depends on actual profile characteristics, methods and definitions. Request engineering evaluation or suitable measurements.
What if the source does not identify a filter?
Record that the setting is not shown. Do not invent a laboratory default in the target copy.
Is an Ra result enough to approve a shipment?
Not necessarily. Acceptance can depend on scope, sampling, other requirements, decision rules and authorization.
Should a translator update old ISO citations?
No. Changing the cited edition is a technical document change requiring approval.
Can a scan be trusted without symbol review?
No. A missing micro sign, comparison operator or arrowhead can change a machining instruction.
Are three readings equivalent to three samples?
Not necessarily. The source must distinguish readings, positions, specimens and lots.
Who can approve a disputed measurement?
The authorized engineering or quality representative under the applicable contract and method.
Does texture describe overall product safety?
No. Surface texture evidence applies to specified characteristics, not every possible performance or safety property.
What is the best translation handover?
A controlled bilingual file containing the source reference, terminology record, numeric check, unresolved questions and approval status.
Does a smoother number always improve the design?
No. Functional surface requirements may depend on direction, lubrication, seals, coating or other design conditions.
What should students learn from these examples?
Symbols, units, qualifiers, evidence types and decision verbs can matter more than decorative language in technical communication.
Publication and review checklist
Identify the document and revision; check ISO edition references; protect parameter symbols and µm units; independently verify decimals and inequality marks; ensure callouts remain attached to the same feature; preserve the original measurement arrangements and sampling scope; separate requirements from results and dispositions; retain any open issue; request engineering approval for actual technical changes; and deliver a controlled translation that points readers back to the source record. This checklist is educational and does not replace the licensed standards or contractual inspection plan.
Authoritative sources and learning routes
Official standard scopes: ISO 21920-1:2021, ISO 21920-2:2021, and ISO 21920-3:2021. This case-focused article complements the established technical-drawings translation architecture, the Vocabulary Learning Hub and How English Works. It does not supersede their broader learning coverage.