Translating diplomatic documents: Setswana and English equivalence
Diplomatic texts—treaties, notes verbale, memoranda, letters of credential and formal exchanges—carry institutional authority. A translation may be treated as the text that creates rights, records consent or directs action. Literal accuracy is necessary but insufficient: wording can shift obligation, permission, urgency or the identity of the institution speaking. The translator must reproduce the intended legal and diplomatic act for the target audience.
Equivalence is directional. In English-to-Setswana work, a phrase must fit Setswana syntax, official usage and the receiving institution’s expectations. In Setswana-to-English work, compressed expressions may require an explicit institutional equivalent, especially where an English reader could otherwise mistake an aspiration for a commitment. The same pair of words can therefore work in one direction and mislead in the other.
Australian readers bring particular expectations. Department of Foreign Affairs and Trade teams in Canberra often coordinate material with Australia’s embassy in Gaborone, while translators and agencies in Sydney and Melbourne serve clients in multilingual communities. The language market commonly distinguishes written translation from oral interpreting, and NAATI accreditation helps buyers identify assessed practitioners. Australian English conventions, including day-month-year dates and local spelling, also shape briefs intended for government, legal or community use.
A dependable rendering is produced through context, terminology control and review, rather than a promise that two texts look identical. Diplomatic translators need to know the instrument’s genre, the parties’ status, the intended legal effect and which language version governs if a dispute arises. These questions shape every choice from modal verbs to the placement of a signature.
Diplomatic meaning extends beyond literal wording
A diplomatic sentence often has several layers: literal sense, institutional meaning, legal effect and ceremonial tone. A verb such as “shall” can create an obligation in one instrument and merely describe an established rule in another. Terms such as “without prejudice,” “subject to” and “notwithstanding” also depend on the surrounding procedure. Translators should read the whole instrument, its annexes and its covering note before settling on an equivalence.
Register matters as much as content. An instrument addressed to a head of government should sound more formal than a technical annex, and wording between equal states should avoid sounding confrontational. Titles, honorifics and formulae of address carry relationships that cannot be separated from the instruction itself. Preserving them does not require copying English syntax; it requires retaining the relative status expressed by the document.
Metaphor is less common in operative diplomatic prose than in political speeches, but idioms still appear in preambles, commemorations and cultural references. A rendering that follows poetic association rather than institutional meaning can shift the tone unpredictably. The Setswana metaphor translation guide provides a useful model for testing connotation, scope and register before adapting figurative language to a formal document.
Build an approved bilingual terminology base
Start with evidence from authoritative sources: bilingual government publications, treaty databases, legislation in Botswana, institutional style lists and comparable correspondence. The lexicographic and corpus research offers methods for checking attestations, frequency and semantic range rather than relying on an isolated dictionary entry. A term that is common in general use may still be unsuitable for a named office or legal instrument.
Each glossary entry should record the source term, proposed target, grammatical function, approving authority and any controlling-language rule. Keep official titles and abbreviations unchanged unless a recipient-facing convention requires otherwise. For example, “agreement” may denote a treaty, an administrative arrangement or a friendly settlement; one Setswana label cannot responsibly cover all three without checking the legal object.
Regional and orthographic detail also needs explicit control. Setswana in Botswana should not be conflated with Sepedi, formerly Northern Sotho, in South Africa. The translator should agree whether to retain Tswana or Setswana in names, how to render institutional titles and which spelling system will govern. An Australian commissioning organisation should record these choices before drafting and retain the approved terminology in a shared bilingual glossary.
Compare force, function, and register
Diplomatic equivalence has three connected tests. Semantic equivalence asks whether the words denote the same thing; functional equivalence asks whether the target performs the same legal or administrative job; pragmatic equivalence asks whether the parties’ intentions and institutional relationships remain clear. A strong rendering normally passes all three, though the exact wording may differ.
| English wording | Diplomatic function | Setswana working treatment | Review point |
|---|---|---|---|
| “shall” or “must” | Creates an obligation | Use an approved form such as ka tshwanetse where house style permits | Confirm that discretion is excluded |
| “may” | Expresses permission | Consider fa go kgone or ka ntlha ya go kgone in context | Retain conditionality |
| “request” | Makes a courteous request | Use kopo with suitable framing | Do not recast it as a demand |
| “Government” | Identifies state authority or a ministry | Use puso for generic authority; retain an official name otherwise | Identify the legal actor |
| “agreement” | Names a legal arrangement | Use the approved equivalent, often tumalanyana | Check the object and binding force |
| “without prejudice” | Reserves a position or right | Use an institutionally approved formula | Check its relationship to the governing text |
Working forms in a comparison aid are not final translations. Setswana syntax, noun-class concord and the placement of modifiers can alter what appears to modify what. A back translation may reveal omissions or contradictions, but it cannot by itself decide whether an obligation, courtesy or reservation has survived. A qualified bilingual reviewer must test each passage against the source’s legal function.
For Setswana-to-English work, the editor may need a more explicit English phrase rather than an artificially short equivalent. If a Setswana original uses an institutional title with no direct English form, a brief parenthetical or translator’s note may be safer than an unmarked guess. The receiving department should approve any such expansion because added clarity can also add unintended commitment.
Preserve identities, dates, and document controls
Names are part of the act. Transliterate personal names consistently, retain diacritics where the source supplies them, and preserve the official names of states, ministries and treaties. Titles accompanying letters of credential should follow the receiving protocol rather than being improvised from a general list of honorifics. Check whether an abbreviation denotes an office, a person or a document, since these require different English and Setswana treatment.
Dates, numbers and references need the same scrutiny. Australian briefs often expect day-month-year order, but changing a source date without a stated house rule can create ambiguity. Spelled months, numerals and paragraph references should be rendered consistently while preserving their referents. Shared identifiers on the cover sheet, attachment list and signature page must remain identical across languages.
Translation does not reduce a document’s sensitivity or legal status. Classifications, distribution limits, seals, initials and handling instructions must travel with the text. Australian Government workflows may engage the Privacy Act 1988 and the Protective Data Security Standards, while classified material may raise the Security of Information Act 2007 and the sender’s security procedures. Secure transfer, limited access and version control are therefore part of translation quality.
Prepare the text for Australian and international readers
For Australian recipients, consistency with the Australian Government Style Manual can prevent avoidable friction over spelling, punctuation, dates and plain language. Formal instruments should retain a formal register, while public summaries can use clearer sentences without altering the binding text. Plain English is valuable there, but the legal document and its plain-language version must remain visibly distinct.
The Australian market also shapes delivery. In Sydney and Melbourne, community organisations, health services and education providers often commission translations across many language communities; a clear statement of audience, purpose, file format and turnaround is essential. NAATI accreditation is relevant to many public-sector buyers, although accreditation alone does not establish competence in diplomatic law. Subject expertise and a tested bilingual review remain necessary.
Style editing should be coordinated with translation rather than added afterwards by an editor unfamiliar with the source. The professional style portfolio shows how register and audience can shape editorial decisions. In a bilingual instrument, terminology consistency, page layout and the treatment of headings matter alongside sentence-level accuracy, especially when both versions will be signed and filed.
Use a controlled translation workflow
A controlled workflow begins with a source audit: identify the authoritative file, language pair, intended recipients, legal status, security level and any precedence clause. Translators should work from the signed or officially issued version, not a convenient email attachment, and record every question sent to the commissioning institution. The approved glossary should be issued with the source material.
Production should move from draft to terminology check, independent bilingual review, institutional or legal review, back-checking, proof reconciliation and final approval. For dual-language publication, give each version a clear version number and date, distinguish signed copies from drafts, and preserve an audit trail. If the parties have not stated which text controls, that ambiguity should be raised before the instrument is presented as final.
The practical takeaway is to treat every rendering as an instrument with institutional consequences. A document is ready only when its terminology, modality, identities, document controls and version precedence have been reconciled against the source by qualified reviewers, leaving each reader with the same rights, duties and intended action.