BIK Terminology

Solving the terminology puzzle, one posting at a time

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

Archives for June 2010

How do I identify a term—terminologization

June 24, 2010 by Barbara Inge Karsch

In What is a term? our focus was on how to define the scope of a terminology database and guide a team on what should and what shouldn’t be entered into a terminology database. It is good to have rough guidelines, but there is obviously more to the story of what a term is and what should be included in a terminology database.

If we are asked to go through a list of term candidates extracted by a term extraction tool or if we are selecting terms manually, we may not always be sure whether a certain term candidate should be included. Especially if you are not a subject matter expert or if you only speak one language, this is a difficult job. It is a little easier for translators, as they are used to analyzing texts very thoroughly. As an aside, this quality makes the translator a content publisher’s best friend, for translators find the mistakes, the inconsistencies or just the minor hitches of a text. And yet in the term selection process, we have to make decisions in split seconds. How do we make them? This and the next eight postings—one short post over the next eight days—will provide more in-depth guidance on why a term should be included in a terminology database.


Let’s start with terms that have gone through what is called “terminologization”—the process by which a general-language word or expression is transformed into a term designating a concept in a language for special purposes (LSP)(ISO 704). This Microsoft Language Portal Blog posting gives a variety of examples for animal names, e.g. mouse or worm, that became technical terms in the IT industry. We are often able to distinguish terms that have undergone terminologization when we distinguish them from other terms in the conceptual vicinity (see Juan Sager’s A Practical Course in Terminology), e.g. dedicated line vs. public line.

So, if we ask ourselves: Is it a word that became a term and is now used with a very specific meaning in technical language, and the answer is yes, let’s include it in the terminology database. Then there is no confusion about what we mean with it, because it is clearly defined, and its usage can be standardized across languages.

More on term selection and the criterion “confusability” next time.

SHARE THIS:

Who has the last word?

June 17, 2010 by Barbara Inge Karsch

In most cases, terminology research leads to one obvious target terminology solution. But sometimes there are several options and many people are involved. How then do you make a decision? Who is the final authority? When a new target term is coined or a controversial term needs to be changed, stakeholders become extremely passionate about these questions (see also a recent discussion in the inkedIn Terminology group).

I believe it is simply the wrong approach to this puzzle. Even just asking the question about authority does not help negotiations. Instead, let’s look at the process: The target terminologist does the research, because that is what they are trained and paid for. Research means accessing and evaluating pertinent resources to find the answer to the terminological problem. Resources may be print and online dictionaries, books and technical magazines, websites and terminology portals, the product itself, related products and material, and, yes, subject matter experts (SMEs).

Target terminologists are the hub in the middle of a bunch of experts. Sometimes they turn out to be self-proclaimed experts or people who are simply passionate about their native language. But especially in localization environments, a terminologist is a generalist and must never work in isolation. A good terminology management system (TMS) supports the terminologist by allowing knowledge sharing by others, voting, etc.

After doing the research, after consulting experts, after weighing each term candidate carefully, the answer should be apparent to the terminologist as well as to stakeholders. Here are some of the aspects that must be taken into consideration:

  • Linguistic presentation—is the new term a well-motivated term? Again, the DTT/DIT Best Practice contains a well-structured list of criteria.
  • Budgetary concerns—does changing from an old to a new term completely blow some product group’s budget and will they therefore not go for the new suggestion?
  • Input by end-users—when the term replaces an existing term: do end-users simply not understand the old term or have a strong dislike for it?
  • Sociolinguistic aspects—how rooted is the old term already in common parlance?
  • And finally, in certain environments, political aspects—e.g. are enough stakeholders convinced to make the change so that it will actually be successful?

It goes without saying that in each situation the criteria need to be weighted differently. For Windows Vista, for example, the German term for “to download” was changed from downloaden to herunterladen. The budgetary impact was high due to the high occurrence of the term in Microsoft material. Who had the final authority on that one? Well, a user survey conducted by the German terminologist at CeBIT in Hannover revealed that many users, even techies attending the computer fair, did not like the Anglicism. The German terminologist made the case to product groups, and the change was implemented by mutual agreement.

So, why do I say that the answer “should” be apparent? The most obvious reason is that, just like everyone else, terminologists are human and make mistakes—another good reason to not work in isolation. Apart from that, here are other aspects that I have observed impacting the negotiation process in today’s virtual world:

  • Culture, gender and hierarchy: At J.D. Edwards, some handbooks were translated multiple times into Japanese. Each time a more high-ranking person in the Japanese subsidiary had a complaint, the books or certain portions of them might be retranslated. Similarly, there was “terminology du jour”—terms that changed based on the input of the subsidiary and with little guidance by the female Japanese terminologist. Gender and hierarchy have an impact on terminological decisions in certain cultures.
  • Outsourcing: An external target terminologist isn’t necessarily in the strongest position. Many may not have contact with the local market subsidiary, because there is none or it is not staffed to discuss terminology. The worst case is, though, when the linguist makes a perfectly sound suggestion, but the counter-suggestion from the subsidiary prevails because it came from the client or the perceived expert. Subsidiary PMs may have strong technical knowledge, but that does not mean that they are always completely clear a) about the concept, b) about the impact of a term change, or even c) whether the term works for the end user. It is a terminologist’s job to assess how valuable the input of an expert is.
  • Expertise and experience: Let’s face it—some terminologists don’t deserve to be called terminologists. Terms are small, if not the smallest unit of knowledge, and terminologists need to deal with dozens of them on a daily basis. Experts usually don’t get paid or have no time for terminology work. Therefore, communication better be efficient and fast. It takes tremendous skill to make a concise case and get to a solution smoothly and efficiently.

In my experience, the best designations result from the work of a team of equals who draw on each others’ strength. In many software scenarios, the ultimate SME does not even exist—terminology-management and subject-matter expertise is contributed by different parties to an online centralized terminology database managed by the terminologist for the respective language.

What is your experience—do too many cooks spoil the terminology database? Or does it take a village?

SHARE THIS:

Terminological Scatterlings*

June 10, 2010 by Barbara Inge Karsch

While it is hard to avoid soccer these days—not that I, who enjoyed the Sommermärchen (the fabulous atmosphere) in Germany four years ago, would want to—, it is not hard to link South Africa, soccer and terminology. So, let me leave corporate terminology management behind for this posting and talk a bit about South Africa from a language and terminology point-of-view.

Let’s start with South African English. If you visit this beautiful country, you will very likely notice that ’just now’ “denotes varying levels of urgency. Phoning someone ‘now now’ is sooner than ‘now’ or ‘just now’ but not as soon as ‘right now’” according to this short glossary of South Africanisms.

In their latest blog, ‘South African World Cup Draws Multilingual Audiences’, Common Sense Advisory talks about the language industry benefitting from the World Cup, which is not a surprise: Large international events always are. I fondly remember my time at the Atlanta Olympics with hundreds of other interpreters. I worked for overtired German journalists, who would normally get away without an interpreter, but long hours and the Southern accent incapacitated them. Back then, I had put together my own glossary of sports terminology. For the World Cup, we don’t need to: CLS Communication just released a multilingual World Cup dictionary in five European languages. I never knew that “Goal” is used in Swiss German. I am sure you’ll find other little surprises in the CLS Football Dictionary. Speaking of football, former Microsoft colleague and good friend, Licia Corbolante, points out cultural differences with regard to soccer in her Italian blog.

But the World Cup is just an event that lets us focus on South Africa. The country has had a rich multilingual history. With the end of apartheid came the recognition of eleven official languages: Afrikaans and English as well as the following nine indigenous languages: seSotho sa Lebowa, seSotho, seTswana, siSwati, Tshivenda, Xitsonga, isiNdebele, isiXhosa and isiZulu. We, in Europe and America, are used to other multilingual countries, like Canada, Switzerland or Belgium, leading multilingual topics. But the general level of understanding of terminology issues in South Africa makes the US look like a developing nation.

There are many governmental bodies who do terminology work. The organization charged with promoting language issues is the Pan South African Language Board:

“…PanSALB is a statutory body established to create conditions to develop and promote the equal use and enjoyment of all the official South African languages. It actively promotes an awareness of multilingualism as a national resource.” (http://www.pansalb.org.za/index.html).

The establishment of terminology is merely one of PanSALB’s many tasks and services. PanSALB members have also been actively involved in the creation of Microsoft terminology accessible on the Microsoft Language Portal in the following South African languages: Afrikaans, isiXhosa, isiZulu, seSotho sa Lebowa, and seTswana.

A look at the website for the TAMA (Terminology in Advanced Management Applications) conference in 2003 shows the multitude of terminology projects under way in South Africa: From the establishment of legal terminology in South African languages by organizations, such as the Centre for Legal Terminology in African Languages, to the work of the Terminology Subdirectorate of the National Language Service. And in time for the World Cup, the Department of Arts and Culture sponsored the publication of a Multilingual Soccer Terminology List.

Let me finish with a personal story: When I was in South Africa for TAMA in 2003, I had an exchange with a cab driver that really made me a terminologist. Ok, I had had the title “terminologist” since 1998, but I never told anyone. It was often too much trouble to explain what terminologists do. So, when the cab driver asked me what I had come to South Africa for, I told him that I was in Pretoria for a conference. “What subject area?” he kept prying. When I said terminology management, he responded, “oh, I have always been interested in semiotics.” Goooooooaal! Never after this conversation have I dumbed down what I really do.

*Borrowed from “Scatterlings of Africa” by Johnny Clegg

SHARE THIS:
« Previous Page
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.