Cross-References, Definitions and Links in Translation

How to translate cross-references without losing the reader’s route

How do you translate a document without breaking its cross-references, definitions, footnotes, figures, tables and links? Accurate document translation preserves more than the meaning of each sentence: it keeps the relationships that tell readers where to find an explanation, which defined term governs a clause, which table supports a statement, and which version of a referenced passage is authoritative. This complete guide explains cross-reference translation, multilingual document navigation, translated footnotes, section-number changes, citation pointers and link validation as one connected meaning problem.

The hidden difficulty is that a sentence may be correct in isolation and still be wrong in the finished translated document. ‘See Figure 4’ is misleading if the translated edition contains the relevant chart as Figure 5. A phrase that refers to a specific defined term may lose its meaning if the termbase maps it to a different concept. A translated link can send a reader to an unrelated page, an unavailable language edition or an outdated procedure. The reader experiences these problems as factual or procedural errors even when every sentence has been carefully proofread.

If you need to translate a technical manual, multilingual report, website, book, academic paper, accessible PDF or help centre, begin with a document-relationship map. Identify every anchor and destination, determine what the reference means, preserve stable identifiers separately from displayed labels, regenerate target-language numbering where appropriate, test the actual reader journey, and check changes after publication. You will learn a repeatable method, common failure modes, worked diagnostics and transfer exercises that explain how accurate words become a usable translated information system.

This chapter is a world-facing translation method, not a platform-specific software tutorial or a substitute for the existing guides on scholarly citations, web accessibility, legal defined terms or English cross-reference constructions. Its distinctive task is to preserve the reader’s ability to move from a statement to the exact explanation, condition, illustration, evidence or action that statement depends upon.

A document relationship can carry a real instruction. ‘Complete the checks in Section 7 before activating the device’ is not simply a navigational convenience. If Section 7 becomes Section 8 in the translated edition and the pointer still opens the wrong section, the translation has changed what a reader is asked to do. The failure lives at the boundary between language and document structure; it must be caught by checking both.

The hidden problem: a translation can preserve sentences and still lose its logic

A long document is not a bag of independent paragraphs. An instruction may depend on an earlier definition; a chart may qualify a claim in the discussion; a footnote may explain why a method was excluded; and a hyperlink may lead to the procedure necessary to complete an action. These relationships are part of what the document means. When translation changes order, word length, section boundaries or page layout, the relationships can be severed even though local syntax remains correct.

Consider a fictional report that states, ‘The threshold in Table 3 applies to approved samples only.’ The target language correctly explains ‘threshold’ and ‘approved samples,’ but a revised layout turns Table 3 into a maintenance timetable. The target reader may now use an irrelevant limit. That is not merely a hyperlink defect: it changes the conditions under which the report’s result is valid. The right fix requires identifying the intended table, not adjusting the wording until the sentence sounds better.

The same danger appears in documents without digital links. A printed booklet may say ‘as defined above’; an audio guide may say ‘in the next section’; a screen reader may announce ‘learn more’ without context; and a translated caption may describe the wrong panel of a figure. We should distinguish the reader’s semantic destination from the notation used to reach it. The former must remain stable as the translation evolves; the latter may need to change.

The document relationship graph: preserve nodes, edges, conditions and journeys

Represent the source as a graph of content objects. A node might be a sentence, subsection, definition, figure, table, footnote, appendix, heading, external page, bibliography entry or form step. An edge records a relationship: defines, refers to, supports, qualifies, warns, illustrates, requires, cites, follows or supersedes. A translated edition does not need identical page numbers or visual order; it does need an equivalent set of reader-relevant relationships.

The simplest ledger has seven columns: source segment identifier, source display label, relationship type, true destination, target edition destination, condition or scope, and validation result. Add a risk rating when a broken relationship could alter a safety instruction, requirement, financial disclosure or research conclusion. Stable technical identifiers should not be confused with human-readable numbers: a generated target heading may be Section 8 even though its database key remains section-safety-check.

There are three different tests. The label test asks whether ‘Figure 6’ is the right label in the target edition. The resolution test asks whether that label points to the intended target object. The comprehension test asks whether readers understand why they should follow it, and whether the destination still gives the information promised. Passing only the first or second is insufficient. A functioning link can lead to an unrelated section, and a correct destination can be described by a misleading link label.

The fourth test is temporal: after a source revision or translation update, does the relationship still hold? When an appendix is split, one inherited pointer may need to become two. When a caution becomes a mandatory requirement, its links must follow the authoritative version. A reader should not need to guess which edition controls a consequence.

Thirty-six relationship mechanisms translators must protect

Mechanism 1: Stable anchor

An element’s durable identifier is different from the heading readers see. Consider this source-document situation: a translated heading changes but the underlying anchor should still resolve to that element. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: a translator rewrites a fragment identifier to match a translated title even though the site preserves the original ID. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Protect the underlying ID unless the publishing system explicitly regenerates it and rewrites all inbound references. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Can the link resolve to the same logical section after the heading is changed? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 2: Generated section number

Section labels are produced by document order and style rules, not necessarily authored text. Consider this source-document situation: a section formerly shown as 4.2 becomes 5.1 after an introductory chapter is added. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: a hard-coded 4.2 remains in a translated paragraph while the destination now displays 5.1. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Regenerate or update visible labels from the target edition’s structure. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Does the reference name the actual destination section in the current target build? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 3: Figure call

The text tells a reader which visual object explains a claim. Consider this source-document situation: a relocated diagram moves from Figure 3 to Figure 5 in a translated handbook. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: the prose still directs readers to Figure 3, now showing a different mechanism. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Bind the reference to a stable figure object and resolve its displayed number after layout. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Does the reader reach the correct diagram and panel? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 4: Table call

A table supplies values, categories or conditions needed to interpret a claim. Consider this source-document situation: a passage refers to the limits in Table 2 for a particular sample class. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: a reordered translation points Table 2 to a staffing calendar instead of limits. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Verify the linked table’s content and applicable row or column in the target. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Could someone act on a wrong numeric value after following the link? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 5: Caption dependency

A caption describes and sometimes qualifies the content of a visual. Consider this source-document situation: a chart caption identifies that data exclude a provisional interval. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: a fluent translated caption omits the exclusion while the chart itself is unchanged. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Carry the scope and exclusion alongside the caption and body reference. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Would a reader know the chart’s limitations without the source? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 6: Alternative text

A nonvisual description provides access to essential visual information. Consider this source-document situation: a diagram shows three stages joined by directional arrows. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: the alt text is translated as a decorative label with no sequence or dependencies. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Describe the information conveyed, and avoid inventing detail unseen in the visual. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Can a nonvisual reader recover the relationship the diagram communicates? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 7: Table header association

Cell meaning depends on its associated header, unit and grouping. Consider this source-document situation: a table repeats ‘Current’ under two headings, Actual and Planned. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: the target reads ‘Current’ without indicating which heading governs the value. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Preserve header semantics and ensure translated heading associations survive rendering. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Which header would a screen reader announce for the disputed cell? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 8: Footnote marker

A superscript or note reference directs a reader to a qualifier. Consider this source-document situation: a methodology sentence contains note 7 describing a sampling exception. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: note numbers are reordered but the marker still opens a different editorial remark. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Keep a stable note link and regenerate visible note numbers after composition. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Does the note explain the exact statement to which its marker is attached? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 9: Endnote sequence

Notes at the end of a chapter may be numbered by chapter rather than book. Consider this source-document situation: an imported chapter causes endnotes to be renumbered. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: a copied numeral points to an endnote from the previous chapter. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Resolve note identifiers in the scope of the target chapter or work. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Is the visible numbering unique and correctly scoped? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 10: Citation pointer

A claim cites a particular evidence source, not an arbitrary bibliography item. Consider this source-document situation: a paragraph cites study A for an observation and study B for a proposed explanation. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: a switched target citation makes B appear to support the observation. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Preserve claim-to-source alignment and citation identifiers through translation. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Does the cited source support the actual proposition after translation? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 11: Bibliography record

A reference describes a distinct publication or edition. Consider this source-document situation: a book appears both in its original title and in a translated edition. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: a translator silently substitutes the new edition’s page range without consulting it. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Separate identification of the original work from any actual consulted translated edition. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Can the reader locate the work and edition cited? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 12: Defined-term link

A document may assign a precise technical meaning to a capitalised term. Consider this source-document situation: the word ‘Service’ is defined as one particular contractual facility. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: a target uses the ordinary word for service and drops the definition pointer. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Preserve the defined concept and point every governed occurrence to the correct definition. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Does the term used in the clause have the same stipulated meaning? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 13: Definition scope

The same expression may be defined differently in separate sections or products. Consider this source-document situation: two appendices use the term ‘approved item’ under distinct criteria. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: a global glossary forces one definition across both contexts. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Carry the scope of each definition, including section and edition limits. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Which definition governs this particular occurrence? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 14: Inflected term

A defined concept can appear with plural, case or gender morphology. Consider this source-document situation: a defined component name occurs inside an inflected target-language phrase. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: the target treats the changed inflection as a different entity or hides the definition. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Use a natural grammatical form while retaining the term’s concept identifier. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Can a reviewer trace every morphological variant to the same concept? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 15: Internal hyperlink

A link moves readers to a location inside the current information product. Consider this source-document situation: a help article links from troubleshooting text to a reset step. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: the target link opens a general home page after translation. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Map the source destination to the corresponding translated step. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Does following the link perform the reader’s intended navigation? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 16: External hyperlink

A destination outside the document may be language-independent or locale-specific. Consider this source-document situation: an article links to a safety data record hosted by a third party. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: a translator invents an untranslated guessed URL that returns an unrelated page. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Verify the authoritative destination and whether a legitimate target-language equivalent exists. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Is the destination both accessible and equivalent in authority? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 17: Relative URL

A path is interpreted relative to a specific base address. Consider this source-document situation: a manual refers to ../reference/calibration.html from a nested chapter. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: the translated chapter moves directories and the relative path now points elsewhere. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Resolve the path from the actual target document location. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: What complete URL results when the target browser follows the relative path? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 18: Fragment target

A hash fragment jumps to a particular block within a page. Consider this source-document situation: a link should open the ‘Before you begin’ subsection. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: the file loads but the fragment does not exist in the translated page. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Test both page retrieval and fragment resolution. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Does the page scroll or focus to the expected destination? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 19: Language alternate

Readers may need a matching translated edition rather than the source language. Consider this source-document situation: the help centre has parallel English and French steps with different routes. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: a translated label points to an English homepage instead of the equivalent procedure. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Use a verified locale mapping and fall back transparently if the target is unavailable. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Does the target reader receive equivalent content in the expected language? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 20: Canonical relation

A search system’s canonical URL is not necessarily the link a reader should follow. Consider this source-document situation: a multilingual site distinguishes canonical search signals from language-navigation links. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: a translator rewrites the canonical to a guessed translation URL without publication authority. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Leave SEO metadata to authorised site controls and verify that user-facing links resolve correctly. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Are navigation and canonical semantics treated as different responsibilities? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 21: Versioned link

A referenced procedure may be valid only for one product release. Consider this source-document situation: a notice for version 4 cites a calibration step in the version 4 manual. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: the translated note routes to version 5 where the limits changed. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Bind the reference to the applicable content version, not just a page title. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Would the target reader apply the correct version-specific instruction? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 22: Circular reference

Two passages can send readers back and forth without a usable destination. Consider this source-document situation: section A says see Section B and Section B says return to A without stating the needed rule. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: the target makes a loop harder to notice with changed numbering. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Flag circular navigation and preserve the source’s limitations without inventing a missing rule. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Can a reader reach the promised answer in a finite number of steps? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 23: Multi-document dependency

A document relies on an annex or companion document for an operative condition. Consider this source-document situation: a policy statement says a test method is specified in an external annex. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: the target annex is absent while the link suggests the rule is complete. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Mark the unavailable dependency and provide an authorised route to the applicable original. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Can the reader find the condition required to apply the sentence? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 24: Reused content

A common warning can be inserted into multiple manuals using a content reference. Consider this source-document situation: one warning block is reused in two products with different preceding steps. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: a translation adds context that is true for only one product. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Keep reusable content context-neutral or scope each variant explicitly. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Does the same text remain accurate everywhere it appears? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 25: Prerequisite edge

One instruction must be completed before another is allowed. Consider this source-document situation: a setup step says to complete the pressure check before opening a valve. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: a renumbered link sends the reader directly to the opening step. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Preserve the ‘requires first’ relationship independently of section number. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: What prerequisite would the translated journey actually show? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 26: Warning linkage

A warning may qualify an action displayed elsewhere. Consider this source-document situation: a procedure points to a hazard table that limits allowed operating conditions. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: the target procedure still works as a link but bypasses the hazard table. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Maintain and test the warning-to-action relationship. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Would a careful reader encounter the hazard information before the action? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 27: Appendix scope

An appendix can be normative, informative, optional or edition-specific. Consider this source-document situation: a manual identifies Appendix A as required test criteria and Appendix B as background. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: the target swaps or weakens those roles during reordering. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Preserve the role and section identity of every appendix reference. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Which annex supplies mandatory criteria in the translated edition? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 28: Index entry

A back-of-book index connects a concept to its occurrences. Consider this source-document situation: the source indexes ‘calibration interval’ under three locations. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: the target reuses source page numbers although text has reflowed. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Regenerate index locators against the target composition. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Can a reader find all intended occurrences in the finished format? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 29: Contents entry

The table of contents is a map of the target work’s hierarchy. Consider this source-document situation: a chapter splits into two sections after localisation. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: the table of contents retains an obsolete single-entry structure. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Generate the contents from the final target headings and stable hierarchy. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Does every entry open the claimed section? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 30: Glossary back-link

A short expression may send readers to a longer concept explanation. Consider this source-document situation: the word ‘nominal’ is glossed at first use and referenced later. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: the later link now opens an unrelated alphabetical glossary entry. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Bind terms to concepts and actual target-language entries. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Does the reader retrieve the intended concept rather than a similar word? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 31: Page-number locator

Printed page numbers are properties of a particular layout. Consider this source-document situation: a print instruction says see the examples on page 46. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: the translated edition changes pagination and page 46 contains unrelated material. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Regenerate page locators or use stable structural references for reflowable editions. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Does the locator match the exact published PDF or printed edition? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 32: Language tag

A language identifier informs pronunciation, speech synthesis and linguistic processing. Consider this source-document situation: a multilingual page quotes a sentence in a third language. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: the quotation is wrapped in the wrong document language tag. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Mark the correct language on the quoted span using supported technology. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Would a screen reader use the intended pronunciation rules? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 33: Link-label intent

Link text needs to tell readers what destination to expect. Consider this source-document situation: a procedure links to the form for reporting a defect. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: the translated link is reduced to ‘click here’ without context. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Name the target action or document in link text and verify its accuracy. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Could someone choose the link without guessing? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 34: Diagram callout

A diagram label and a passage may refer to the same numbered part. Consider this source-document situation: text instructs a user to inspect part C shown in the illustration. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: the translated legend changes C to D in prose but not in the illustration. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Align prose, embedded art, legend and alt text as one translation unit. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Does the letter point to the physically correct component? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 35: Form dependency

A form field may link to its explanation or condition. Consider this source-document situation: the consent box refers users to the retention schedule in Section 6. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: the target version points to a marketing FAQ rather than the schedule. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Preserve both the condition and the form-field reference. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Does the linked information support an informed decision? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

Mechanism 36: Translation-unit boundary

A sentence-level segment may detach ‘this table’ from its antecedent. Consider this source-document situation: a translation memory segment starts halfway through a paragraph referring to a prior illustration. The central translation question is not just which words sound natural. It is which object, condition, edition or reader action this piece of text connects to. Draw that connection before editing any target-language label or identifier.

An instructive failure looks like this: the translator assumes the wrong illustration because context is missing. Such a defect often survives ordinary bilingual proofreading because the local sentence can be grammatical and the surrounding content may look familiar. The error becomes visible only when the reviewer follows the actual reference or reconstructs how the reader will use it.

Repair: Provide contextual screenshots, source IDs or neighbouring segments. Make the repair on the new translation and its own structural metadata; do not edit existing canonical material just to make one target string fit. When the destination lacks an authorised translation, name that limitation clearly and use the original authoritative source rather than fabricate a new page or falsely claim equivalent language coverage.

Diagnostic: Can the reviewer identify the antecedent from the complete document? Require the reviewer to record both an expected result and the observed result in the generated target edition. If they differ, the sentence has failed a relational meaning check even if the anchor opens a page. Retest after reflow, export or release updates, because references can break after translation has already passed a sentence-level review.

The twenty-stage reference-preserving translation method

Stage 1: Clarify the reader task

Ask whether the translation supports browsing, learning, legal review, maintenance, scientific interpretation or a time-sensitive action. The reason is concrete: a reference that governs a safety prerequisite receives a stricter release gate than a casual ‘see also’. Decide who owns this stage, which artefact proves completion and which failure prevents publication. A workflow without named evidence tends to collapse into a final visual scan, which cannot show whether references have been updated throughout a document.

For a meaningful pass, inspect at least one actual source-and-target reference in context, not only a screenshot of a heading. Record the source object ID, target object ID, displayed label, visible link wording, expected destination, observed destination and whether a reader obtains the promised information. Repeat after any relevant revision; previously correct links can become wrong when an upstream object moves.

Stage 2: Inventory content objects

List headings, figures, tables, notes, definitions, hyperlinks, appendices, citations, labels and reused fragments. The reason is concrete: unlisted structural objects are invisible to translation QA. Decide who owns this stage, which artefact proves completion and which failure prevents publication. A workflow without named evidence tends to collapse into a final visual scan, which cannot show whether references have been updated throughout a document.

Stage 3: Capture stable identifiers

Save technical IDs and object types separately from visible labels such as Figure 2 or Section 4. The reason is concrete: a target edition may renumber a visible label while preserving the same semantic object. Decide who owns this stage, which artefact proves completion and which failure prevents publication. A workflow without named evidence tends to collapse into a final visual scan, which cannot show whether references have been updated throughout a document.

Stage 4: Build the source relationship graph

Record each ‘defines’, ‘qualifies’, ‘supports’, ‘requires’, ‘illustrates’, ‘continues’ or ‘supersedes’ edge. The reason is concrete: the graph reveals when an apparently minor link carries an essential condition. Decide who owns this stage, which artefact proves completion and which failure prevents publication. A workflow without named evidence tends to collapse into a final visual scan, which cannot show whether references have been updated throughout a document.

Stage 5: Identify authority and edition

For every destination, specify the document version and responsible publisher. The reason is concrete: a link to an obsolete but similar page is not equivalent to the authoritative edition. Decide who owns this stage, which artefact proves completion and which failure prevents publication. A workflow without named evidence tends to collapse into a final visual scan, which cannot show whether references have been updated throughout a document.

Stage 6: Separate translatable text from protected tokens

Determine which labels are prose and which values are identifiers, commands, codes or external handles. The reason is concrete: a translated fragment ID may prevent software from finding its target. Decide who owns this stage, which artefact proves completion and which failure prevents publication. A workflow without named evidence tends to collapse into a final visual scan, which cannot show whether references have been updated throughout a document.

Stage 7: Resolve source ambiguity

Ask which ‘this table’ or ‘above example’ is meant when the source gives insufficient context. The reason is concrete: the source author may need to clarify before the translator can preserve the correct edge. Decide who owns this stage, which artefact proves completion and which failure prevents publication. A workflow without named evidence tends to collapse into a final visual scan, which cannot show whether references have been updated throughout a document.

Stage 8: Plan target content order

Record expected chapter splits, figure moves, glossary sorting and layout changes. The reason is concrete: structural edits change displayed numbering but should not change underlying relationships. Decide who owns this stage, which artefact proves completion and which failure prevents publication. A workflow without named evidence tends to collapse into a final visual scan, which cannot show whether references have been updated throughout a document.

Stage 9: Define locale and fallback policy

Choose how a reader reaches an untranslated or unavailable target. The reason is concrete: a silent fallback to an unrelated homepage misrepresents content equivalence. Decide who owns this stage, which artefact proves completion and which failure prevents publication. A workflow without named evidence tends to collapse into a final visual scan, which cannot show whether references have been updated throughout a document.

Stage 10: Draft semantic text

Translate the instruction and destination description naturally, with its relation intact. The reason is concrete: literal reproduction of a source label is not required when the target edition differs. Decide who owns this stage, which artefact proves completion and which failure prevents publication. A workflow without named evidence tends to collapse into a final visual scan, which cannot show whether references have been updated throughout a document.

Stage 11: Preserve object binding

Attach translated text to the correct target ID and reference type. The reason is concrete: a link can have perfect grammar but the wrong destination. Decide who owns this stage, which artefact proves completion and which failure prevents publication. A workflow without named evidence tends to collapse into a final visual scan, which cannot show whether references have been updated throughout a document.

Stage 12: Regenerate displayed labels

Use document tools to update figures, tables, chapters, notes and index locators. The reason is concrete: hard-coded numbers are brittle after reflow and insertion. Decide who owns this stage, which artefact proves completion and which failure prevents publication. A workflow without named evidence tends to collapse into a final visual scan, which cannot show whether references have been updated throughout a document.

Stage 13: Validate link resolution

Check full URL, relative path, fragment ID, redirect and error responses. The reason is concrete: a 200 response for a page does not prove the intended subsection exists. Decide who owns this stage, which artefact proves completion and which failure prevents publication. A workflow without named evidence tends to collapse into a final visual scan, which cannot show whether references have been updated throughout a document.

Stage 14: Validate destination meaning

Open the referenced object and confirm its subject, scope, edition and claimed function. The reason is concrete: a link to a correct-looking title can still change the operative instruction. Decide who owns this stage, which artefact proves completion and which failure prevents publication. A workflow without named evidence tends to collapse into a final visual scan, which cannot show whether references have been updated throughout a document.

Stage 15: Check accessibility

Verify headings, meaningful link text, language tags, table headers, note relationships and keyboard reading order. The reason is concrete: a visually correct link may be unusable or ambiguous in assistive technology. Decide who owns this stage, which artefact proves completion and which failure prevents publication. A workflow without named evidence tends to collapse into a final visual scan, which cannot show whether references have been updated throughout a document.

Stage 16: Run bilingual semantic review

Compare source claims, target claims and the mapped object relationships. The reason is concrete: language accuracy and structural resolution need independent checks. Decide who owns this stage, which artefact proves completion and which failure prevents publication. A workflow without named evidence tends to collapse into a final visual scan, which cannot show whether references have been updated throughout a document.

Stage 17: Run monolingual journey tests

Ask a reader who sees only the target edition to find definitions, prerequisites and evidence. The reason is concrete: the final reader cannot rely on a translator’s memory of the source. Decide who owns this stage, which artefact proves completion and which failure prevents publication. A workflow without named evidence tends to collapse into a final visual scan, which cannot show whether references have been updated throughout a document.

Stage 18: Stress-test alternate formats

Export PDF, HTML, print and mobile views and rerun high-risk references. The reason is concrete: an anchor or page number can succeed in one format and fail in another. Decide who owns this stage, which artefact proves completion and which failure prevents publication. A workflow without named evidence tends to collapse into a final visual scan, which cannot show whether references have been updated throughout a document.

Stage 19: Review change dependencies

When source or target objects change, identify every incoming reference and linked translation segment. The reason is concrete: an updated figure may invalidate several previously accepted claims. Decide who owns this stage, which artefact proves completion and which failure prevents publication. A workflow without named evidence tends to collapse into a final visual scan, which cannot show whether references have been updated throughout a document.

Stage 20: Record acceptance and maintenance

Save a dated manifest of source version, target version, reviewer, exceptions and tests. The reason is concrete: a clean first release is insufficient if later edits silently sever the graph. Decide who owns this stage, which artefact proves completion and which failure prevents publication. A workflow without named evidence tends to collapse into a final visual scan, which cannot show whether references have been updated throughout a document.

Thirty concrete failure modes: what an error actually does to a reader

An effective taxonomy identifies where meaning breaks. These failures range from a visible wrong number to a silent change in a procedural dependency. Each has a detectable signature, a particular correction and a reader consequence. They are not interchangeable: re-rendering a table of contents cannot repair a wrong definition, and updating a page number cannot validate whether the target passage still supports the claim.

Failure 1: Stale figure number

The source asks readers to examine Figure 2, while the target edition labels the intended visual Figure 4. Consequence: a reader consults the wrong figure and may learn a different mechanism. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Regenerate the reference from the target figure object and verify the caption. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 2: Copied page number

A translated print edition refers to source page 67 even though the relevant text moved. Consequence: the reader searches an unrelated page and may abandon an important qualification. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Update the target pagination or use a structural reference. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 3: Wrong cross-document version

An operating procedure for release A links to requirements for release B. Consequence: the target can appear valid while instructing the wrong action. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Bind the link to the correct release-specific document. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 4: Orphaned fragment

A link opens the proper web page but not the requested subsection. Consequence: the reader assumes the general page replaces a precise condition. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Verify the hash fragment and update the anchor mapping. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 5: Translated identifier

An editor translates an anchor key used by a CMS without updating inbound links. Consequence: existing references no longer resolve. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Keep immutable IDs stable or coordinate an authorised migration. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 6: False translation alternate

A language switch routes to an unrelated home page because the specific translated article is absent. Consequence: the reader believes the promised explanation exists in the chosen language. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Offer a transparent unavailable-edition fallback. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 7: Circular note chain

A note sends the reader to another note that sends them back without supplying the answer. Consequence: the cited condition cannot be found. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Record the unresolved source loop and request an editorial resolution. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 8: Reassigned note marker

A note is renumbered during layout but the body marker retains the old number. Consequence: a qualification attaches to the wrong assertion. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Link by note object and regenerate numbering. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 9: Caption scope lost

A translated chart caption drops a restriction such as ‘experimental conditions only’. Consequence: readers generalise the chart beyond the source. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Restore the restriction and recheck body claims. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 10: Misidentified table column

A column heading is associated with an adjacent value after translation wraps. Consequence: a reader takes a planned figure to be an actual result. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Validate header-to-cell associations and units. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 11: Alt text disconnected

A diagram’s translated alternative text describes another illustration. Consequence: nonvisual readers receive a contradictory account. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Align alt text with the final actual visual. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 12: Index page drift

A translated index keeps old page locators after text expansion. Consequence: the reader cannot find a term in print. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Regenerate the index from the target layout. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 13: Conflicting glossary sense

A short label links to a similarly spelled but different concept. Consequence: the reader applies the wrong definition. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Use concept IDs and scope-sensitive term mappings. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 14: Definition scope lost

The same term has different meanings in two annexes, but target glossary merges them. Consequence: a requirement expands or narrows unintentionally. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Retain local definition scope and point to correct annex. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 15: Condition separated

A linked prerequisite is moved beneath the action it restricts. Consequence: the reader may act before seeing a condition. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Preserve action-to-prerequisite order or prominent warning. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 16: Authority substituted

An external public page replaces a versioned official specification. Consequence: the reader assumes an informal summary has normative force. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Link to the applicable authority and identify commentary as commentary. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 17: Bibliography record mismatch

The target citation points to an edition not actually used. Consequence: readers cannot verify the quoted page or conclusion. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Preserve exact consulted edition and page span. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 18: Automated title drift

A target heading is edited, but imported link labels remain old. Consequence: navigation text promises a destination that has changed. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Regenerate labels and test semantic destination. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 19: Broken relative path

A file is moved one folder deeper and its relative link still resolves from the old base. Consequence: the link returns a different resource or error. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Resolve full URLs from the actual published target location. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 20: Invisible keyboard route

A visual click target works but is not reachable by keyboard or has no useful accessible name. Consequence: some readers cannot follow the promised cross-reference. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Check keyboard reachability and link-purpose context. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 21: Quoted term normalised

A deliberately defined capitalised term becomes an ordinary expression. Consequence: the target loses a condition built into its formal definition. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Preserve the defined concept and link to the governing definition. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 22: Hidden transclusion mismatch

A reused warning is translated with details true for only one product. Consequence: another product displays inaccurate advice. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Scope reused strings or maintain validated variants. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 23: Table call after reorder

A chart and table exchange positions, but nearby references remain hard-coded. Consequence: the reader gets a logically different illustration. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Rebind every call to its intended object ID. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 24: Live-source revision

A linked page is updated after the translated paragraph was approved. Consequence: the destination no longer supports the statement. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Trigger dependency review when linked source versions change. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 25: Citation key collision

Two imported references share the same local key and resolve unpredictably. Consequence: one assertion may acquire the wrong authority. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Ensure identifiers are unique in the relevant scope. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 26: OCR superscript error

A scanned note marker is misread as an exponent or missing digit. Consequence: a scholarly explanation is lost or numeric meaning changes. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Inspect the original visual and reconstruct the note boundary. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 27: Conflated informative annex

A background appendix is portrayed as mandatory criteria. Consequence: an optional discussion becomes an obligation. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Preserve normative versus informative status. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 28: Language tag omission

Embedded foreign-language text is pronounced using the document’s default language. Consequence: screen-reader interpretation may become confusing. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Mark span language correctly in supported output. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 29: Unclear link label

Every destination is described as ‘more information’ in a translated navigation list. Consequence: readers cannot predict where links lead. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Use purpose-bearing labels and context. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Failure 30: Unverified PDF export

Web anchors work but exported PDF bookmarks or internal links point nowhere. Consequence: offline readers cannot complete the journey. The translation may have passed ordinary spelling, grammar and terminology checks, because these do not simulate the reader’s attempt to follow a reference. An accurate local phrase does not excuse a broken dependency that determines how the phrase is interpreted.

Repair and evidence: Test each important relation in the exported PDF itself. Record the expected destination, the observed target object and the test result in the same review log. When the failure involves an unavailable source or unclear authorial intention, stop short of fabricating a destination. Escalate to the content owner and preserve the uncertainty visibly until an authorised correction exists.

Worked diagnostic collection: how a reference changes the meaning of a document

Every scenario below is invented for instruction. Source and target sentences are English paraphrases representing the intended semantic contrast; they are not claimed translations from any particular language. The task for an actual translator is to preserve the connection while choosing an idiomatic construction in the target language and validating the generated output. Each diagnostic describes a concrete reader journey, a misleading rendering, a safer reconstruction and a test.

Worked domain 1: Equipment manuals

A safety prerequisite is embedded in a section call. The relevant source artefact is the maintenance procedure. When the target edition changes language, length or layout, a reader should still reach the object that supplies the condition, definition or evidence. Start by recording the object identity and the intended relationship. Then ask a monolingual reviewer to navigate the published target version without seeing the original.

Diagnostic 1: Equipment manuals, scenario 1

Source assertion: “Before opening the housing, complete the isolation check in Section 6.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “See Section 6 after opening the housing.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Before opening the housing, complete the isolation check in the target edition’s corresponding section.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the linked section actually describe the required check? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 2: Equipment manuals, scenario 2

Source assertion: “The torque value is specified in Table 4 under the dry-fit condition.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “Use the value in Table 4 for all conditions.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Use the dry-fit torque value in the correctly mapped target table.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the target table preserve the dry-fit row and units? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 3: Equipment manuals, scenario 3

Source assertion: “The warning icon in Figure 2 points to the external emergency stop.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The icon points to the ordinary start control.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “The warning refers to the emergency-stop component shown in the corresponding target figure.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Do the translated label and actual illustration identify the same device? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Worked domain 2: Research reports

A claim’s qualification appears outside its immediate sentence. The relevant source artefact is the methods and appendices. When the target edition changes language, length or layout, a reader should still reach the object that supplies the condition, definition or evidence. Start by recording the object identity and the intended relationship. Then ask a monolingual reviewer to navigate the published target version without seeing the original.

Diagnostic 4: Research reports, scenario 1

Source assertion: “The trend in Figure 5 excludes the trial period described in Note 3.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The trend covers every observation period.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “The trend excludes the trial period, as explained by the linked note in the translated edition.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the note preserve the exclusion? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 5: Research reports, scenario 2

Source assertion: “The result uses the adjusted denominator defined in Appendix A.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The result uses the ordinary sample count.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “The result uses the specifically defined adjusted denominator in the corresponding annex.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the translated formula match the intended definition? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 6: Research reports, scenario 3

Source assertion: “See the original analysis in Reference 12 for the treatment of missing observations.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “Reference 12 proves there were no missing observations.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Consult the correctly mapped source for how missing observations were handled.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the cited work actually discuss missing-data treatment? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Worked domain 3: Digital help centres

Language switching and navigational labels create a reader promise. The relevant source artefact is the online support pages. When the target edition changes language, length or layout, a reader should still reach the object that supplies the condition, definition or evidence. Start by recording the object identity and the intended relationship. Then ask a monolingual reviewer to navigate the published target version without seeing the original.

Diagnostic 7: Digital help centres, scenario 1

Source assertion: “For password reset instructions, open the account recovery procedure.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “Open the support homepage.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Open the target-language account recovery procedure when an equivalent edition exists.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the route display the requested procedure? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 8: Digital help centres, scenario 2

Source assertion: “The next step is in the subsection Before you begin.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The next step is on this general documentation page.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Follow the link to the target edition’s Before you begin subsection.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the fragment land on the intended heading? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 9: Digital help centres, scenario 3

Source assertion: “The payment dispute form explains evidence requirements in its help panel.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “Any form will supply the evidence requirements.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Use the verified evidence-requirements panel associated with the dispute form.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Can a reader open the panel and identify its actual rule? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Worked domain 4: Academic books

Footnotes, index entries and reflowed pages preserve the argument trail. The relevant source artefact is the book chapters and notes. When the target edition changes language, length or layout, a reader should still reach the object that supplies the condition, definition or evidence. Start by recording the object identity and the intended relationship. Then ask a monolingual reviewer to navigate the published target version without seeing the original.

Diagnostic 10: Academic books, scenario 1

Source assertion: “The exception to this interpretation is discussed in footnote 18.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “Footnote 18 supports the main claim without exception.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “The mapped note discusses an exception to the interpretation.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the target note qualify the same paragraph? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 11: Academic books, scenario 2

Source assertion: “The definition of narrative voice is on page 42 of this edition.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The definition is on page 42 in every edition.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “In this translated edition, consult the recomputed page or stable section for the definition.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the printed page contain the definition? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 12: Academic books, scenario 3

Source assertion: “Further examples appear under the index entry temporal framing.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “Every indexed entry has exactly the same locations after translation.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Consult the regenerated target-language index entry for temporal framing.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Are the cited target pages correct and complete? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Worked domain 5: Engineering drawings

Labels and drawing coordinates are part of the meaning. The relevant source artefact is the schematics and legends. When the target edition changes language, length or layout, a reader should still reach the object that supplies the condition, definition or evidence. Start by recording the object identity and the intended relationship. Then ask a monolingual reviewer to navigate the published target version without seeing the original.

Diagnostic 13: Engineering drawings, scenario 1

Source assertion: “The circuit breaker is marked B7 in the diagram.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The breaker is marked B1 in the diagram.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “The circuit breaker is identified by the actual B7 label preserved or mapped in the final drawing.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the identifier point to the correct component? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 14: Engineering drawings, scenario 2

Source assertion: “Refer to the upper-right panel for the valve position before step 4.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “Refer to the lower-left panel for the valve position.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Use the corresponding actual panel and position in the translated drawing.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the panel contain the intended valve position? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 15: Engineering drawings, scenario 3

Source assertion: “The shaded area in Figure 3 denotes the excluded measurement region.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The shaded area denotes the approved operating region.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “The shaded area is the excluded measurement region, as defined by the translated legend.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Do body text and legend agree? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Worked domain 6: Policy documents

Cross-document scope and annex status govern interpretation. The relevant source artefact is the policy and annex. When the target edition changes language, length or layout, a reader should still reach the object that supplies the condition, definition or evidence. Start by recording the object identity and the intended relationship. Then ask a monolingual reviewer to navigate the published target version without seeing the original.

Diagnostic 16: Policy documents, scenario 1

Source assertion: “The procedure applies only to the exceptions listed in Annex B.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “All exceptions from every annex apply.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Only the exceptions in the correctly identified Annex B govern this procedure.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Is Annex B the operative exception set? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 17: Policy documents, scenario 2

Source assertion: “The advisory examples in Appendix C are informative, not mandatory.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The examples in Appendix C are compulsory requirements.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Appendix C illustrates possible applications and does not itself impose mandatory requirements.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the translated appendix preserve its stated role? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 18: Policy documents, scenario 3

Source assertion: “For approval authority, consult the current delegation schedule.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “Any historical delegation schedule proves approval authority.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Consult the applicable current delegation schedule identified in the translated policy.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the link reach a valid dated schedule? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Worked domain 7: Museum catalogues

Object labels depend on catalogue notes and image panels. The relevant source artefact is the exhibition captions. When the target edition changes language, length or layout, a reader should still reach the object that supplies the condition, definition or evidence. Start by recording the object identity and the intended relationship. Then ask a monolingual reviewer to navigate the published target version without seeing the original.

Diagnostic 19: Museum catalogues, scenario 1

Source assertion: “The attribution is provisional; see catalogue note 7.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The artist’s identity is confirmed.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “The artist attribution is provisional and explained in the correctly mapped catalogue note.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the note preserve the reason for uncertainty? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 20: Museum catalogues, scenario 2

Source assertion: “The reverse of the object is pictured in panel C.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The reverse is shown in panel A.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “The reverse is shown in the corresponding panel of the translated display.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Is the referenced image actually the reverse? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 21: Museum catalogues, scenario 3

Source assertion: “The provenance note uses the meaning of acquisition as defined in the catalogue glossary.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “Acquisition has whatever everyday meaning the reader prefers.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Use the catalogue’s stated sense of acquisition and the associated glossary entry.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the target glossary distinguish acquisition from custody? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Worked domain 8: Software API guides

Code tokens, anchors and prose have different translation rules. The relevant source artefact is the API specification. When the target edition changes language, length or layout, a reader should still reach the object that supplies the condition, definition or evidence. Start by recording the object identity and the intended relationship. Then ask a monolingual reviewer to navigate the published target version without seeing the original.

Diagnostic 22: Software API guides, scenario 1

Source assertion: “The request parameter page_size must match the documented range in Table 2.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “Translate page_size into a different parameter name.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Preserve page_size as the API identifier and point to the correct translated range table.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the code example still use the valid parameter key? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 23: Software API guides, scenario 2

Source assertion: “For the error code E409, see the conflict resolution section.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “Follow the section on successful responses for E409.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Link E409 to the actual conflict resolution section in the target manual.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the destination describe the code’s recovery path? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 24: Software API guides, scenario 3

Source assertion: “The schema field is deprecated in version 3; consult the version 2 appendix for legacy cases.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The field is valid in all releases.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Mark the version 3 deprecation and preserve the legacy-version appendix link.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the target tell developers which version applies? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Worked domain 9: Learning materials

Exercises may depend on figures, definitions and answer notes. The relevant source artefact is the workbook chapters. When the target edition changes language, length or layout, a reader should still reach the object that supplies the condition, definition or evidence. Start by recording the object identity and the intended relationship. Then ask a monolingual reviewer to navigate the published target version without seeing the original.

Diagnostic 25: Learning materials, scenario 1

Source assertion: “The triangles in Figure 8 illustrate the relation defined in Section 2.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “Any triangle figure illustrates the same relation.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Use the corresponding illustration of the defined relation in the target workbook.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Do the example and definition still agree? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 26: Learning materials, scenario 2

Source assertion: “The answer to Problem 14 includes the limitation explained in Note 5.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The numeric answer has no conditions.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “The target answer retains the caveat from the correctly linked Note 5.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Can the learner find the caveat? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 27: Learning materials, scenario 3

Source assertion: “Revisit the earlier example on proportional change, not the example on fixed differences.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “Revisit the nearest example regardless of topic.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Refer explicitly to the corresponding proportional-change example.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the linked example demonstrate proportional change? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Worked domain 10: Legal information

Defined terms, clause calls and operative schedules differ from ordinary prose. The relevant source artefact is the contract and schedule. When the target edition changes language, length or layout, a reader should still reach the object that supplies the condition, definition or evidence. Start by recording the object identity and the intended relationship. Then ask a monolingual reviewer to navigate the published target version without seeing the original.

Diagnostic 28: Legal information, scenario 1

Source assertion: “The Supplier must follow the criteria defined in Schedule 2.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The supplier may choose any criteria.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “The defined Supplier role remains subject to the criteria in the correct target Schedule 2.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Do the role and schedule bind the same parties? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 29: Legal information, scenario 2

Source assertion: “The review option applies only under Clause 9.3.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The review option applies under all clauses.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “The option is restricted by the condition contained in the corresponding target clause.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the target clause contain the relevant condition? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 30: Legal information, scenario 3

Source assertion: “A reference to this instrument is to its version effective on the signing date.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “A reference automatically means the latest version after signing.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “The reference is tied to the defined effective edition.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Which edition does the translated clause identify? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Worked domain 11: Transport notices

A route map and an alert may use different labels for the same stop. The relevant source artefact is the public transport guide. When the target edition changes language, length or layout, a reader should still reach the object that supplies the condition, definition or evidence. Start by recording the object identity and the intended relationship. Then ask a monolingual reviewer to navigate the published target version without seeing the original.

Diagnostic 31: Transport notices, scenario 1

Source assertion: “Platform 4 is closed; use the replacement route shown in Map B.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “All platforms remain open.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Platform 4 is closed, and the replacement route is depicted in the correctly mapped diagram.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the target map show the stated route? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 32: Transport notices, scenario 2

Source assertion: “The footnote on the timetable explains when the overnight service does not run.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The timetable guarantees overnight service every day.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Retain the service exception associated with the appropriate timetable note.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Which days does the reader infer are excluded? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 33: Transport notices, scenario 3

Source assertion: “The symbol legend identifies accessible entrances.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “Every marked entrance is accessible without checking the legend.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Consult the corresponding legend for the entrances marked as accessible.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does each icon’s meaning match the final map? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Worked domain 12: Product instructions

Safety claims and warranty exceptions can reside in notes. The relevant source artefact is the user guide. When the target edition changes language, length or layout, a reader should still reach the object that supplies the condition, definition or evidence. Start by recording the object identity and the intended relationship. Then ask a monolingual reviewer to navigate the published target version without seeing the original.

Diagnostic 34: Product instructions, scenario 1

Source assertion: “The charging limitation is explained in the small-print note beside Figure 6.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “Figure 6 confirms there is no charging limit.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “The charging limitation remains attached to the relevant target figure and note.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Can a user see the limitation before acting? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 35: Product instructions, scenario 2

Source assertion: “The replacement part number must be copied exactly from Table 5.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The replacement part number may be freely translated.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Preserve part IDs while translating the surrounding table labels.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the final identifier match the actual part? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 36: Product instructions, scenario 3

Source assertion: “The maintenance log refers to a different procedure for older models.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The same maintenance procedure applies to all models.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Route older models to their specifically identified procedure.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Is the version distinction visible? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Worked domain 13: Disaster-readiness guides

Warnings and linked steps can change reader action. The relevant source artefact is the preparedness booklet. When the target edition changes language, length or layout, a reader should still reach the object that supplies the condition, definition or evidence. Start by recording the object identity and the intended relationship. Then ask a monolingual reviewer to navigate the published target version without seeing the original.

Diagnostic 37: Disaster-readiness guides, scenario 1

Source assertion: “For the preparation checklist, see the equipment section before the sequence begins.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “Read the checklist after completing the sequence.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Open the relevant checklist before beginning the described steps.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the target lead to the right preparation task? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 38: Disaster-readiness guides, scenario 2

Source assertion: “The evacuation map has an alternate route for mobility restrictions.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The main route applies without exception.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “The translated map and caption retain the separately identified alternative route.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the alternate route remain identifiable? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 39: Disaster-readiness guides, scenario 3

Source assertion: “A footnote distinguishes a recommendation from a local legal requirement.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “Every recommendation in the guide is a legal requirement.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Preserve the note’s explicit distinction and link readers to authorised requirements.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the target overstate the guide’s authority? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Worked domain 14: Scientific datasets

Metadata and table columns determine what a number means. The relevant source artefact is the data dictionary. When the target edition changes language, length or layout, a reader should still reach the object that supplies the condition, definition or evidence. Start by recording the object identity and the intended relationship. Then ask a monolingual reviewer to navigate the published target version without seeing the original.

Diagnostic 40: Scientific datasets, scenario 1

Source assertion: “Values in column Q are quality-control flags, not physical measurements.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “Column Q contains physical readings.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “The translated data dictionary marks Q as a quality-control indicator.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the dataset schema agree? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 41: Scientific datasets, scenario 2

Source assertion: “Figure 7 uses the normalised index described in Appendix D.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “Figure 7 shows unadjusted counts.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “The index is the normalised measure defined in the corresponding appendix.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Is normalisation clearly disclosed? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 42: Scientific datasets, scenario 3

Source assertion: “The units are specified in the table header rather than repeated in each cell.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The values have no stated units.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Retain unit-bearing header relationships in the target table.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Can a reader reconstruct the units for every affected cell? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Worked domain 15: Healthcare education

Illustrations and instructions must not substitute for professional decisions. The relevant source artefact is the health information booklet. When the target edition changes language, length or layout, a reader should still reach the object that supplies the condition, definition or evidence. Start by recording the object identity and the intended relationship. Then ask a monolingual reviewer to navigate the published target version without seeing the original.

Diagnostic 43: Healthcare education, scenario 1

Source assertion: “For the diagram of the procedure, see Figure 3; the text remains the controlling explanation.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The diagram alone constitutes complete clinical advice.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “The target points to the corresponding illustration while preserving the text’s priority.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the wording avoid presenting an illustration as a medical instruction? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 44: Healthcare education, scenario 2

Source assertion: “The glossary defines a screening result separately from a diagnosis.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “A positive screen means a confirmed diagnosis.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Preserve both defined terms and their separate glossary links.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Can the target reader distinguish screening from diagnosis? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 45: Healthcare education, scenario 3

Source assertion: “The consent explanation points to a linked section describing how data are retained.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The consent form does not need a data-retention explanation.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Keep the linked retention section and the reader’s ability to review it.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Can the reader reach the actual retention conditions? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Worked domain 16: Historical editions

Page, chapter and editorial notes differ across editions. The relevant source artefact is the translated archival book. When the target edition changes language, length or layout, a reader should still reach the object that supplies the condition, definition or evidence. Start by recording the object identity and the intended relationship. Then ask a monolingual reviewer to navigate the published target version without seeing the original.

Diagnostic 46: Historical editions, scenario 1

Source assertion: “The original author wrote this note in the first edition.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The translator supplied this note as authorial text.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Identify the note’s author and edition in the translated work.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Can the reader tell original notes from editorial notes? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 47: Historical editions, scenario 2

Source assertion: “An early edition cites Chapter 9, later merged into Chapter 8.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The historical author cited the later Chapter 8.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Preserve the historical reference and explain mapping as editorial context.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the note distinguish historical wording from current navigation? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 48: Historical editions, scenario 3

Source assertion: “The commentary refers to plate IV, not the modern plate numbering.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The artist’s source used today’s plate number.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Retain the historical designation and offer a clearly labelled correspondence.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Is the original designation recoverable? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Worked domain 17: Public dashboards

Legends, tooltips and accessible descriptions carry conditions. The relevant source artefact is the statistical display. When the target edition changes language, length or layout, a reader should still reach the object that supplies the condition, definition or evidence. Start by recording the object identity and the intended relationship. Then ask a monolingual reviewer to navigate the published target version without seeing the original.

Diagnostic 49: Public dashboards, scenario 1

Source assertion: “The red line marks forecasts while the blue line marks observations.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The red line shows measured values.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “The target legend retains forecast and observation labels without swapping them.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the colour-independent description make the distinction? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 50: Public dashboards, scenario 2

Source assertion: “The note beneath the chart says the values are provisional.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The values are final certified results.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “The translated note continues to mark provisional status.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Can a nonvisual reader encounter the qualification? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 51: Public dashboards, scenario 3

Source assertion: “The data source link opens the methodology for the displayed metric.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The data source link opens the main agency homepage.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “The target link leads to the actual method for the displayed metric.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Can the reader verify the metric’s definition? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Worked domain 18: Museum audio guides

Audio sequence and visual reference can diverge from wall labels. The relevant source artefact is the spoken tour. When the target edition changes language, length or layout, a reader should still reach the object that supplies the condition, definition or evidence. Start by recording the object identity and the intended relationship. Then ask a monolingual reviewer to navigate the published target version without seeing the original.

Diagnostic 52: Museum audio guides, scenario 1

Source assertion: “Look at the second panel beside the entrance before proceeding.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “Look at an unrelated second panel in the next room.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Identify the corresponding panel by its actual location in the target presentation.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the spoken prompt direct the listener correctly? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 53: Museum audio guides, scenario 2

Source assertion: “The object described in stop 4 is depicted on the preceding display.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The object in stop 5 is the same object.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “The narration identifies the same specific object, without confusing stop numbers.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Can visitors map audio stops to displays? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Diagnostic 54: Museum audio guides, scenario 3

Source assertion: “A transcript link provides a fuller explanation than the audio summary.” The relationship that matters is not just a repeated noun or numeral: it is the precise document object that supplies missing information. Treat its label, identifier, edition and role as separate variables. The label can change in translation; the connection to the intended information must not.

Unsafe result: “The audio summary is complete without any missing context.” This version would give a target-language reader a different instruction, a stronger claim or a misleading document route. It might be perfectly fluent. That is why a reviewer must compare not only the sentence but also the actual destination and the information it contains. A working hyperlink is not sufficient if the linked item is semantically wrong.

Safer reconstruction: “Describe the transcript as an optional expanded explanation and link the matching language edition.” Use this sentence as a meaning target rather than a fixed phrase for every language. Depending on the publication format, replace a hard-coded number with an automatically generated reference, retain a stable ID while translating its label, or provide an authorised link to the corresponding edition. Do not invent a translated destination when none has been verified.

Decisive review question: Does the transcript contain the promised detail? To complete this test, open the target output, follow the route and compare what the destination actually says with what the translated source promised. Write down the observed object, not merely whether the page responded. If the edge is broken, correct the new translated artefact or escalate to the owner of the original rather than modifying protected pages.

Transfer: build a reader journey that survives a change of language and medium

The central skill transfers beyond translation memory and bilingual proofreading. A multilingual reader may begin with a search snippet, jump to an anchor, download a PDF, consult a figure and then return to a form. A successful translation preserves that journey without assuming that every format has identical pagination or navigation. If an edge carries a prerequisite, warning, definition or reason for a claim, the edge must remain readable wherever a user encounters the content.

The following workshops are intentionally different. Some test structural identity, others test meaning, accessibility, versioning or institutional authority. For each exercise, the trainee should submit the source mapping, a proposed target segment, the actual expected destination, the observed destination and a short explanation of why the reader obtains equivalent meaning. Mere assertion of a successful link test is not enough.

Transfer workshop 1: Headings without anchor damage

The exercise begins with this condition: a long page has its heading translated but external documents still reference an old fragment ID. Draft the target wording, document relationship map and a brief reader task. The reader task should say what someone must discover or do after following the reference; it should not be satisfied merely by a page loading in the browser.

Recommended method: Keep the fragment stable if the system permits, or coordinate a validated mapping of all inbound pointers. Decide which parts of the source need literal identity and which can change display language, numbering or order. State how you would handle the case if the target-language destination did not exist. A faithful translation must not conceal an unavailable dependency or invent a new authority to make the page look complete.

Acceptance test: Create a test link from a separate page and verify that it lands on the translated section, not the top of the document. Capture the outcome and the actual destination in a release record. Have a second reviewer try the route without the original document. Their interpretation is the best check that the translated navigation transfers useful knowledge rather than only reproducing a plausible label.

Transfer workshop 2: Renumbered figures

The exercise begins with this condition: a translated handbook inserts a new photograph before the original Figure 4. Draft the target wording, document relationship map and a brief reader task. The reader task should say what someone must discover or do after following the reference; it should not be satisfied merely by a page loading in the browser.

Recommended method: Generate display numbers after layout while preserving the intended figure object. Decide which parts of the source need literal identity and which can change display language, numbering or order. State how you would handle the case if the target-language destination did not exist. A faithful translation must not conceal an unavailable dependency or invent a new authority to make the page look complete.

Acceptance test: Inspect the final figure caption and the calling sentence together, then navigate from the reference. Capture the outcome and the actual destination in a release record. Have a second reviewer try the route without the original document. Their interpretation is the best check that the translated navigation transfers useful knowledge rather than only reproducing a plausible label.

Transfer workshop 3: Split chapter

The exercise begins with this condition: an editor divides one chapter into two to make the target easier to read. Draft the target wording, document relationship map and a brief reader task. The reader task should say what someone must discover or do after following the reference; it should not be satisfied merely by a page loading in the browser.

Recommended method: Map each source section ID to a specific target section; preserve references with the correct new hierarchy. Decide which parts of the source need literal identity and which can change display language, numbering or order. State how you would handle the case if the target-language destination did not exist. A faithful translation must not conceal an unavailable dependency or invent a new authority to make the page look complete.

Acceptance test: List all incoming references to the original chapter and ensure each now reaches its intended section. Capture the outcome and the actual destination in a release record. Have a second reviewer try the route without the original document. Their interpretation is the best check that the translated navigation transfers useful knowledge rather than only reproducing a plausible label.

Transfer workshop 4: Consolidated definitions

The exercise begins with this condition: two target-language expressions are proposed for one defined technical term. Draft the target wording, document relationship map and a brief reader task. The reader task should say what someone must discover or do after following the reference; it should not be satisfied merely by a page loading in the browser.

Recommended method: Use one approved concept mapping where the definition is the same and preserve contextual grammar. Decide which parts of the source need literal identity and which can change display language, numbering or order. State how you would handle the case if the target-language destination did not exist. A faithful translation must not conceal an unavailable dependency or invent a new authority to make the page look complete.

Acceptance test: Search the target document for all variants and check that each is linked to the correct definition. Capture the outcome and the actual destination in a release record. Have a second reviewer try the route without the original document. Their interpretation is the best check that the translated navigation transfers useful knowledge rather than only reproducing a plausible label.

Transfer workshop 5: Versioned procedure

The exercise begins with this condition: a translated notice relates to product edition 3 while the reference portal defaults to edition 4. Draft the target wording, document relationship map and a brief reader task. The reader task should say what someone must discover or do after following the reference; it should not be satisfied merely by a page loading in the browser.

Recommended method: Link the applicable version or explain the limitation when no edition-specific translation exists. Decide which parts of the source need literal identity and which can change display language, numbering or order. State how you would handle the case if the target-language destination did not exist. A faithful translation must not conceal an unavailable dependency or invent a new authority to make the page look complete.

Acceptance test: Open the destination and check the version identifier and effective dates. Capture the outcome and the actual destination in a release record. Have a second reviewer try the route without the original document. Their interpretation is the best check that the translated navigation transfers useful knowledge rather than only reproducing a plausible label.

Transfer workshop 6: Reflowable eBook

The exercise begins with this condition: page 38 in the source paperback has no stable equivalent in reflowable reading software. Draft the target wording, document relationship map and a brief reader task. The reader task should say what someone must discover or do after following the reference; it should not be satisfied merely by a page loading in the browser.

Recommended method: Use a chapter or section locator appropriate to the edition rather than copying the page number. Decide which parts of the source need literal identity and which can change display language, numbering or order. State how you would handle the case if the target-language destination did not exist. A faithful translation must not conceal an unavailable dependency or invent a new authority to make the page look complete.

Acceptance test: Resize the text, change devices and confirm that navigation still identifies the passage. Capture the outcome and the actual destination in a release record. Have a second reviewer try the route without the original document. Their interpretation is the best check that the translated navigation transfers useful knowledge rather than only reproducing a plausible label.

Transfer workshop 7: Citation and summary

The exercise begins with this condition: a result paragraph cites a source for one claim and offers a separate editorial interpretation. Draft the target wording, document relationship map and a brief reader task. The reader task should say what someone must discover or do after following the reference; it should not be satisfied merely by a page loading in the browser.

Recommended method: Keep the citation on the supporting claim and leave the interpretation distinguishable. Decide which parts of the source need literal identity and which can change display language, numbering or order. State how you would handle the case if the target-language destination did not exist. A faithful translation must not conceal an unavailable dependency or invent a new authority to make the page look complete.

Acceptance test: Read the cited material and ask which exact proposition the reference can substantiate. Capture the outcome and the actual destination in a release record. Have a second reviewer try the route without the original document. Their interpretation is the best check that the translated navigation transfers useful knowledge rather than only reproducing a plausible label.

Transfer workshop 8: Quoted figure limitation

The exercise begins with this condition: a graph is accurate only for conditions indicated in a small note. Draft the target wording, document relationship map and a brief reader task. The reader task should say what someone must discover or do after following the reference; it should not be satisfied merely by a page loading in the browser.

Recommended method: Translate the note and make sure it remains associated with the graph or its caption. Decide which parts of the source need literal identity and which can change display language, numbering or order. State how you would handle the case if the target-language destination did not exist. A faithful translation must not conceal an unavailable dependency or invent a new authority to make the page look complete.

Acceptance test: Check the graph in the target PDF without the original document nearby. Capture the outcome and the actual destination in a release record. Have a second reviewer try the route without the original document. Their interpretation is the best check that the translated navigation transfers useful knowledge rather than only reproducing a plausible label.

Transfer workshop 9: Public web link

The exercise begins with this condition: a translated article promises a detailed method but the intended locale has no method page. Draft the target wording, document relationship map and a brief reader task. The reader task should say what someone must discover or do after following the reference; it should not be satisfied merely by a page loading in the browser.

Recommended method: Provide a clearly identified link to the authoritative original or state that the translation is unavailable. Decide which parts of the source need literal identity and which can change display language, numbering or order. State how you would handle the case if the target-language destination did not exist. A faithful translation must not conceal an unavailable dependency or invent a new authority to make the page look complete.

Acceptance test: Ask a target-language reader whether the destination is the promised method or a misleading substitute. Capture the outcome and the actual destination in a release record. Have a second reviewer try the route without the original document. Their interpretation is the best check that the translated navigation transfers useful knowledge rather than only reproducing a plausible label.

Transfer workshop 10: Short-screen help

The exercise begins with this condition: mobile navigation truncates descriptive links to the first words. Draft the target wording, document relationship map and a brief reader task. The reader task should say what someone must discover or do after following the reference; it should not be satisfied merely by a page loading in the browser.

Recommended method: Put distinct destination information early in the translated label. Decide which parts of the source need literal identity and which can change display language, numbering or order. State how you would handle the case if the target-language destination did not exist. A faithful translation must not conceal an unavailable dependency or invent a new authority to make the page look complete.

Acceptance test: Test common viewport sizes and accessible names for meaningful differentiation. Capture the outcome and the actual destination in a release record. Have a second reviewer try the route without the original document. Their interpretation is the best check that the translated navigation transfers useful knowledge rather than only reproducing a plausible label.

Transfer workshop 11: Nested notes

The exercise begins with this condition: one footnote quotes another note from an earlier edition. Draft the target wording, document relationship map and a brief reader task. The reader task should say what someone must discover or do after following the reference; it should not be satisfied merely by a page loading in the browser.

Recommended method: Keep separate note identities and cite the historical edition accurately. Decide which parts of the source need literal identity and which can change display language, numbering or order. State how you would handle the case if the target-language destination did not exist. A faithful translation must not conceal an unavailable dependency or invent a new authority to make the page look complete.

Acceptance test: Inspect both referenced notes for authorship and edition. Capture the outcome and the actual destination in a release record. Have a second reviewer try the route without the original document. Their interpretation is the best check that the translated navigation transfers useful knowledge rather than only reproducing a plausible label.

Transfer workshop 12: Multi-format report

The exercise begins with this condition: a report is published in web, PDF and downloadable text formats. Draft the target wording, document relationship map and a brief reader task. The reader task should say what someone must discover or do after following the reference; it should not be satisfied merely by a page loading in the browser.

Recommended method: Use structural IDs and regenerate format-specific locators. Decide which parts of the source need literal identity and which can change display language, numbering or order. State how you would handle the case if the target-language destination did not exist. A faithful translation must not conceal an unavailable dependency or invent a new authority to make the page look complete.

Acceptance test: Follow the same three high-impact references in each format and record failures separately. Capture the outcome and the actual destination in a release record. Have a second reviewer try the route without the original document. Their interpretation is the best check that the translated navigation transfers useful knowledge rather than only reproducing a plausible label.

Transfer workshop 13: Print index

The exercise begins with this condition: an indexer’s source page locators survive a major target-language expansion. Draft the target wording, document relationship map and a brief reader task. The reader task should say what someone must discover or do after following the reference; it should not be satisfied merely by a page loading in the browser.

Recommended method: Regenerate locators from target composition rather than source page numbers. Decide which parts of the source need literal identity and which can change display language, numbering or order. State how you would handle the case if the target-language destination did not exist. A faithful translation must not conceal an unavailable dependency or invent a new authority to make the page look complete.

Acceptance test: Check at least one early, middle and late entry after typesetting. Capture the outcome and the actual destination in a release record. Have a second reviewer try the route without the original document. Their interpretation is the best check that the translated navigation transfers useful knowledge rather than only reproducing a plausible label.

Transfer workshop 14: Diagram callouts

The exercise begins with this condition: an illustration has letters A, B and C printed directly on the image. Draft the target wording, document relationship map and a brief reader task. The reader task should say what someone must discover or do after following the reference; it should not be satisfied merely by a page loading in the browser.

Recommended method: Preserve or update all diagram callouts and corresponding textual labels as a coordinated unit. Decide which parts of the source need literal identity and which can change display language, numbering or order. State how you would handle the case if the target-language destination did not exist. A faithful translation must not conceal an unavailable dependency or invent a new authority to make the page look complete.

Acceptance test: Compare embedded artwork, caption, body and alternative text for the same object identities. Capture the outcome and the actual destination in a release record. Have a second reviewer try the route without the original document. Their interpretation is the best check that the translated navigation transfers useful knowledge rather than only reproducing a plausible label.

Transfer workshop 15: Form condition

The exercise begins with this condition: a consent checkbox relies on an explanatory section elsewhere. Draft the target wording, document relationship map and a brief reader task. The reader task should say what someone must discover or do after following the reference; it should not be satisfied merely by a page loading in the browser.

Recommended method: Keep the condition visible and the link available before the user confirms. Decide which parts of the source need literal identity and which can change display language, numbering or order. State how you would handle the case if the target-language destination did not exist. A faithful translation must not conceal an unavailable dependency or invent a new authority to make the page look complete.

Acceptance test: Follow the link from the actual form control and inspect the target explanation. Capture the outcome and the actual destination in a release record. Have a second reviewer try the route without the original document. Their interpretation is the best check that the translated navigation transfers useful knowledge rather than only reproducing a plausible label.

Transfer workshop 16: Cross-document dependency

The exercise begins with this condition: a procedure refers to a required external annex whose translated version is pending. Draft the target wording, document relationship map and a brief reader task. The reader task should say what someone must discover or do after following the reference; it should not be satisfied merely by a page loading in the browser.

Recommended method: Do not present an unrelated summary as an authorised replacement. Decide which parts of the source need literal identity and which can change display language, numbering or order. State how you would handle the case if the target-language destination did not exist. A faithful translation must not conceal an unavailable dependency or invent a new authority to make the page look complete.

Acceptance test: Record unavailable status and demonstrate how the reader can reach the legitimate original. Capture the outcome and the actual destination in a release record. Have a second reviewer try the route without the original document. Their interpretation is the best check that the translated navigation transfers useful knowledge rather than only reproducing a plausible label.

Transfer workshop 17: Help search

The exercise begins with this condition: a search index displays a translated heading but serves an old excerpt from another edition. Draft the target wording, document relationship map and a brief reader task. The reader task should say what someone must discover or do after following the reference; it should not be satisfied merely by a page loading in the browser.

Recommended method: Align title, excerpt, destination and current source version. Decide which parts of the source need literal identity and which can change display language, numbering or order. State how you would handle the case if the target-language destination did not exist. A faithful translation must not conceal an unavailable dependency or invent a new authority to make the page look complete.

Acceptance test: Search the target phrase and inspect the result independently. Capture the outcome and the actual destination in a release record. Have a second reviewer try the route without the original document. Their interpretation is the best check that the translated navigation transfers useful knowledge rather than only reproducing a plausible label.

Transfer workshop 18: Table header

The exercise begins with this condition: a table’s multi-level headers wrap into a confusing mobile layout. Draft the target wording, document relationship map and a brief reader task. The reader task should say what someone must discover or do after following the reference; it should not be satisfied merely by a page loading in the browser.

Recommended method: Keep the correct cell-header association in markup and translation. Decide which parts of the source need literal identity and which can change display language, numbering or order. State how you would handle the case if the target-language destination did not exist. A faithful translation must not conceal an unavailable dependency or invent a new authority to make the page look complete.

Acceptance test: Check a sample of values with keyboard and screen-reader navigation as well as visually. Capture the outcome and the actual destination in a release record. Have a second reviewer try the route without the original document. Their interpretation is the best check that the translated navigation transfers useful knowledge rather than only reproducing a plausible label.

Transfer workshop 19: Editorial correction

The exercise begins with this condition: a source page changes an appendix from informative to mandatory. Draft the target wording, document relationship map and a brief reader task. The reader task should say what someone must discover or do after following the reference; it should not be satisfied merely by a page loading in the browser.

Recommended method: Trigger a review of every target sentence and link that references the appendix. Decide which parts of the source need literal identity and which can change display language, numbering or order. State how you would handle the case if the target-language destination did not exist. A faithful translation must not conceal an unavailable dependency or invent a new authority to make the page look complete.

Acceptance test: Record the source version transition and verify that target materials do not preserve the old status. Capture the outcome and the actual destination in a release record. Have a second reviewer try the route without the original document. Their interpretation is the best check that the translated navigation transfers useful knowledge rather than only reproducing a plausible label.

Transfer workshop 20: Released archive

The exercise begins with this condition: an old edition must remain available for historical reference but not as current guidance. Draft the target wording, document relationship map and a brief reader task. The reader task should say what someone must discover or do after following the reference; it should not be satisfied merely by a page loading in the browser.

Recommended method: Label its archived status and direct operational readers to the current authorised edition. Decide which parts of the source need literal identity and which can change display language, numbering or order. State how you would handle the case if the target-language destination did not exist. A faithful translation must not conceal an unavailable dependency or invent a new authority to make the page look complete.

Acceptance test: Ask a reader which edition currently governs the action and which is historical. Capture the outcome and the actual destination in a release record. Have a second reviewer try the route without the original document. Their interpretation is the best check that the translated navigation transfers useful knowledge rather than only reproducing a plausible label.

A practical publication checklist for one translated document

1. Document identity: source and target title, language, authorial scope, publication date and effective edition are established.

2. References inventoried: every source figure, table, note, definition, appendix, index entry, citation and hyperlink has an identifier.

3. Meaning mapped: each important reference is classified by what it defines, qualifies, supports, warns about or requires.

4. Source claims verified: the source destination is actually relevant to the claim, or the original source ambiguity is identified.

5. Target object located: every reference has a specific equivalent destination or a clearly documented exception.

6. Numbers regenerated: automatic figure, table, note, section and page locators reflect the final target edition.

7. Definitions preserved: repeated technical concepts use the same governing sense wherever that sense applies.

8. Version boundaries clear: links do not silently cross incompatible products, dates or authoritative editions.

9. External destinations verified: an available target-language page is not assumed merely from a locale path pattern.

10. Fragments inspected: in-page links open the relevant section, not just the top of a related page.

11. Captions and legends aligned: body text, artwork, alternative text and visible labels agree.

12. Accessible purpose checked: important links have meaningful labels and remain usable with keyboard and assistive technology.

13. Tables interpreted correctly: headers, units and qualifiers remain associated with the right cells.

14. Footnotes and endnotes aligned: each note qualifies the right passage and preserves authorship and status.

15. Translation memory context preserved: dependent segments receive enough information to avoid guessing their antecedents.

16. Output formats tested: web, PDF, print and other released forms each receive appropriate relationship checks.

17. Change dependencies listed: updates to a source section can trigger review of incoming translated references.

18. Exceptions documented: missing translations, unavailable annexes and unresolved source defects are not silently corrected.

19. Qualified reviewer identified: high-risk references receive subject-matter review appropriate to their consequences.

20. Final reader journey passed: a reader using only the target can find the promised information and interpret the main claim correctly.

The terms readers need for a document-relationship audit

Anchor

A location or identifier used as a destination for navigation. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Fragment identifier

A part of a URL that identifies a location or element within a resource. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Cross-reference

A pointer in one passage to a different passage or object. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Referent

The entity or object to which an expression points. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Citation

An attribution and pointer that supports source identification. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Footnote

A note associated with a marker in the body, often displayed at a page foot. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Endnote

A note collected at the end of a chapter or work. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Caption

Text identifying or interpreting an image figure or table. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Figure call

A body-text reference to a figure. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Table call

A body-text reference to a table. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Defined term

An expression assigned a particular meaning within a document’s scope. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Termbase

A collection of managed terminology records and concept relations. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Concept identifier

A stable key designating a concept independently of its word form. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Relative path

A resource location interpreted relative to a base address. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Absolute URL

A complete address resolved without relying on the current page’s relative path. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Redirect

A server or application route that sends readers from one resource address to another. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Language alternate

A counterpart of a resource intended for users of another language. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Fallback

A declared route when a requested language version is not available. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Canonical URL

A search-oriented identity signal distinct from ordinary reader navigation. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Document version

An identifiable release or revision of a publication. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Supersession

The relationship by which a newer authoritative version replaces an older one. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Normative annex

An annex that carries requirements in an applicable standard or document. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Informative annex

An annex supplying explanation or background rather than binding requirements. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Dependency

A relation in which understanding or using one item relies on another. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Transclusion

Inclusion of content from one source into another presentation. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Translation unit

A bounded portion of text or data submitted for translation. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Translation memory

Stored source-target segment pairs that can support future work. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Referential integrity

Consistency of relationships between pointers and intended targets. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Reader journey

The practical sequence of decisions and navigation a user follows. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Reading order

The sequence in which content is presented to an assistive technology or reader. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Alternative text

A text equivalent conveying relevant information from an image. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Heading hierarchy

The organised levels through which a document’s topics are structured. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Schema identifier

A technical key used to identify a field element or object in a data model. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Object binding

A connection between a text reference and an identified content object. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Release gate

A condition that must be satisfied before publication. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Regression test

A check repeated after changes to catch reintroduced errors. In practice, a translator should record how this element operates in the source and which corresponding object or function will appear in the final target edition. The definition is a working distinction, not a command to translate every occurrence with the same word. Source-document format, audience and edition can change the correct implementation.

Frequently asked questions

1. What is cross-reference translation?

It is the task of preserving the link between a passage and the exact heading, figure, table, note, definition or resource it refers to, even when visible labels and page layouts change.

Apply the answer by choosing one real reference in the document and tracing it end to end. Record both the object the text promises and the object the generated target actually supplies. A correct decision should be explainable to a reader who has never opened the source-language edition.

2. Why can a grammatically correct translation be misleading?

Because a sentence can name the wrong destination, omit a prerequisite, cite a different definition or send readers to an outdated edition while remaining fluent.

3. Should section numbers be translated word for word?

Usually the target edition should reference the number that actually identifies the intended section. Automatic cross-references are often safer than copying numbers manually.

4. What is the difference between a label and an identifier?

A label is the human-facing name such as Figure 4; an identifier can be a stable technical key connecting the sentence to a content object.

5. How do I translate footnotes accurately?

Preserve the correct note, marker and relationship to the body claim. Regenerate visible numbers when composition changes and keep editorial notes distinguishable.

6. Do all external links need a target-language equivalent?

No. Use a verified equivalent if available; otherwise make the original destination and any language limitation clear rather than inventing a translation.

7. Can I translate a URL’s fragment identifier?

Only if the publishing system actually uses the translated identifier and all relevant references are updated. An arbitrary translation can break the link.

8. What if the source cross-reference is already wrong?

Identify the defect, seek authorised clarification and do not silently invent the intended target. If the source is corrected, document the relationship and scope of the change.

9. What if the translated edition has a new order?

Reconstruct the same semantic relationships while using appropriate target numbering and locations. Identical source and target page order is not required.

10. How do I handle a missing translated appendix?

State the limitation and provide the authorised original or a verified equivalent if appropriate. Do not claim the missing target edition exists.

11. Why do table headers matter to translation?

A number’s meaning often depends on its unit, column group or condition. Translating the cell alone can silently reassign it to the wrong measure.

12. How do I translate ‘see above’ or ‘below’?

Check whether the referenced item is still above or below after the target layout is generated. Prefer a precise section or object reference when order may change.

13. Can a screenshot prove the references work?

No. Screenshots show appearance, not necessarily keyboard access, link resolution, accessible names or destination content.

14. What is a semantic link test?

It checks not only whether a link opens but also whether the destination supplies the information the referring sentence promised.

15. What is the role of the XLIFF standard?

XLIFF 2.1 defines an XML interchange format for localizable information moving between tools. It can support structured exchange, but the workflow still needs semantic validation of destinations.

16. Does W3C ITS translate every HTML element automatically?

No. ITS 2.0 defines internationalization metadata categories and rules; HTML’s translate attribute is specifically relevant to what content is translatable.

17. What does WCAG say about links?

The link-purpose criterion addresses whether readers can determine the purpose of a link from its text or associated context. Translation must preserve that intelligibility.

18. Why should PDF exports receive separate tests?

A web document’s anchors and layout do not necessarily survive PDF export, where page labels, bookmarks and internal navigation can differ.

19. How do defined terms differ from ordinary vocabulary?

A defined term has an assigned meaning in a particular document or section, so a common dictionary synonym can change the document’s operative meaning.

20. Should the target always use the same word for one source term?

Not blindly. The same concept can require inflected or contextual forms, and one source word can represent different concepts. Manage meanings and scope, not only strings.

21. What is a versioned destination?

It is a reference whose meaning depends on a particular release, edition or effective date. A newer page may not replace the earlier reference accurately.

22. How should I handle a broken link discovered after publication?

Validate the intended destination, update only the authorised new content and retest linked readers or output formats. Maintain a dated change record.

23. How can I check an index in another language?

Regenerate locators against the final target composition and inspect whether the selected concepts lead to the promised passages.

24. How does this relate to How English Works?

English cross-reference expressions and sentence-level discourse help readers interpret pointers; this chapter focuses on preserving the same navigational relationships across languages and formats.

25. What does a complete audit prove?

It supplies evidence that the tested reference relationships and reader journeys are correct for the specified source and target versions; it does not guarantee every future edit will remain correct.

Research and authoritative terminology sources

These sources establish the terminology and practice used in this chapter. They address different parts of the problem: translation project specifications and evaluation, internationalization metadata, structured interchange, content references and accessible link purpose. They should not be misrepresented as a single certification scheme or as proof that a translated document’s particular contents are factually correct.

ISO 11669:2024 — Translation projects: General guidance offers a framework for specifying and managing translation projects, including needs analysis, risk and workflow. It does not itself prescribe a full analytic procedure for evaluating translated output.

ISO 5060:2024 — Evaluation of translation output addresses analytic human evaluation of human and machine-assisted translation output, including error types, sampling and evaluator competence. Its stated scope is evaluation rather than every subsequent corrective process.

W3C Internationalization Tag Set (ITS) Version 2.0 explains internationalization metadata, including translatability and terminology-related categories, and distinguishes HTML translate attributes from XML-specific representations.

OASIS XLIFF Version 2.1 is the published specification for an XML interchange format transporting localizable information and its structure between tools. It is not a substitute for verifying what a displayed link actually means.

OASIS DITA 1.3 — Processing cross-references within content references illustrates why reference resolution may depend on the source document, rendered context, key scope and reference type.

W3C Understanding WCAG 2.2 discusses navigability, link purpose, headings and labels. Technique G53 gives a documented example of making link purpose clear through link text and its surrounding sentence.

Next routes: follow the right owner and return to the translation system

Return to Master Art of Translation | The Complete System for Moving Meaning Between Languages for the overall architecture. The immediately preceding chapter, The Ambiguity Decision System, teaches how to choose or preserve readings when the source’s meaning is unresolved.

For the specific scholarly citation task, use the existing Translate | Citations, References, Footnotes and Bibliographies. For English language and cross-reference expressions, visit the protected How English Works | The Cross-Reference, or the broader How English Works | Translation and Meaning Across Languages.

For terminology learning and meaning development, use the existing Vocabulary Learning Hub. These resources retain their own editorial ownership. This new document-relationship chapter does not rewrite, retitle or replace any of them.

The final question is a reader question rather than a copy-editing question: after navigating the translated edition alone, can someone find exactly the definition, example, condition, explanation, source or action the original referred them to? If the answer is yes for every consequential connection, the document has preserved meaning across both language and structure.

Architecture child: EDKSG-TRANS-MASTER-WORLD-1320. The chapter is international in scope; the examples are fictional and do not refer to a particular country’s law or curriculum.

Master Art of Translation | The Document Relationship System — How Cross-References, Definitions, Footnotes, Tables and Links Preserve Meaning