BIK Terminology

Solving the terminology puzzle, one posting at a time

  • About
    • Curriculum Vitae
  • Services
  • Portfolio
  • Resources
  • Blog
  • Contact

Avoiding doublettes or a report from the ISO meetings in Korea

June 23, 2011 by Barbara Inge Karsch

One of the main reasons we have doublettes in our databases is that we often don’t get around to doing proper terminological analysis. I was just witness to and assistant in a prime example of a team doing this analysis at the meetings of ISO TC37.

ISO TC 37 is the technical committee for “Terminology and other language and content resources.” It is the standards body responsible for standards such as ISO 12620 (now retired, as discussed in an earlier posting), 704 (as discussed here) or soon 26162 (already quoted here). This year, the four subcommittees (SCs) and their respective working groups (WGs) met in Seoul, South Korea, from June 12 through 17.

One of these working groups had considerable trouble coming to an agreement on various aspects of a standard. Most of us know how hard it is to get subject matter experts (or language people!) to agree on something. Imagine a multi-cultural group of experts who are tasked with producing an international standard and who have native languages other than English, the language of discussion! The convener, my colleague and a seasoned terminologist, Nelida Chan, recognized that the predicament could be alleviated by some terminology work, more precisely by thorough terminological analysis.

First, she gave a short overview of the basics of terminology work, as outlined in ISO 704 Terminology work – Principles and methods. Then the group agreed on the subject field and listed it on a white board. Any of the concepts up for discussion had to be in reference to this subject field; if the discussion drifted off into general language, the reminder to focus on the subject field was right on the board.

The group knew that they had to define and name three different concepts that they had been struggling with, although lots of research had been done; so we put three boxes on the board as well. We then discussed, agreed on and added the superordinate to each box, which was the same in each case. We also discussed what distinguished each box from the other two. Furthermore, we found examples of the concepts and added what turned out to be subordinates right into the appropriate box. Not until then did we give the concepts names. And now, naming was easy.

Step 1 SUBJECT FIELD
Step 2 Superordinate Superordinate Superordinate
Step 3 Distinguishing characteristic 1
Distinguishing characteristic 2
Distinguishing characteristic 1
Distinguishing characteristic 2
Distinguishing characteristic 1
Distinguishing characteristic 2
(Step 4) Subordinate
Subordinate
Step 5 Designator Designator Designator

After this exercise, we had a definition, composed of the superordinate and its distinguishing characteristics as well as terms for the concepts. Not only did the group agree on the terms and their meanings, the data can now also be stored in the ISO terminology database. Without doublettes.

Granted, as terminologists we don’t often have the luxury of having 15 experts in one room for a discussion. But sometimes we do: I remember discussing terms and appellations for new gaming concepts in Windows Vista with marketing folks in a conference room at the Microsoft subsidiary in Munich. Even if we don’t have all experts in shouting distance, we can proceed in a similar fashion and collect the information from virtual teams and other resources in our daily work. It may take a little bit to become fluent in the process, but terminological analysis helps us avoid doublettes and pays off in the long run.

SHARE THIS:

How gridiron became a term

February 3, 2011 by Barbara Inge Karsch

When I was looking at football terminology the other day, I noticed many terms which used to be words in common everyday language and have become technical terms in sports terminology. That is what terminologization is all about.

ISO 704 formally defines terminologization as “the process by which a general-language word or expression is transformed into a term designating a concept in a language for special purposes”.

The following entry from the Merriam Webster shows quite well that the original meaning of “gridiron”, first recorded in the 14th century, was that of the cooking grate. You can find more about the etymology of gridiron in this entry of the Online Etymology Dictionary. Today, the meaning of the football field is probably more common, especially in the United States. Gridiron has moved from the everyday language of cooking into the language for special purposes of American football.

Another good example is “fumble.” In the past, fumble, the meaning of which most of us are painfully aware, moved from verb to noun in the 1640s. Here is an excerpt from the Online Etymology Dictionary:

Today, it has a very specific meaning in football terminology, as this entry from the About – Football Glossary shows. Note that the definition used in this glossary is, by terminology management standards, not a proper definition. But the sample sentence shows how “fumble” is used as a noun in football today.

The reverse effect of terminologization is called de-terminologization. There are some good examples in sports, too. Stay tuned for those.

SHARE THIS:

Jump List? Or what should we call it?

October 14, 2010 by Barbara Inge Karsch

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:
Next Page »

Blog Categories

  • Advanced terminology topics
  • Branding
  • Content publisher
  • Events
  • Interesting terms
  • Job posting
  • Process
    • Coining terms
    • Designing a terminology database
    • Maintaining a database
    • Researching terms
    • Selecting terms
    • Setting up entries
    • Standardizing entries
  • Return on investment
  • Skills and qualities
    • Negotiation skills
    • Producing quality
    • Producing quantity
  • Subject matter expert
  • Terminologist
  • Terminology 101
    • Terminology methods
    • Terminology of terminology
    • Terminology principles
  • TermNet
  • Theory
  • Tool
    • iTerm
    • Machine translation
    • Proprietary terminology management systems
      • J.D. Edwards TDB
      • Microsoft Terminology Studio
    • Term extraction tool
      • memoQ
    • Terminology portals
      • BACUS
      • EuroTermBank
      • Irish National Terminology Database
      • Microsoft Language Portal
      • Rikstermbanken
  • Translator
  • Usability

Blog Archives

  • November 2012
  • October 2012
  • September 2012
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • April 2011
  • March 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • September 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010

BIK Terminology

  • About Barbara Inge Karsch
  • Terminology Services
  • Terminology Resources
  • My Terminology Portfolio
  • Let’s Talk Terminology

From the Blog

  • A glossary for MT–terrific! MT on a glossary—horrific!
  • Part-time position for an Arabic terminologist
  • Tidbit from the ATA Conference
  • Bilingual corpora and target terminology research
  • Terminology internship at Eurocopter in France

Find It Here

Follow Me

  • Email
  • LinkedIn
  • Phone
Copyright © 2023 BIK Terminology. All Rights Reserved. Sitemap. Website by sundaradesign.