This article offers straightforward advice about how to approach abbreviations, so that you never feel that frustration again. Unless a client gives specific instructions about abbreviations, it makes sense to follow these rules:
The Rule of Thumb
If you aren’t sure, just leave an abbreviation untranslated. Yes, some end users of the translation might be unhappy about it, but this is nothing compared to the potential damage from an incorrect translation. Even if you spend an hour researching an abbreviation, that doesn’t guarantee that your assumptions are correct. Translation in general doesn’t lend itself to guessing, and even more so with abbreviations.
Widely Used Abbreviations: Translate
- You should definitely translate an abbreviation which has a widely used equivalent in the target language. For example, if you are an English to Russian translator, you will translate these abbreviations:
ABS (anti-lock braking system) — АБС
PVC (polyvinyl chloride) — ПВХ
WHO (World Health Organization) — ВОЗ
- If an abbreviated term is widely used in the target language, but has no established abbreviation, I prefer to spell it out:
Head of HR — директор по управлению персоналом
- Some terms may be widely used in the target language, but their abbreviations are left untranslated nonetheless. Examples include:
DNS (Domain Name System)
IP (Internet Protocol)
- When an abbreviation occurs in a text for the first time, it’s a good idea to spell it out in parentheses:
Автомобиль оснащен АБС (антиблокировочной системой).
Client-Specific Abbreviations: Leave Untranslated
- If an abbreviation doesn’t have a widely used equivalent in the target language, you normally don’t want to translate it. This kind of abbreviation is usually used by a client internally in their company. The first reason to leave such abbreviations untranslated is that a translation won’t make much sense to anyone, including employees of the company itself, because its staff is used to the original abbreviation. The second reason is the high probability that in other publications, these abbreviations will be left untranslated. Examples of such publications include catalogs, images, and labels. If you translate them in your text, your translations will likely become inconsistent with other publications down the road.
- In theory, you may ask your client to confirm whether they want the abbreviations translated, and if yes, explain those abbreviations. In practice, however, clients usually reply that abbreviations should not be translated, so this question is often superfluous.
- When this type of abbreviation occurs in the text for the first time, it’s a good idea to spell it out in parentheses, together with a translation. Again, you must be sure about the meaning of the abbreviation:
English: This component is part of the SS.
Russian: Этот компонент входит в состав SS (Segmental System — сегментарная система).
Do you have your own best practices about translating abbreviations to share?
If you liked this article, you might also be interested in the article about best practices for localizing user interface items.