applying-iconic-linkage-and-consistency

name	applying-iconic-linkage-and-consistency
description	Translate recurring, semantically identical information with one uniform target-language construction (iconic linkage), and scale that consistency through controlled language, style guides and translation memory where it fits.
kind	skill
status	ready
provenance	{"principles":["P013","P021","P026","P044","P074","P075","P134"],"claims":["C00336","C00343","C00347","C00419","C00422","C00483","C00491","C00505","C00510","C00522","C00525","C00529"],"evidence":["E00317","E00324","E00328","E00392","E00395","E00452","E00459","E00473"],"source_anchors":[]}

Applying Iconic Linkage and Consistency

Purpose

This skill guides the translator to translate recurring, semantically identical information with one uniform target-language construction (iconic linkage), and scale that consistency through controlled language, style guides and translation memory where it fits. It advises on the decision; it does not produce the final translation, override the client's brief, or sign off safety-critical or legally-mandated content — those are handed back to the translator and the commissioner.

When to use

• The translated or instructional guide contains recurring equivalent procedural information.
• Equivalent procedural information recurs across a technical document.
• Applying iconic linkage at scale or evaluating its effect.
• Instructional or technical text contains repeated equivalent concepts or procedures.
• Equivalent instructions recur in user guides.
• A translation workflow needs reuse, consistency, lower cost, or broader standardisation.
• the same information recurs across a text with varied wording.

Procedure

1. Treat the main study as empirical support that iconic linkage can improve speed, errors, completion, recall, satisfaction, clarity, and learning. (P013)
2. Apply iconic linkage by expressing recurring semantically identical information with the same target-language construction and preserving latent repetition. (P021)
3. Introduce iconic linkage with test materials that contain suitably spaced recurrence, a concise style guide, and translation-memory support. (P026)
4. Use iconic linkage only where recurring information makes standardisation practical, and treat it as one cognitive strategy among others. (P044)
5. Do not assume consistency is disruptive; inconsistent instruction phrasing may be more harmful than repeated structures. (P074)
6. Scale consistency through controlled language, style guides, translation memory, and improved semantic-match tooling. (P075)
7. Apply Iconic Linkage: when the source expresses the same information several times with slightly different wording, pick one single translation and reuse it throughout, because doing so cuts the reader's cognitive effort, improves predictability and learning, looks consistent and professional, and makes translation memory more effective for pivot or relay translations. (P134)
8. Emit recommendations highest-impact first, in the format under Output, flagging where a draft or plan departs from the principles above.

Inputs

• The document or excerpt under translation (or its type) and the target-text function.
• The audience, their tasks and prior knowledge, and how the text is used and distributed.
• The translation brief, any client style guide, mandated terminology, and the constraints in force (deadline, format, space, safety/legal status).

Output

Per recommendation: name the applicable principle(s), tie the advice to the audience, brief and target-text function, state the trade-off or residual uncertainty, and end with a concrete next step. Order recommendations highest-impact first. The advisor never delivers the translation or makes the client's commercial or final linguistic decision — that is handed back to the translator and the commissioner.

References

See ../../references/technical-translation-principles-index.md for the full principle catalogue and ../../references/technical-translation-evidence-notes.md for grounding notes. For adjacent concerns, see the sibling skills: analyzing-audience-brief-and-skopos, selecting-translation-strategy-and-procedures, grounding-translation-in-reader-cognition, handling-terminology-units-and-nomenclature, matching-document-type-and-genre, designing-document-structure-and-presentation, planning-usability-evaluations, running-and-analyzing-usability-studies, assuring-quality-safety-and-practice.

Provenance

Derived from P013, P021, P026, P044, P074, P075, P134, grounded in Jody Byrne's Technical Translation: Usability Strategies for Translating Technical Documentation (2006) and Scientific and Technical Translation Explained (2012) (distillation-only). The frontmatter provenance block lists the exact principle, claim, and evidence ids, which resolve into principles/principles.yaml, analysis/claims.jsonl, and evidence/evidence-records.yaml.