BIK Terminology

Solving the terminology puzzle, one posting at a time

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

Archives for July 2010

Use and Misuse of Latin

July 8, 2010 by Barbara Inge Karsch

Latin can be incredibly helpful in finding the correct target term for plants or animals. And it can be a nightmare for us terminologists, when people use it just because it sounds hip.

Experts in the field of biology, botany, zoology, etc., have the luxury of using Latin as their ‘universal translator,’ as a horticulturalist put it so aptly in the San Jose Mercury News. The following example shows how we in translation benefit from it: A translator working on a German text about, say, a Kaisergoldfliege, first needs to find the Latin equivalent. An online search will reveal that the Latin name is Lucilia ceasar, according to Linneus (who Oeser and Picht justly call the founder of terminology research in Hoffmann’s “ Fachsprachen – Languages for Special Purposes”). It takes another online search to see that it is referred to as green bottle fly in English. A picture certainly helps to ascertain that it is the same animal.

This is the method that we planned to apply a few years ago, when the team responsible for the Microsoft game franchise Zoo Tycoon 2 approached the terminology team for help. Unfortunately, the project never came through. But we would have set up an entry for the common name and one for the scientific name and added a picture. That would have greatly enabled the target terminologists to find the correct equivalents in their language.

Latin is not so helpful when it is used incorrectly to form new terms, and yet that is fairly common. A Microsoft team was looking to name a reporting tool that detects something and came up with the term “detectoid.” Anyone who went through five years of Latin (albeit grudgingly) and through a course on medical terminology (more happily) like myself will recognize -oid as the suffix for “resembling” or “like.” But the tool didn’t “resemble” anything; it just did detect. Anyone who encountered the term without explanation and who was familiar with the meaning of –oid, would have been distracted. Upon further research, I also found the following argument against it: The suffix is used in hacker jargon (see this wonderful entry in Foldoc). After that it was easy to argue against “detectoid”—no incorrect application of existing meaning, and no jargon, least of all hacker jargon!

Latin is a good tool for terminologists in many fields. Terminologists in scientific disciplines or our colleagues in medical informatics and ontology rely on its clarity all the time. If used incorrectly, it can lead to unclear source terminology and potentially even worse target terms. On that note—absit iniuria verbis, or “let injury be absent from (these) words.”

SHARE THIS:

How do I identify a term—standardization

July 1, 2010 by Barbara Inge Karsch

And the final criterion in this blog series on how to identify terms is, in my mind, one of the most important ones—standardization. Standardized usage and spelling makes the life of the product user much easier, and it is fairly clear which key concepts need to be documented in a terminology database for that reason. But are they the same for target terms? And if not, how would we know what must be standardized for, say, Japanese? We don’t—that’s when we rely on process and tools.

Example 1. Before we got to standardizing terminology at J.D. Edwards (JDE), purchase orders could be pushed, committed or sent. And it all meant the same thing. That had several obvious consequences:

  • Loss of productivity by customers: They had to research documentation to find out what would happen if they clicked Push on one form, Send on another or Commit on the third.
  • Loss of productivity by translators: They walked across the hall, which fortunately was possible, to enquire about the difference.
  • Inconsistency in target languages: If some translators did not think that these three terms could stand for the same thing (why would they?), they replicated the inconsistency in their language.
  • Translation memory: Push purchase order, Commit purchase order and Send purchase order needed to be translated three times by 21 languages before the translation memory kicked in.

All this results in direct and indirect cost.

Example 2. The VP of content publishing and translation at JDE used the following example to point out that terms and concepts should not be used at will: reporting code, system code, application, product, module, and product code. While everyone in Accounting had some sort of meaning in their head, the concepts behind them were initially not clearly defined. For example, does a product consist of modules? Or does an application consist of systems? Is a reporting code part of a module or a subunit of a product code? And when a customer buys an application is it the same as a product? So, what happens if Accounting isn’t clear what exactly the customer is buying…

Example 3. Standardization to achieve consistency in the source language is self-evident. But what about the target side? Of course, we would want a team of ten localizers working on different parts of the same product to use the same terminology. One of the most difficult languages to standardize is Japanese. My former colleague and Japanese terminologist at JDE, Demi, explained it as follows:

For Japanese, “[…] we have three writing systems:

  • Chinese characters […]
  • Hiragana […]
  • Katakana […].

We often mix Roman alphabet in our writing system too. […]how to mix the three characters, Chinese, Katakana, Hiragana, plus Roman alphabet, is up to each [person’s] discretion! For translation, it causes a problem of course. We need to come up with a certain agreements and rules.”

The standards and rules that Demi referred should be reflected in standardized entries in a terminology database and available at the localizers’ fingertips. Now, the tricky part is that, for Japanese, terms representing different concepts than those selected during upfront term selection may need to be standardized. In this case, it is vital that the terminology management system allow requests for entries from downstream contributors, such as the Japanese terminologist or the Japanese localizers. The requests may not make sense to a source terminologist at first glance, so a justification comment speeds up processing of the request.

To sum up this series on how to identify terms for inclusion in a terminology database: We discussed nine criteria: terminologization, specialization, confusability, frequency, distribution, novelty, visibility, system and standardization. Each one of them weighs differently for each term candidate and most of the time several criteria apply. A terminologist, content publisher or translator has to weight these criteria and make a decision quickly. No two people will come up with the same list upfront. But tools and processes should support downstream requests.

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