What Is Polysemy? How the Meaning of a Technical Term Shifts with the Subject Field

One of the most insidious sources of error in technical translation is polysemy: a single term taking on a completely different equivalent according to the engineering field it appears in. In everyday language this flexibility is a richness; in a technical text it produces a direct risk. A wrongly chosen equivalent does more than irritate the reader – it can lead to a part being fitted incorrectly, or even to a safety warning being understood back to front.

Contents

Hann’s dictionary of technical translation places exactly this problem at its centre. The German word Gitter can be “grate”, “cage”, “grid” or “mesh” depending on context; Fläche, meanwhile, means “area”, “surface” or “plane”. The examples given in the book’s preface, Rolle (roll, reel, pulley, wheel) and Netz (net, grid, power line, mesh), point to the same difficulty.

In this article we look at why polysemy matters so much, at how it differs from homonymy and at how it is managed in terminology work. Our aim is to help the buyer of technical translation recognise this invisible cost and guard against it.

Polysemy and Homonymy Are Not the Same Thing

Two concepts are frequently confused in terminology. In polysemy, a single word has more than one sense and those senses are related to each other: one origin, branching meanings. In homonymy, there are two separate words whose spelling coincides but whose origin and meaning are entirely unconnected.

In Hann’s dictionary the distinction is illustrated even through gender rules: German Leiter means “conductor” when used as a masculine noun and “ladder” when used as a feminine one; these are accidental homonyms. In the same way, Messer means “measuring instrument” in its masculine form and “knife” in its neuter form. The “surface” and “area” senses of Fläche, by contrast, are branches of the same conceptual family.

The difference is decisive in practice. Homonymous terms need separate records in the termbase, because there is no conceptual link between them at all. A polysemous term, on the other hand, sits as a single record under one concept tree, its sub-senses separated by subject-field labels. Designing a termbase without drawing this distinction creates confusion that is hard to unpick later, and it misleads automatic term checking.

How Does Subject-Field Context Determine Meaning?

The right equivalent for a term is very often hidden in the engineering field the text belongs to. Hann’s dictionary makes this visible by attaching a subject-field code to every equivalent. The same German root takes different English equivalents under different codes.

Term	Subject field	Equivalent
Aufnahme	Photography	shot, photograph
Aufnahme	Stereo	recording
Aufnahme	Chemistry	absorption
Anschluß	Electrical	earth connection
Anschluß	Hydraulics	union

Every row in the table shows why choosing an equivalent without context is impossible. The first task of terminology management is to tie the term not to a meaning but, before that, to a subject field. The abbreviations the book uses (AUTO automotive, SEMI semiconductor, NUCL nuclear) carry that context in a single group of letters and fix the equivalent to one sense.

The subject-field code is in fact a disambiguation mechanism. The translator is never left asking “which Aufnahme?”; the code supplies the answer in advance. This is why every well-built termbase carries subject-field information alongside the equivalent.

Why Do Dictionaries Fall Short?

Traditional alphabetical dictionaries list the possible translations of a headword one after another and leave the choice entirely to the translator. Hann’s criticism at this point is unambiguous: because the approach disregards context and usage, it is misleading in technical translation. A translator who does not know the field tends to take the first equivalent on the list.

The solution the book proposes is to reorganise the dictionary around concept and subject field. Equivalents are not listed at random; each is given together with the field it occurs in, its synonyms and its contrasting terms. This lets you reach the equivalent you are looking for with greater confidence.

The second weakness of the alphabetical dictionary is that it offers no examples of use. Which verbs and adjectives a term appears with in a sentence very often settles its meaning; a flat list does not show this. Current termbase tools follow a similar logic, enriching every record with subject-field, context and example-sentence information in an effort to close this classic gap.

How Is Hann’s Polyseme Dictionary Built?

Hann’s Polyseme Dictionary gathers formally similar terms together. Under the root Anlage, for instance, dozens of compounds such as computer system, brake system, fuel system and stereo system are grouped under a single headword, each separated by its own subject-field code.

This arrangement does two jobs. First, the translator sees at a glance how many different faces a term has. Second, terms that are close in form but distant in meaning are prevented from becoming confused. Rather than concealing polysemy, the dictionary makes it visible; the error is thus noticed before the moment of choice rather than at it.

Under the root Band, for example, “energy band” (semiconductor), “belt” (general), “magnetic tape” (computing) and “transmission band” (electrical) stand side by side. In a paper dictionary this grouping trains the eye; in an electronic termbase the same logic is preserved through the subject field attached to each equivalent. The principle held good in 1992 and it remains the basis of termbase record structure today.

Steps for Choosing the Right Equivalent from Context

There is a practical sequence that a translator meeting a polysemous term can follow:

1. Establish the engineering field the text belongs to (automotive, semiconductor, nuclear and so on).
2. Verify the equivalent that is valid in that field against a source with subject-field codes.
3. Examine the neighbouring words in the sentence (the collocation); words used together narrow the meaning.
4. Where there are synonymous candidates, choose the preferred term in the project glossary.
5. Record your choice in the termbase with a subject-field label, so that you do not have to search for it again next time.

This sequence turns an intuitive choice into a measurable decision. In long projects with several authors especially, tying the steps to a written set of instructions is essential; otherwise every translator records their own preference and the coherence of the document breaks down. The subject-field codes in Hann’s dictionary, together with the contrasting-term (ct) and scope (cv) markers, are designed precisely to speed up this decision. The note “ct: drum brake” at the entry for disc brake, for example, positions the term alongside its opposite and heads off the wrong match from the outset.

Typical Errors Produced by Polysemy

The most common error is carrying an equivalent from one field into another. Take the word Becken: in acoustics it means “cymbal”, in domestic appliances “basin” or “sink”, in hydraulics “reservoir”. Writing “basin” in a text on acoustics turns the text into nonsense. In the same way Bild becomes “diagram” in general language, “picture” in television and “drawing” in technical drawing; a translator who mistakes the field is exposed to three separate errors.

The second frequent error is clinging to the first equivalent found. Under time pressure the translator takes the first item in the dictionary and does not check the context. The third is translating a term inconsistently within the document: the same Aufnahme becomes “recording” in one paragraph and “shot” in the next.

All three errors spring from the same root, namely from failing to give context priority. The remedy is not technical but methodological: fix the field before translation starts, take the equivalents into the termbase and run a consistency check before delivery. Managing polysemy is really a question of discipline; the right tool makes that discipline easier but does not stand in for it.

The Türkiye context

Turkish carries difficulties of its own where polysemy is concerned. Its agglutinative structure makes it easy for words derived from the same root to acquire different technical meanings according to context: “gerilim” covers both voltage in electrical engineering and stress in mechanics, while “iletken” can be either a material or an adjective. When a Turkish equivalent is chosen for a term coming from English or German, this internal polysemy has to be taken into account as well.

Because Turkish is a relatively low-resource language, reliable termbases with subject-field codes are few. In many technical fields no settled equivalent yet exists; more often than not the translator is faced with an institutional preference. The glossaries of the Turkish Standards Institution and the term lists of field associations are valuable, but their coverage is limited.

For this reason organisations commissioning technical translation in Türkiye have to start compiling their own term lists earlier than their counterparts in English-speaking markets. At our office in Ankara Kızılay, the first step on a technical project is usually to draw up this in-house glossary and to fix the preferred equivalents together with the client. Once the list has been settled, it improves both speed and consistency on every job that follows.

What does this mean for you?

If you are commissioning a technical document, polysemy is a hidden cost item for you. A single wrongly chosen term can mean the whole manual has to be reviewed again. To reduce that risk:

1. State clearly, before translation begins, which technical field the document belongs to.
2. Share your in-house term preferences and your earlier translations, if you have them.
3. Plan a round of approval for critical terms, so that your subject specialist can verify the equivalents.

These three steps make most later corrections unnecessary from the start. The most expensive translation is the one reopened after delivery because of a term.

On technical projects we fix the subject-field knowledge from the very beginning; as part of our translation services we document term choices together with their context. If there is a text you find unclear and would like us to assess, you can reach us through the quote form.

Frequently asked questions

Are polysemy and homonymy the same thing?

No. In polysemy a single word has several related senses; in homonymy there are two separate words with the same spelling but with unrelated origins and meanings. This distinction determines whether you open one record or separate records in the termbase.

Why is polysemy dangerous in technical terms?

Because, unlike in literary translation, choosing the wrong sense can lead to an assembly error or a safety risk. Hann stresses that the priority in technical translation is not elegance but precision and clarity; an equivalent should therefore not be chosen before the context has been established.

How do I find the right equivalent for a polysemous term?

Establish the field of the text in which the term appears (automotive or semiconductor, for example) and choose the equivalent specific to that field. Termbases with subject-field labels speed this choice up.

Do dictionaries solve polysemy?

Alphabetical dictionaries only list the possible equivalents and often fail to show which one is valid in which field. Sources with subject-field codes fill this gap and lead you to the right equivalent together with an example of its use.

Sources

• Hann, M. (1992). The Key to Technical Translation, Vol. 2. John Benjamins.
• Cabré, M. T. (1999). Terminology: Theory, Methods and Applications. John Benjamins.
• ISO 1087:2019. Terminology work and terminology science – Vocabulary.