BIK Terminology

Solving the terminology puzzle, one posting at a time

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

A terminologist in bear country

September 27, 2011 by Barbara Inge Karsch

For the last several weeks, I have been working on terminology for the nicely regulated aviation industry where well-defined terminology is prevalent. It was perfect timing to learn about training, maintenance, and safety concepts in this industry, since in the midst of the assignment, I climbed into a floatplane (The Otter) and flew to Katmai National Park for four fascinating days.

This park, located in the southwestern corner of Alaska, was founded following a volcanic eruption in 1912. The explosion of Novarupta was the largest volcanic event of the 20 century, and ashes could be found as far away as Africa. When researchers around Robert Griggs ventured back into the area, they found what they thought were small sources of fire still smoldering and dubbed the place ‘Valley of Ten Thousand Smokes.’ Years later upon closer investigation, the “smoke” turned out to come from the Ukak River that had gotten buried underneath the lava. Instead of particles produced by combustion, water vapor was rising from the lava fields. The misnomer of the valley stuck, though, but outside of the proper noun, “smoke” has since been put in quotes on most boards and documents.

Inaccurate terminology in historic names is common. In fact, misleading terms could be considered an indication of progress in a subject field and incorrect names of landmarks even add to the places. I am glad, though, that terminology at the other attraction of the Park is being handled extremely carefully these days. I am referring to the Brooks River and its resident bear population.

From a safe platform, these large mammals can be observed catching fish in four distinct ways: Snorkeling which is the most effective and most popular technique; younger bears often engage in what is called the “dash-and-grab” technique of running in shallower water and snatching fish with the paw. If they are not successful and hunger really strikes, specialists switch to technique number three, stealing. The least popular, but most interesting to watch, is diving: After the bear head disappears in the green water of Naknek Lake, a pair of leathery feet emerges. Seconds later, the lucky diver pops back up with a red sockeye salmon in his jaw.

Where bears and people live close together, rangers don’t have an easy task. People are to stay at least 50 yards from the bears, and even if you have the best intentions, you constantly need to be on your toes, in more than one sense of the word.

From 8 AM to 8 PM, rangers are stationed at three strategic places, roughly where you see the blue crosses on the adjacent map. It was highly interesting to listen to them inform each other about bear movement via two-way radio. One ranger was more precise and efficient in his or her communication than the next. And they all referred to places the same way: For example, the lowest cross is close to “the platform;” the next cross up was a place called “corner.” The corner and the platform were connected via a small floating bridge (“the bridge”). And to the East of the corner was a little promontory referred to as “the point.” Rangers described pathways of bears very clearly, so that each ranger always knew when to move people away from a spot or when the bridge could be approached, even though the terrain was covered by forest.

While names of most landmarks had emerged over the years, returning rangers drew up a map to define important places for newcomers. Naming was logical and communication was adjusted seamlessly to recipient (fellow ranger or guest) and method (radio or face-to-face). While this might seem an obvious behavior, it is one that clearly contributes to the safety of the environment. Besides these professional observations, my father and I had an incredible time at Katmai National Park.

SHARE THIS:

UI is communication

August 19, 2011 by Barbara Inge Karsch

And communication contains technical terminology. Here is a simple way of showing this.

A UX designer who gets not only the user focus, but who also knows the critical role of language is my former colleague, Windows UX designer and now principal of UX Design Edge, Everett McKay. I borrowed the title of this posting from his presentation which later became a book: UI is Communication.

Obviously not everything on the user interface is language or terminology-related. And with the increased use of touch, voice or motion interaction, we might see an even clearer focus of certain types of software on these other ways of communication.

But a simple screen shot without words can demonstrate that certain types of user interfaces rely heavily, if not exclusively, on language as the means of communication between the developer of the product and the user. If the developer does not communicate the intent of the form, screen, etc. well, the user will struggle.

Here is a form without words. Get it? No? No problem: I designed it in Visual Studio myself, and I am a level 0 designer on Everett’s scale. So, there is nothing to get other than terminology on the form matters.

SHARE THIS:

Terminology extraction with memoQ 5.0 RC

August 15, 2011 by Barbara Inge Karsch

In the framework of a TermNet study, I have been researching and gathering data about terminology management systems (TMS). We will not focus on term extraction tools (TE), but since one of our tools candidates recently released a new term extraction module, I wanted to check it out. Here is what I learned from giving the TE functionality of memoQ 5.0 release candidate a good run.

Let me start by saying that this test made me realize again how much I enjoy working with terminological data; I love analyzing terms and concept, researching meaning and compiling data in entries; to me it is a very creative process. Note furthermore that I am not an expert in term extraction tools: I was a serious power-user of several proprietary term extraction tools at JDE and Microsoft; I haven’t worked with the Trados solution since 2003; and I have only played with a few other methods (e.g. Word/Excel and SynchroTerm). So, my view of the market at the moment is by no means a comprehensive one. It is, however, one of a user who has done some serious term mining work. One of the biggest projects I ever did was Axapta 4.0 specs. It took us several days to even just load all documents on a server directory; it took the engine at least a night to “spit out” 14,000 term candidates; and it took me an exhausting week to nail down 500 designators worth working with.

As a mere user, as opposed to a computational linguist, I am not primarily interested in the performance of the extraction engine (I actually think the topic is a bit overrated); I like that in memoQ I can set the minimum/maximum word lengths, the minimum frequency, and the inclusion/exclusion of words with numbers (the home-grown solutions had predefined settings for all of this). But beyond the rough selection, I can deal with either too many or too few suggestions, if the tool allows me to quickly add or delete what I deem the appropriate form. There will always be noise and lots of it. I would rather have the developer focus on the usability of the interface than “waste” time on tweaking algorithms a tiny bit more.

So, along the lines of the previous posting on UX design, my requirements on a TE tool are that it allows me to:

  • Process term candidates (go/no-go decision) extremely fast and
  • Move data into the TMS smoothly and flawlessly.

memoQ by Kilgray Translation Technologies* meets the first requirement very nicely. My (monolingual) test project was the PowerPoint presentations of the ECQA Certified Terminology Manager, which I had gone through in detail the previous week and which contained 28,979 English words. Because the subject matter is utterly familiar to me, there was no question as to what should make the cut and what shouldn’t. I loved that I could “race” through the list and go yay or nay; that I could merge obvious synonyms; and that I could modify term candidates to reflect their canonical form. Because the contexts for each candidate are all visible, I could have even checked the meaning in context quickly if I had needed to.

I also appreciated that there is already a stop word list in place. It was very easy to add to it, although here comes one suggestion: It would be great to have the term candidate automatically inserted in the stop-word dialog. Right now, I still have to type it in. It would safe time if it was prefilled. Since the stop word list is not very extensive (e.g. even words like “doesn’t” are missing in the English list), it’ll take everyone considerable time to build up a list, which in its core will not vary substantially from user to user. But that may be too much to ask for a first release.

As for my second requirement, memoQ term extraction doesn’t meet that (yet) (note that I only tested the transfer of data to memoQ, but not to qTerm). I know it is asking for a lot to have a workflow from cleaned-up term candidate list to terminological entry in a TMS. Here are two suggestions that would make a difference to users:

  • Provide a way to move context from the source document, incl. context source, into the new terminological entry.
  • Merging terms into one entry because they are synonyms is great. But they need to show up as synonyms when imported into the term base; none of my short forms (e.g. POS, TMS) showed up in the entry for the long forms (e.g. part of speech, terminology management systems) when I moved them into the memoQ term base.

My main overall wish is that we integrate TE with authoring and translation in a way that allows companies and LSPs, writers and translators to have an efficient workflow. It is imperative in technical communication/translation to document terms and concepts. When this task is put on the translators, it is already quite late, but it is better than if it doesn’t happen. Only fast and flawless processing will allow one-person or multi-person enterprises, for that matter, to carry out terminology work as part of the content supply chain. When the “fast and flawless” prerequisite is met, even those of my translator-friends who detest the term “content supply chain” will have enough time to enjoy themselves with the more creative aspects of their profession. Then, economic requirements essential on the macro level are met, and the need of the individual to get satisfaction out of the task is fulfilled on the micro level. The TE functionality of memoQ 5.0 RC excels in design and, in my opinion, is ready for translators’ use. If you have any comments, if you agree or disagree with me, I’d love to hear it.

*Kilgray is a client of BIK Terminology.

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 © 2025 BIK Terminology. All Rights Reserved. Sitemap. Website by sundaradesign.