Someone whose job is intermediating in oral communication in situations involving speakers of different languages; to be clearly distinguished from translators, who work with written texts. There are considerable differences between the skill sets involved and the appropriate personality types for the jobs. Interpreters, or rather interpreting jobs, come in several different flavours:

Simultaneous interpreting
The most common popular image of the interpreter, listening to the speaker and speaking in a different language at the same time without interrupting the speaker's own flow. May either be an individual accompanying a particular speaker who is operating in a different language context, as sometimes seen on TV at major international events, but more commonly to be found in glass booths at multilingual meetings and conferences, with their versions being put out on headphones to attendees from the relevant language group. The ability to listen and talk at the same time is a somewhat peculiar one, and pretty uncommon; the work is stressful and early career burnout is not uncommon. Conference interpreters generally work in teams of two or three per language pair.
Consecutive interpreting
Interpreting on a more or less sentence by sentence basis, alternating with the original speaker. This is notionally easier, but means that the interpreter needs to "manage" the discussion, and obviously slows things down. This is appropriate for one-to-one meetings, interviews, etc. and includes ...
Liaison interpreting
Consecutive interpreting working both ways, so that the interpreter is the only person who is actually aware of what both side are saying. The norm for community interpreting (e.g. between civil authorities and members of a linguistic minority group) or for those accompanying explorers or journalists in exotic locations.
Simultaneous one-way whispered interpreting for a single person at a meeting who may have trouble understanding what is going on.
Used mainly on television news and documentaries, usually with the original voice still faintly audible in the background (but usually too quietly to be intelligible, which can be quite annoying for people who understand the source language. Clearly where this is done on recorded material (as is usually the case) it can be transcribed, translated and read by a non-interpreter, but professionals do tend to do it when speed is of the essence.

Most interpreters are self-employed and work via agencies, although major international organisations like the EU and the UN do employ staff. The way into the profession (in major languages) is mainly via specialist degrees and postgraduate training, although both the US and British military intelligence services (among others, no doubt) train up serving personnel in interpreting techniques.

In an interpreted language (or just "interpreter"), commands are executed as they are read from input. An interpreter is that part of the language which does this. This is distinct from what a compiler does. The interpreter takes the higher-level source code, and rather than just generating machine code, it goes right ahead and performs whatever instruction it has parsed and translated. Python, perl, LISP, (original old-style) BASIC, awk and Java are important interpreters. An interpreter often permits interactive use, where instructions are typed in one by one, with output returned (on screen) in between. Interpreters are also common in scripting situations, but may be useful too for heavier programming, with a tendency to rapid deployment.

Broadly speaking, interpretation happens one command at a time (or line by line), and on the fly so nothing which happens "later in the program" has any effect on what the interpreter does. This also means the average interpreter can be more relaxed (than most compilers) about type-matching, declarations, and such: once it gets to the instruction in question it will just try and execute it, and throw an error if it runs into difficulties. Apart from syntax errors, runtime errors are the norm. But take this with a grain of salt, though, as most modern interpreters do go through some intermediate bytecode compilation of instructions (especially defining entire functions, classes, etc.). This doesn't change the principle, but it does mean you need to be careful defining what "one command at a time" means.

In*ter"pret*er (?), n. [Cf. OF. entrepreteur, L. interpretator.]

One who or that which interprets, explains, or expounds; a translator; especially, a person who translates orally between two parties.

We think most men's actions to be the interpreters of their thoughts. Locke.


© Webster 1913.

Log in or register to write something here or to contact authors.