When a corporate translation request arrives, the first thing asked is the language pair. Even so, naming the two languages is not always enough: the direction in which the work will be done and the market to which the target language belongs are also part of this definition. An incompletely defined pair means a wrong team assignment.
Definition
A language pair is the source and the target language stated together. The definition is always directional. The order runs from source to target.
Direction as a separate piece of information
There are two separate directions between the same two languages, and these are different jobs. A person who works in one direction may not work in the other. The direction is always stated.
Difference in competence
Most translators are markedly stronger in one direction. This difference comes from writing competence in the target language. Assignment is made accordingly.
Market information
Which market the target language is aimed at changes the preferences. Two markets of the same language may use different terms. The information is obtained at the outset.
Stating the variant
In some languages the distinction between variants is compulsory, and the pair is defined with this distinction. If it is not stated, an assumption is made. An assumption is risky.
Translation through a third language
The source text may already have been translated into another language, and this information matters. Translation through an intermediate language accumulates errors. The question is asked.
The risk of an intermediate language
Every transfer creates a degree of deviation, and as the chain gets longer the deviation accumulates. Where possible, work is done from the original source. A request is made for it.
Multilingual projects
One source text may be translated into more than one target language, and each pair is managed separately. Term decisions are kept central. Consistency is ensured.
Imbalance in capacity
In some pairs capacity is tight, and the turnaround is set accordingly. The limit is known in advance. Commitments are made with care.
More than one language in a document
A single document may contain sections in more than one language. In that case the scope is mapped. Additional competence may be needed.
Uncertainty about the source language
In some documents the source language is not clearly evident and has to be identified. Automatic detection can be wrong. The check is made by hand.
The definition in the contract
The language pair is written clearly in the contract. A vague definition leads to a dispute over scope. The direction and the variant are stated.
Pricing by pair
Commercial terms may vary with the pair, because capacity and effort differ. This structure is kept transparent. The figures live in their own place.
Separating memories and lists
A separate memory and terminology list are kept for each pair. Mixing them produces wrong suggestions. The separation is structural.
Reverse direction jobs
Working in the reverse direction of a pair requires a new memory. The existing memory cannot be used directly. Preparation is carried out separately.
Writing the direction marker
In documents the direction is generally shown with a marker, and it is written consistently. Mixed notation spoils the records. The convention is fixed.
In client records
Which pairs have been worked in is recorded in the client file. This record feeds capacity planning. Data accumulates.
What it is confused with
A language pair is frequently thought to be just the names of two languages, and the direction and the variant are skipped. Yet a pair whose direction is not stated does not determine who will do the work. The definition is always made with a direction and a variant.