BIK Terminology

Solving the terminology puzzle, one posting at a time

Jump List? Or what should we call it?

by

Giving a new concept a name in a source language often leads directly to the question of what to do with it in another language. This seems like a problem for target terminologists and translators, right? It isn’t. Marketing, branding and content publishing folks listen up!

We have just created a new term or appellation according to best practices from ISO 704. Now, what do we call it in the target language? What do we do with new designations, such as Azure or jump list? Well, the same best practices apply for target language terms as well. But there is a difference for terms and appellations.

Terms represent generic concepts. They are the parent concept or superordinate to other concepts. The concept called “operating system” in English has many different subordinate concepts, e.g. Windows, Linux, or Mac OS. Many times generic concepts have native-language equivalents in other languages. Of course, a particular language may borrow a term from another language, a direct loan. But that should be a deliberate term formation method and it is just one of them, as discussed in What I like about ISO 704.

An appellation represents an individual concept, one that is unique. Like you and me. And just as our parents gave us names that should represent us to the world—some very common and transparent, others peculiar or extraordinary—products get names that represent them to buyers. The criteria for good formation are weighted slightly differently than they are when used during new term formation: An appellation might be deliberately not transparent or consistent with the rest of the subject field. After all, it is a new product that is supposed to stand out. And it might be deliberately in another language.

Windows Azure™ is the appellation for “a cloud services operating system that serves as the development, service hosting and service management environment for the Windows Azure platform,” according to the official website. If we leave aside the trademark for a moment, nobody in their right mind would use the literal translations “Fenster ‘Azurblau’”, “Fenêtre bleu” or “Finestra azzurra”.

Once again, I find ISO 704 very helpful: “Technically, appellations are not translated but remain in their original language. However, an individual concept may have an appellation in different languages.” Good examples are international organizations which tend to have appellations in all languages of the member states, such as the European Union, die Europäische Union, or l’Union européenne.

ISO 704 goes on to say that “whether an individual concept has an appellation in more than one language depends on the following:

  • The language policy of a country;
  • How internationally well known the concept is;
  • The multilingual nature of the entity in question;
  • The need for international cooperation and relations.”

Based on this, it is pretty clear that an international organization would have an appellation in each of the languages of the member states. What about product names, such as Windows Azure? As terminologists for the target market, we should make recommendations in line with the above.

That is exactly what happened with a new feature for Windows 7, called Jump List in English. The message from the marketing department was that it was to remain in English even in the localized versions of Windows. But the problem wasn’t that simple.

There are actually two concepts hidden behind this name:

  • Jump List: The Windows feature that allows users to display jump lists.
    • A unique feature and therefore an individual concept.
    • An appellation.
  • jump list: A list associated with programs pinned to the taskbar or Start menu.
    • A generic concept that can happen multiple times even within one session
    • A technical term.
    • Erroneously capitalized in English.

Generally, when a new feature is introduced the feature gets a name and many times, the individual instances of the feature take on a term derived from the feature name. In this case, the feature was named Jump List and the instances were called Jump Lists. The later should not be uppercase and is in many instances not uppercase. But the two concepts were not differentiated, let alone defined up front.

So, when the German localizers got the instruction to keep the English term for all instances of the concept, they had a problem. They would have gotten away with leaving the appellation in English (e.g. Jump List-Funktion), but it would have been nearly impossible to get the meaning of the generic concept across or even just read the German text, had the term for the generic concept been the direct loan from the English. We could argue whether the literal translation Sprungliste represents the concept well to German users.

Naming is tricky, and those who name things must be very clear on what it is they are naming. Spelling is part of naming, and casing is part of spelling. Defining something upfront and then using it consistently supports clear communication and prevents errors in source and target texts.

SHARE THIS:

Dog food anyone?

by

Language is part of a company’s culture. Like other social groups, employees at a company develop a vernacular that allows them to communicate (efficiently) with each other, be specific enough, and maybe even have fun. Part of this language may be technical terms or jargon. Sometimes that works, sometimes it doesn’t.

When employees of Microsoft use a product that hasn’t been released yet, the product is referred to as dog food and the practice is called dog-fooding. Apparently, the expression eating your own dog food was coined in 1988,and it is still in use today.

According to the best practices for terminology work just published by Deutscher Terminologie-Tag e.V. and Deutsches Institut für Terminologie, well-motivated, transparent terms allow the recipient of the communication to understand the concept (the idea represented by the term) immediately and comprehensively

From a term formation standpoint, dog food is not a well-motivated term: food for dogs and software products don’t have anything obvious in common, and we have to look to Wikipedia to understand the etymology. It also violates a few other criteria for good terms:

  • There was no other dog- or food-related terminology in use for related concepts, as far as we can tell today (usage).
  • Dog food has another meaning, although one could argue that the context allows the recipient to uniquely identify what the sender refers to in his communication (uniqueness).
  • Lack of ability to derive words of another part of speech from it; the verb “to dog-food” cannot seriously be considered a well derived verb (derivation).

We can only speculate why dog food as a designator for an unreleased product has taken root anyway:

  • It is easy to pronounce and to remember.
  • It works for the casual atmosphere of an innovation-driven software environment.
  • It may have been suggested and propagated by high-ranking employees.

This last point is an interesting one. If these high-ranking individuals used the term and used it consistently and often, caused people to chuckle or to listen up, they have a very good chance of succeeding even with a poorly motivated term. Sociolinguistic aspects, e.g. who coins and disseminates a term, do play a role in term formation.

Very likely frequency and vigor of use were the two aspects that were lacking when in November 2009 Microsoft CIO, Tony Scott, tried to convince Microsoft employees to use ice cream (and ice-creaming) instead of dog food. His intentions of changing to a term that is actually associated with something that people like to eat were good. But it was far too late.

It is very difficult to eradicate even a poorly motivated term, if it has been around for a while, people are used to it, and it has a certain weirdness factor to it. Not that ice creaming wasn’t weird: In fact, back when I, as Microsoft terminologist, read the story, I was screaming, too.

SHARE THIS:

BIK Terminology

From the Blog

Follow Me