How to Translate Family Trees and Kinship Diagrams

How to translate a family tree into another language is not simply a question of finding words for mother, cousin or grandparent. A family-tree diagram expresses relationships through branches, shared lines, labels, generation levels, names, symbols and sometimes dates. If one connector is misunderstood, a careful sentence translation can still assign the wrong parent, sibling, spouse or ancestor.

This guide explains how to translate family trees, genealogy charts and kinship diagrams while preserving who is related to whom. It covers paternal and maternal distinctions, multiple meanings of “cousin,” adoption and step-relationships, changing names, cultural terminology, privacy, uncertain evidence, and the practical job of making the finished diagram readable in another language.

The primary search problem here is translating a relationship diagram, not researching the entire history of a family and not translating isolated kinship words outside their context. The reliable method is to recover the relationship network first, translate the words second, and test whether someone reading the target diagram would reconstruct the same people and connections.

A family tree is a network, not a picture of boxes

The familiar visual tree places ancestors above descendants or places a couple beside their children. But a rectangle or line has meaning only under the conventions of a particular chart. Some diagrams are pedigree charts showing biological ancestry; others record legal or social kin; others map households, descendants, marriage alliances or the people relevant to a historical narrative. A translator must not assume every line denotes a genetic connection or every adjacent pair is married.

Start by identifying the chart’s purpose. Does it answer “Who descended from whom?”, “Who lived together?”, “Who inherited a title?”, or “How are the characters in this story connected?” These tasks require different labels. If the source is a clinical pedigree, it may encode information that a literary family tree deliberately omits. In a public-history chart, dates, uncertainty and source attribution may matter as much as relationships. Translating the title precisely tells readers which question the diagram can answer.

Think of each person as a node and each relationship as an explicitly labelled connection. You can then translate the labels without moving the nodes. A line between two people should be recorded as partner, spouse, co-parent, parent-child, guardian or another relation only when the source supports it. A pleasant-looking diagram is not trustworthy merely because its vertical branches are tidy.

Read the legend before assigning relationships

A common mistake is to rely on familiar conventions. One genealogy platform uses a solid line for biological parentage and a dashed line for adoption; another uses dotted lines for uncertain relationships; a historical diagram may use dashed lines for possible descent or a marriage outside a formal lineage. Without a legend, the translator cannot safely state what a line means. This is also why the words beside symbols can be more important than the symbols themselves.

Record each line style, bracket, shape, colour and arrow. Identify whether the chart distinguishes biological, adoptive, step, foster, guardianship, marriage, civil partnership or co-residence. Do not introduce a distinction the source does not make, and do not erase one that it does. A target language may offer one general word for parents in everyday speech but additional expressions that are needed for an accurate genealogical record. Choose them according to the relationship type documented, not according to what seems socially typical.

Legends also carry uncertainty. A question mark after a parent name may mean a disputed identification; a question mark beside a year may mean uncertain birth date. If the original legend states “solid: documented; dotted: hypothesised,” repeat that semantic contrast in the target version. Changing dotted to solid for visibility alters evidence. When a monochrome output removes colour coding, replace colour-dependent meanings with textual tags rather than expecting every reader to infer the hidden categories.

Build a relationship register before writing the target version

Create one stable identity record per person. It can include a neutral person ID, name exactly as given, known variants, birth and death dates when relevant, source notes, privacy status and the roles that connect the person to others. Then create separate relationship records: P03 is the recorded parent of P07; P04 and P05 married in a specified year; P06 appears as guardian of P08. Keep relationships separate from the wording used to describe them.

Why bother? Because the diagram may give a person different roles depending on the point of view. A woman is one person’s daughter, another person’s mother and a third person’s aunt. Those are not conflicting identities; they are relations from different reference nodes. Translating an unanchored “aunt” label without specifying whose aunt invites an error. An explicit register reveals which term is relative to which person.

For a family history with multiple generations, record generation and side of family separately. Do not use screen position as a substitute for evidence. A distant aunt may be placed above the main character solely to keep lines apart. A name repeated in three generations may be three different people. Assign unique IDs even if every person has the same first name, and keep initials or dates if they are needed for reader disambiguation.

Separate kinship terms from the underlying relation

Kinship vocabularies carve the social world differently. English “cousin” covers relationships for which another language may distinguish paternal from maternal relatives, older from younger cousins, or a cousin’s particular generation. English “uncle” can refer to a parent’s brother, an aunt’s husband, or a familiar adult unrelated by family. A target translation that picks one narrow term without the relevant facts can invent a relationship. The issue is not that either language is deficient; the languages simply require different distinctions.

When a narrow target-language term needs information the source does not supply, keep the ambiguity visible. A descriptive phrase such as “relative identified as a cousin; exact line not specified” may be more accurate than a fluent but unverified word. If the relationship is established by the tree’s connections, choose the specific term only after tracing those connections. Do not guess from the gender of a nearby name or the person’s location on the page.

Conversely, a source language may distinguish older and younger siblings and the target language may typically say only brother or sister. The translation may need an added qualifier to preserve that information. A kinship glossary can help maintain consistency across a large family narrative, but it should contain definitions tied to relationships, not just a bilingual word list. The translator is mapping concepts in context.

Identify the viewpoint whenever a term changes with the speaker

“Grandmother,” “daughter-in-law” and “second cousin” are not standalone facts in the same way as a birth date. They depend on the speaker or designated reference person. A family tree often highlights a person whose relations appear throughout the chart. If the highlighted person changes during translation, every relative label may need to be recalculated. This is particularly important when converting a genealogy diagram into a first-person family narrative or an educational question.

Write the viewpoint explicitly in the working notes: “all relationships in the captions are described relative to P11.” If a section changes perspective, introduce the new subject. For example, “Mara is Leo’s aunt” is a relation that can be checked; “Mara is the aunt” has no reference. If a diagram is an ancestry chart of Mara, a caption “Leo: nephew” may make sense, but only if the chart tells the reader whose nephew is intended.

Exercises based on family trees sometimes ask the reader to move viewpoints deliberately. Translating “my father’s sister’s daughter” into a single kinship term requires tracing two links and then choosing the correct relation. Teach learners to draw the path before choosing a word. This makes the exercise about semantic structure rather than the deceptive simplicity of a bilingual dictionary entry.

Preserve paternal, maternal and generational information

A genealogical record may say “maternal grandfather,” “paternal aunt” or “great-grandparent.” These modifiers are not optional decoration. Replacing all such terms with “grandfather” or “aunt” removes the path needed to understand the chart. Equally, confusing great-grandparent with grandparent moves a person one generation and can create impossible dates. Count each parent-child edge in the tree; a grandparent is two generations away from a person through parent-child links, while a great-grandparent is three.

Generational labels are not the same as age categories. An elderly first cousin can share the same genealogical generation as a younger relative. Some families have large age gaps between siblings, and branches can cross over in ages. Translating a genealogical term as “older person” distorts the relationship. Use generation number or path rather than age to check degree of kinship, unless the source is explicitly about age-based honorific use.

Some target languages distinguish mother’s brother from father’s brother or distinguish parents’ older from younger siblings. If the diagram does not supply birth order, do not invent it. A translator can retain a relational phrase even where a single culturally natural term would usually be preferred. Precision matters more than forcing every relation into the shortest possible label.

Handle marriage, partnerships and household boundaries carefully

A horizontal connecting line may show marriage, partnership, co-parenthood or simply the parents shown together. Each is a distinct fact. Marriage can be a dated legal status; partnership may be described without formal status; co-parenthood does not establish a continuing couple relationship. Do not translate one into another for familiarity. Likewise, two people sharing a household are not necessarily a couple, and a person’s household may change throughout the timeline of a family history.

If the source records multiple partners across time, preserve the order and associated children without treating the layout as a moral judgment. A branching chart can have several co-parent connections. A neat translation that places every child under one spouse because there is no room for a second branch produces false parentage. If a traditional diagram cannot display the actual relationships clearly, supplement it with text or change the layout with explicit source approval.

Terms for husband, wife, partner and spouse also carry gender and legal assumptions that may not be justified by the available record. Follow documented descriptions and relevant self-identification rather than inferring gender from which side of the diagram someone occupies. The FamilySearch GEDCOM 7 specification explicitly notes that traditional structural fields should not be read as evidence of a person’s gender or title. This is a useful reminder that software storage conventions are not always human facts.

Distinguish biological, adoptive, step, foster and guardian ties

A child’s adoptive parent, biological parent, stepparent, foster carer and legal guardian may be different people. A language that uses the same ordinary “parent” word in family conversation still needs a means of preserving the distinction in a genealogy or case record where it matters. A diagram could contain several correct family relationships to the same child. It is not necessarily contradictory for the child to appear in multiple family groups.

Avoid treating one type as more authentic than another in the translation. Translate the record’s purpose and category respectfully. If the source labels a recorded adoption, do not replace it with “real parent” versus “other parent.” If the source has not established adoption status, do not infer it from a dotted line without a legend. Family structures vary across communities, time periods and legal systems, so terms may not map one to one.

In child protection, court, healthcare or personal-record contexts, relationship accuracy has practical consequences and often requires qualified review. Do not publish a speculative relationship as a verified fact. The translation can say “listed as guardian in this record” rather than “is the parent” where those categories differ. Preserve exactly whose statement or document supplies the link.

Treat names, aliases and transliteration as identity problems

Names travel through scripts and across generations. A single person may have a birth name, a married name, an adopted name, a pen name, a transliterated spelling and a modern cataloguing form. Translating a family tree means preserving identity across those variants. Do not accidentally create two people because the name has two spellings, and do not merge two people because they share a familiar given name.

Keep a name concordance. For each person ID, list the source form, target-script rendering if used, and documented variants. If a family tree contains two people named Alex Morgan, disambiguate with dates, generation or another verified attribute rather than relying on arbitrary position. Transliteration is not the same as translating the semantic meaning of a name, and a name that happens to resemble a common word should not be replaced by that word.

Historical sources also present uncertain spellings. A handwritten registry may support two plausible readings. The translation should not hide a source transcription problem under a smooth modern name. Mark an uncertain reading according to the project’s editorial conventions and retain a reference to the original record. A name is a link to other documents; inventing an attractive spelling can make future verification harder.

Keep dates, generations and life events logically consistent

A chart can include birth, death, marriage, separation, migration and adoption dates. These are different events and should stay attached to the correct person or relationship. Birth and death years in parentheses are common but not universal; a dash may indicate a date range rather than a person’s lifespan. Verify local conventions before choosing labels. An estimated birth year should retain its approximation marker, and “living” should not automatically be inferred because the death field is blank.

Chronology provides a useful consistency check, though it is not proof. If translation places a child three generations above a recorded parent, inspect the diagram. If the source appears biologically implausible, do not silently “fix” it; transcription errors, retrospective naming, symbolic ancestry and uncertain sources are all possible. Raise a source query. A translator should neither impose a conventional family age pattern nor ignore a detectable contradiction.

When creating an accessible narrative, phrase life events with dates rather than stacking bare numerals in an ambiguous table. “Married in 1912” is clearer than putting “1912” between two names with no key. Keep the timing of a relationship distinct from the timing of births and deaths. For family histories, a diagram and a short narrative often complement one another.

Read ancestry charts, descendant charts and household charts differently

An ancestry chart starts with one person and traces earlier generations, often doubling the number of possible ancestral positions at each level. A descendants chart begins with an earlier person and follows children and later generations outward. Neither necessarily lists every spouse, household member or adopted connection. Translating “ancestors” as “relatives” broadens the chart’s claim; translating “descendants” as “children” narrows it wrongly.

A household chart represents who resided together at a stated time. Its connecting lines might show accommodation, guardianship or administrative grouping rather than ancestry. A fictional family map may serve plot comprehension and include secrets or disputed parentage that the novel reveals only later. Do not resolve the narrative’s mystery in a translated diagram whose source intentionally leaves a line uncertain.

Check whether the chart is complete or selective. Titles such as “selected descendants” and “known heirs” limit the scope. The absence of someone from a tree does not establish that they did not exist, nor is a missing link evidence that there was no relationship. In a multilingual version, a clear scope note prevents readers from treating a teaching illustration as an exhaustive legal genealogy.

Manage culturally specific relations and respectful address

In some families, people use kinship terms as forms of address for unrelated elders, close family friends or members of a wider community. That social practice matters in oral histories and ethnographic diagrams, but it should not be mistaken for documented consanguinity. Where a diagram maps address terms rather than descent, the title and legend must say so. A person called “uncle” in conversation may be a neighbour or respected elder, not a parent’s sibling.

When translating culturally specific terms, decide whether to transliterate the form of address, use a descriptive gloss or combine both on first mention. The right choice depends on audience and genre. A literary explanation may preserve the original word to convey social texture, while a child-friendly chart may favour plain descriptive language. Do not pretend that a cultural term has one exact English equivalent if it encodes age, seniority, lineage and politeness together.

Avoid reducing cultural difference to a stereotype. Describe the documented relationship and the source context. If a target language lacks a compact equivalent, use an explanatory phrase; if the source uses one flexible term, keep the original ambiguity where necessary. The goal is conceptual fidelity, not forced symmetry between two vocabulary systems.

Prepare an accessible text equivalent to the diagram

A caption such as “family tree of five generations” identifies an image but does not communicate its relationships. For a complex genealogy graphic, provide a structured long description that identifies the starting person, generations, parent-child links, partners and any significant uncertainties. The W3C’s accessibility guidance treats complex diagrams as requiring more than a short alternative phrase; a text equivalent should preserve the essential relationships, not merely describe the visual style.

A usable text form often groups people by generation or family unit. For example: “Generation 1: Iona and Sam are recorded as parents of Kai and Mira. Generation 2: Kai is the recorded parent of Lee. Mira’s relationship to Theo is marked uncertain.” That is more useful than describing boxes on the top, middle and bottom rows. It can also be translated and searched more reliably than text burned into a picture.

Privacy matters. A public family diagram involving living people may expose sensitive relationships, dates or addresses. Translate only information the publication is authorised to display, and avoid creating new detail from guesses. When a source is redacted, preserve the redaction rather than attempting to reconstruct the person from adjacent names. Accessibility is not an excuse to reveal an identity that the source intentionally conceals.

Review the relationship graph, not just the sentences

A bilingual proofreader can see that “maternal aunt” is grammatically correct yet miss that the line points to the father’s sibling. Create a second review specifically for graph structure. Select a person; trace each parent-child and partner connection in the source and target; check degree and direction; confirm uncertainty markers; and verify that aliases consistently identify the same person. This detects the most consequential family-tree translation errors.

Have a second reader reconstruct a compact relationship list from the target chart alone. Ask questions such as “Who is recorded as the parent of P12?”, “Is P14 a sibling or cousin of P12?”, and “Which links are uncertain?” Compare the answers with the original register. If the reconstruction differs, the visual translation failed even if every visible word appears fluent. The same review catches misplaced labels after right-to-left mirroring or mobile reflow.

For regulated records or inheritance matters, involve the appropriate specialist rather than letting editorial judgement substitute for official evidence. The translator should carry a transparent audit trail: source snapshot, identity register, terminology choices, unresolved questions and final decision record. A reader should be able to distinguish what the source asserts from what the translation team has merely inferred.

Build fluency by following relationship paths

Kinship diagrams are excellent material for language learning because they force learners to go beyond word memorisation. To translate “my mother’s brother’s daughter,” trace mother, then brother, then daughter. Only after recovering the relation should you select a target term, noting whether age or side of family must also be known. Repeat with relations that cross marriage, adoption and multiple generations. Explain what is not specified rather than pretending the diagram has supplied it.

The exercise strengthens pronoun reference, possession, prepositional phrases, names and precision. It also teaches the difference between a social label and evidence of a documented relationship. Readers who practise these distinctions can better interpret biographies, histories and family narratives in other languages.

Useful companion routes include the eduKateSG English Learning Hub, its vocabulary learning framework, and the dedicated discussion of kinship terms across languages. For authoritative technical context, see the FamilySearch GEDCOM 7 specification and the W3C guidance on describing complex images.

Worked translation clinic: twenty-four relationship decisions

These cases use imaginary names and hypothetical family diagrams. Their purpose is to show the exact point at which fluency can become misinformation. For each, try writing one compact label and one full explanatory sentence. The two versions should agree on who is connected to whom.

1. Two cousins named alike

Picture a source in which the chart has a first cousin named Lina and a second cousin named Lina. An apparently convenient choice would be to merge both entries because the translated names match. That would change the family record, not simply its linguistic style. Instead, keep distinct identity IDs and show the documented branch or generation for each. Before publishing, check path length between relatives before assigning cousin degree. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

Now test the wording from a different perspective. Imagine a reader who has never seen the source diagram and does not know what the translator meant to imply. Could that reader state the same relationship path and degree of confidence? If not, revise the label or add a short explanation. The final sentence should identify a relationship clearly while remaining faithful to the evidence and respecting the people represented.

2. A dotted parent-child line

Picture a source in which a legend defines dots as an unverified parentage claim. An apparently convenient choice would be to turn the line into a confirmed parent-child relationship. That would change the family record, not simply its linguistic style. Instead, mark the link as proposed or disputed, not established. Before publishing, retain the legend in translated output. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

3. A maternal uncle

Picture a source in which the person is the source subject’s mother’s brother. An apparently convenient choice would be to write paternal uncle because the name is on the right side of the diagram. That would change the family record, not simply its linguistic style. Instead, select the maternal relation supported by two explicit edges. Before publishing, reconstruct the path from the subject to the mother and then her brother. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

4. An adoptive father

Picture a source in which an adoption line and an ancestral line connect one child to different people. An apparently convenient choice would be to replace both labels with birth father. That would change the family record, not simply its linguistic style. Instead, preserve adoptive and biological categories without implying either is less authentic. Before publishing, read the specific relationship types in the source register. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

5. A household member

Picture a source in which a 1930 household chart shows an unrelated boarder living with the family. An apparently convenient choice would be to make the boarder a cousin to fit the family diagram. That would change the family record, not simply its linguistic style. Instead, say boarder or household member as the source does. Before publishing, check whether the chart is a census household or a descent record. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

6. An uncertain marriage

Picture a source in which a dashed partner line is labelled ‘marriage unconfirmed’. An apparently convenient choice would be to state a marriage as historical fact. That would change the family record, not simply its linguistic style. Instead, retain the uncertainty and distinguish a report from a documented event. Before publishing, consult the legend and any attached reference. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

7. Three people called grandfather

Picture a source in which the narrator uses an affectionate honorific for an unrelated elder. An apparently convenient choice would be to assume biological grandparent. That would change the family record, not simply its linguistic style. Instead, describe the honorific or social relationship without creating lineage. Before publishing, check whether the source is a speech transcript or formal genealogy. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

8. A stepdaughter

Picture a source in which a parent’s new spouse is connected to a child from an earlier partnership. An apparently convenient choice would be to record the new spouse as the child’s biological parent. That would change the family record, not simply its linguistic style. Instead, show the step-relationship if that is what the diagram asserts. Before publishing, use relationship records rather than position under the same household bracket. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

9. A child with two guardians

Picture a source in which a contemporary family diagram identifies two adults as guardians. An apparently convenient choice would be to translate guardian as parent in both instances. That would change the family record, not simply its linguistic style. Instead, retain guardianship status without guessing parentage. Before publishing, check legal or social categories in the chart’s note. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

10. Identical first names across generations

Picture a source in which three relatives are called Theo in successive generations. An apparently convenient choice would be to collapse all three into one timeline. That would change the family record, not simply its linguistic style. Instead, retain three person IDs and distinguishing dates when verified. Before publishing, check generation and life events separately. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

11. A maternal grandmother

Picture a source in which a source explicitly traces mother then her mother. An apparently convenient choice would be to choose a generic mother figure. That would change the family record, not simply its linguistic style. Instead, preserve the two-generation relation and maternal side. Before publishing, count the parent-child edges and viewpoint. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

12. Siblings with unknown birth order

Picture a source in which two people share recorded parents but no dates. An apparently convenient choice would be to label one older sibling based on visual order. That would change the family record, not simply its linguistic style. Instead, use sibling or brother or sister only as supported. Before publishing, do not infer age from left-to-right placement. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

13. A cousin with unknown side

Picture a source in which the caption says simply cousin and the connecting branch is cropped. An apparently convenient choice would be to invent the exact maternal branch. That would change the family record, not simply its linguistic style. Instead, keep the general cousin relation and note any missing provenance. Before publishing, request the uncropped chart or original relationship register. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

14. A partner label

Picture a source in which a connector says partner, but marriage status is not supplied. An apparently convenient choice would be to translate partner as husband or wife. That would change the family record, not simply its linguistic style. Instead, use an equivalent that does not add marriage or gender status. Before publishing, check the original label and any documented dates. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

15. A hyphenated surname

Picture a source in which a person appears under two documented surnames after a name change. An apparently convenient choice would be to split the person into separate nodes. That would change the family record, not simply its linguistic style. Instead, treat documented name variants as one identity where the record proves it. Before publishing, maintain a name concordance. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

16. An alias in an archive

Picture a source in which a historical record uses a cataloguer’s spelling that differs from a birth certificate. An apparently convenient choice would be to replace both with an invented standard form. That would change the family record, not simply its linguistic style. Instead, retain source spellings and explain the documented equivalence. Before publishing, note which spelling belongs to which source. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

17. An unknown parent

Picture a source in which a chart marks one parent ‘not recorded’. An apparently convenient choice would be to translate that as ‘no parent’. That would change the family record, not simply its linguistic style. Instead, preserve the limits of the documentary evidence. Before publishing, distinguish missing data from biological or social nonexistence. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

18. A remarriage

Picture a source in which one person has two spouse connections with different marriage dates. An apparently convenient choice would be to move all children under the later spouse. That would change the family record, not simply its linguistic style. Instead, keep children attached only to documented parent connections. Before publishing, review each child’s link rather than the couple boxes. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

19. A descendant chart

Picture a source in which a graphic follows selected grandchildren and great-grandchildren. An apparently convenient choice would be to translate its title as complete family history. That would change the family record, not simply its linguistic style. Instead, keep the chart’s selection and descendant scope. Before publishing, verify that absence does not become a negative claim. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

20. A sibling-in-law

Picture a source in which a person is married to the subject’s sibling. An apparently convenient choice would be to call them a blood sibling. That would change the family record, not simply its linguistic style. Instead, preserve the marriage-mediated relation. Before publishing, trace both the sibling edge and the partner edge. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

21. A deceased/living ambiguity

Picture a source in which a genealogy shows birth years but leaves several death years blank. An apparently convenient choice would be to mark everyone without a death year as living. That would change the family record, not simply its linguistic style. Instead, report only that death information is not supplied. Before publishing, treat missing data as missing rather than proof of a life status. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

22. A right-to-left layout

Picture a source in which a pedigree is adapted for a right-to-left script. An apparently convenient choice would be to mirror only names and let lines connect different children. That would change the family record, not simply its linguistic style. Instead, rebuild the layout while preserving all nodes and edge endpoints. Before publishing, ask a reviewer to identify each person’s parents from the published form. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

23. An adoption date

Picture a source in which a person has an adoption date later than the recorded birth date. An apparently convenient choice would be to move the birth date to the adopting parent’s box. That would change the family record, not simply its linguistic style. Instead, keep both dated events attached to the correct subject or relation. Before publishing, check exactly which event each date qualifies. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

24. A sensitive redaction

Picture a source in which a public chart contains one redacted living person’s identity. An apparently convenient choice would be to infer the person’s name from sibling labels in a long description. That would change the family record, not simply its linguistic style. Instead, carry the redaction through both image text and accessible narrative. Before publishing, audit source permissions before publication. When the evidence is incomplete, it is acceptable to preserve a broader term or mark an unresolved question; it is not acceptable to manufacture certainty.

A practical translation exercise from start to finish

Draw a fictitious chart with two grandparents, three adult children, two partnerships, four grandchildren and one uncertain connection. Give everyone a stable ID before writing a name. Translate the chart into another language and then write a text-only version starting from a named reference person. Ask a second reader to list each documented relation without seeing the drawing. Compare their answer with the intended records. A mistaken edge is not a spelling problem; it is a structural problem.

For an advanced exercise, introduce one documented adoption, one surname change and one social honorific used for a nonrelative. Do not hide the relationships or imply that one connection invalidates another. Make the reference point clear whenever a term is relational. If a target-language term requires an age or lineage distinction the source lacks, write down the unresolved fact and choose wording that does not invent it.

Translating a family tree well means preserving identities, relationship paths, evidence status and human dignity at the same time. The diagram is readable when a person can answer “Who is related to whom, in what way, according to which record?” without accidentally gaining a new ancestor, losing a guardian or mistaking a familiar title for documented parentage.

How to Translate Easily | How to Translate Family Trees and Kinship Diagrams Without Changing Who Is Related to Whom