LISA Terminology Survey for the Localization Industry

Responses Received: 73

 

"Other" responses:

Globalization company with in-house localization tools and services

freelance translator

software company

translation

Localization educator

Localization service dept in all-round computer manufacturer (HW, SW, and Services)

company incorporates both: localization service vendor AND localization tool vendor

Localization service dept in all-round computer manufacturer (hardware, software, and services)

language service provider for companies

Software Development company

Telecom company with in-house localization organization

CRM Software Company

Applicaiton development company providing its own localization services.

Software development

software developer

mobile sellables

and Translation Memory Tool vendor

S/W developers, we localise

consultant on translation and terminology management methods

Client

Translation Company

Phoenix Contact, Germany - Automation, Surge Voltage Protection, Interfaces

If you answered No to question 2, explain why you do not manage terminology.

My company doesn't even want to pay for Glossaries.

We only manage terminology by Project.

We are aware of the benefits but have difficulty allocating busy resources away from direct client work

This is discussed case by case between the agency and our company

Our localization organisation consists of several in-country teams that are not yet fully integrated. Terminology is managed in those teams but not systematically. That is one of the challenges ahead.

There is no CENTRAL terminology management. Some monolingual terminology management might be done within the content producing departments. Multilingual t.m. is done at project level in the localization center.

It is managed systematically for some clients, where the client specifically requests it, or where we can convince clients that it is important. However, it is considered as a "nice to have" rather than an essential by many clients.

Lack of time

Despite efforts to motivate both translators and editors to systemarically maintain multilingual and bilingual term bases, this seems to succeed only when this is a client request. Otherwise maintenance tends to be sporadic.

Processes not yet established. Localization maintains a small, multilingual database, but there is no unified system yet.

no resources company not mature enough

no resources

We do it at a local level but so far we have not cooredinated ourselves to build a common database, for example.

Effort and time consuming. Most effective in conjunction with TM solutions PROVIDED can quickly import Word tables, Excel tables or whatever else the end customer may provide. Translation services are not sufficiently highly valued for a prodessional approach to this activity, which is not a direct earner.

Not enough time

"Other" responses:

All students conduct terminology research.

at vendors places

The terminology mgt is done on an ad hoc basis by translators and project mgrs

Terminology is handled by the authors and the localization project managers

Inhouse in the localisation dept and also incountry in the localisation department

Depends on the project

No dedicated staff

it is done on a project by project basis using freelancers

Translation service

it is done mainly by product managers and reviewed by editors and location specialists

Project managers manage terminology for their projects

The answer is all and none of these (one man band)

third party vender

If you answered Yes to question 7, please describe the tools.

Centralized concept-oriented multilingual relational database with queryable web interfaces. Output of word-oriented products such as glossaries and translation dictionaries. Term extraction tool. TranslationManager dictionaries. Lotus Notes databases for local project-level terminology management (preprocessing).

Trados Multiterm, Xerox Terminology Suite

Trados' Multi-term/IX

Déjà Vu X's Terminoly database management functions

Trados MultiTerm

Collins Cobuild Ver 3.1, BTQ, Termium 2001 (also includes "Le guide du rédacteur", "Lexique analogique", "Techniques de l'Ingénieur" and "The Canadian Style"), Multiterm, Multiterm Web (secure internal use by Freelance translators and Employees), Terminotix

Saqqara's CommerceSuite

So far TermStar XV

Trados Multiterm, TermSeek, SDL, TermStar

termbase Multiterm

Trados Muliterm

Microsoft Excel.

Multiterm from Trados

Domino based database

TRADOS

Terminology management tool and terminology database developed by us Internet dictionary search service

TermStar

Terminology management tool and Terminology database developed by us, Internet dictionary search service

SDLX Termbase, Trados Multiterm (used only on a project-specific basis)

Term It

MultiTerm 5.5 and MultiTerm Web Access by TRADOS

MultiTerm iX

Developped internally.

Trados

Multiterm (and Termex before)

Still in development

XTS

Multiterm IX, Termstar, SQL database

Trados Multiterm

Trados Multiterm

Catalyst and our own in-house tools.

Originally created internally because no sutable tools were available off the shelf.

Trados MultiTerm and internally developed tools

Multi-term, Catalyst, Foreign Desk

SDLX

MOT/Termit by Kielikone

STAR WebTerm, STAR TermStar

IBM Translexis

TRADOS MultiTerm

IBM TM/Win, Trados Multiterm

Trados, SDLX, WordFast

Multiterm

SDLX TermBase, Multiterm, TermStar, UniTerm

SDLX, TRADOS

TermIt

Multiterm

MultiTerm, Otherwise as specified by clients.

Trados Suite, Proprietary Tools

TermStar and WEbTerm

Access database

TRADOS

MultiTerm, Proprietary Terminology Extraction Tool

dtSearch for terminology mining

Multiterm for bilingual terminology but none for English only.

SDLX TermBase

Excel spreadsheet, Word files, flat text files, mails are used to collect the terms from our vendors. Then the terms are integrated in various tools, depending on the clients' requirements, such as: IBM Translation Manager Dictionary function, Trados Multiterm

Trados Multiterm

MultiTerm

MultiTerm (Standard), Proprietry

TRADOS 5.e all components, upgrade for next year already bugdeted

terminology tool based on DB2 database

End customer provided tables, Trados Multiterm - but only rarely (self-construction is VERY time-consuming).

Excel, SDLX termbase, Dejavu termbase

"Comment" responses:

Trados

with translation memory and machine translation tools

Trados

Only for some clients. We have not found terminology extraction tools to suit our needs. Terminology management is not a problem but extraction is.

F key access from Windows applications

TRADOS WorkBench etc.

MultiTerm + Trados Translator's Workbench

It's part of one of the TRADOS packs

Trados

bundled with Trados

"Other" responses:

No CENTRAL terminology management

Company has not recognized the need for it

What is the biggest problem you could remedy for your company by upgrading your terminology management processes or tools?

Inconsistent terminology affecting product quality and increasing translation costs. Duplication of work.

-inconsistency and ambiguity (in source and target documentation) leading to increased costs and time-to-market delays

lack of uniformity in translated text.

I could merge several glossaries. I usually don't check them because they are too many.

I would like to have our translators have glossaries, but instead we don't pay for any.

Reduce HR cost and investment.

Consistent information presented to our customers

budget and understanding of importance

We really don't look for solutions to problems in our environment. We just try to figure out what problems arise with the different tools & what kinds of solutions we can come up with for them.

Increase terminology management efficiency and ensure terminology meet local market requirements.

Sharing the terminology database wih the customes

Term inconsistence !!

None

None

so far so good, one challenge is to integrate the terminology database with localisation tools.

quality, efficiency, cost effectiveness

No problem at all

true integration with TM tool

accurate terminology update on changing fields (i.e Bluetooth)

Unified terminology mgt, starting (in the source language: English) at documentation development level, even before localization takes place.

Still lot of manual work

manpower

Price

POSSIBLE inconsistencies.

Would aid consistency across translations.

Fully integrated authoring, terminology filter, validation scanner and transltion editor would reduce human time and mistaikes.

Increase productivity in terms of glossary management and application

Improving process for terminology management

motivational, terminology management is regarded by staff as an obstacle to productivity, even if it should increase productivity

We have not been impressed by the functionality of the tools that are available. At this point, we find it easier to manage terminology in an excel spreadsheet or access database

Reduce localization costs (time spent researching terminology, trying to work around inconsistent use of English terminlogy)

customer confusion caused by lack of consistency between various documents produced at the company

look for best practice

Lack of consistency at source text level

Terminology incoordination

too many different typ of users

Collaboration and workflow around terminology management

Uniformity of usage between departments; Consistency of message.

Consistency

Inconsistencies

Centrally sharing of the terminology between our vendors and various teams internally.

consistency across product UI, documentation, marketing and legal information in all languages

The integration of terminology tools with CAT, authoring, standard implementation (J2450) and extraction processes. Trados Multiterm 5.5 is not very good and its successor is ridiculously expensive or not networkable to any extent...don't get me started!

A lot of money could be saved on software translation if software was localized right from the start!!! Term Extraction in TRADOS 6 would enable faster and more effective terminology findings/evaluation and management.

time to learn.

Higher quality, faster translation

"Comment" responses:

We collect addiitonal info on an as needed basis, we don't want to over invest.

A range of items from ISO 12620; too numerous to mention.

SOURCES for every single information; phraseological information

Internal customer

project codes

Other fields are "Notes" fields with detailed explanation of usage as required

if possible and available (ie semantic, contextual, etc.)

2500 terms for all product lines. Different catagories: some with definitions + grammar, others not, 6 languages, 2 more planned

Briefly describe your current terminology management practices (e.g., "localization vendor manages all terminology for us" or "we collect terms and definitions in spreadsheets", etc.)

Centralized management of terms. Delivery of project-specific products. Global virtual team. In-house localization which receives prepared English terminology from central db.

We manage terminology for our business and for our customers. Our terminology database stores concepts with individual term structure per language.

We collect "GUI" terms in Excel spreadsheets

I collect terms and definitions in spreadsheets and add their sources.

localization vendor manages all terminology for us, but we do not allow them to refresh translation memories, we don't allow them to create glossaries, and by allow I mean we don't pay them to do this.

we collect terms/def'ns in spreadsheets and upload into tool managed by vendor

Translators feed their terminology databases on the fly, during the course of the translation work.

We manage the process for our clients

we collect terms in databases for all in-house language pairs

Terminology is currently being managed by Rockwell QA reviewers and project manager

Primarily students document their ongoing terminology in Trados MultiTerm.

we use different application for different client - depending on how the project work is done and which tools are used in the process

We collect terms and some related information (definition, part of speech etc.) in Excel spreadsheet.

we collect terms and definitions and put them into MultiTerm database

localization vendor manages all terminology for us and we gave our feedbacks to them

We collect terms into terminology database. Localization vendor contacts us to confirm the translation for new terms.

translators/proofreaders add terminology during translation/proofreading

We collect terms into terminology database. Localization vendor contacts us to confirm the translation for new terms.

Varies widely depending on client's willingness to pay for work that is not perceived as a concrete deliverable. Common scenario is collect terms in Excel, provide tentative definitions, review by client, translate, import into tool.

We collect terms and put them in a centralized terminology database.

The terminology team manages approximately 20 multilingual sector- and client-specific terminology databases as well as numerous glossaries (Excel or Word).

we collect terms and definitions in spreadsheets

We use MultiTerm iX and spreadsheets to manage our terminology

Terminology is available in the forms of glossaries in spreasheets or in our internal terminology database format. A new tool would help improve our terminology database, but most of all, we would need resources dedicated to terminology in each of the languages we localise into.

localization vendor manages all terminology for us,except on new fields where terminology is not yet stable (50/50)

We collect terms and definitions in a non-unified way.

localization vendor manages all terminology for us and we act as a controller for consistency and also acta as Project management

We use terminology tools to collect all the data

We collect source terms, definitions and translated terms in spreadsheets.

Terminology and ancillary data is extracted by linguists for 1 language, usually in a spreadsheet. This spreadsheet (the monolingual glossary) is provided to the other languages for translation. Approval is by the client.

localization vendor manages all terminology for us

Localization vendor does some terminology mgmt for us. We do some minimal term. mgmt. in-house.

We are trying to go back and capture the English terms and capture them in central repositiory.

Client-specific, multilingual glossary databases, managed centrally and accessible to the entire project team.

We collect/create terms and definitions in Catalyst, Multi-term, Foreign Desk, Excel, etc.

we collect terms and definitions in spreadsheets, trnaslate then and have the translations verified in-region by our internal staff.

we have a well-defined terminology management process that is being deployed and evolving

We collect terms and definitions in spreadsheets for each client we work with.

We collect terms and definitions in spreadsheets during translation, validate, and import to MultiTerm.

We collect terms and definitions in spreadsheets, then converted into the formats which IBM TM/win and Trados Multiterms can accept.

none

we collect terms and definitions in spreadsheets and access databases.

Cooperate as closely as possible with our customer´s "terminology creators". Extract monolingual terminology from legacy data to show "historical" inconsistencies. Terminologiy Workshops with technical authors. Support industry standards. Combination Terminologist/Senior and Lead Translator

we collect terms and definitions in spreadsheets

we collect terms and definitions in spreadsheets first

Client + subject specific MultiTerm glossaries. Otherwise as specified by clients.

Terminology is collected centrally in databases, based on projects/products, and exported/imported as needed.

we use proper tools for terminology management practices

Access tables are created and updated by translators when translation work is done.

We register in Multiterm the problematic terms in order to have a consisten data base

Systematically extract terminology from source text build bilingual dictionaries (either in-house or outsourced) to provide translators with a comprehensive source for consistent translation

In many sections of the defense industry, term mining with dtSearch and similar tools is far more efficient than dedicated tools because SL authors are incredibly inconsistent in their own term usage.

We keep the terminology of most products. Vendors work with us to redefine terms if needed.

1 collection of translation questions using spreadsheets or dedicated forms 2 working out of terminology by our QA team (varying depending on projects) 3 insertions of these terms in terminology tools (TM, Multiterm, other databases). 4 transmission of the terminology lists to our clients, on a project basis

if time permits L10N project manager collects terms via UI and documentation as part of the L10N kit to vendors. Terms are chosen manually based on repetition or key concept, or if may pose difficulty in translation. Terms added to XLS sheet. Vendor translates Linguistic reviewer accepts/debates Terms signed off and added to MT database MT database cross-checked against all terms to ensure nothing missed. SW UItrº starts. **If no time permits vendor(s) select terms and L10N project manager reviews for validity. (unusual process only done because this person has degree in translation and specialized in terminology)

We extract, collate and present terms

English terms: During internal + external translations terms are collected and "maintained" in Multiterm, also in the TMs. All other languages: annual external translation of all new GErman terms in the database, based on TMs.Terms will be confirmed or changed by subsidiaries in the corresponding countries. Afterwards: TM maintenance accordingly

Source and target terms are logged in a terminology database under own management. Subset is made available in the translation tool.

localization vender is making our software product accessable for localization needs

We collect terms and definitions in spreadsheets, and as Dejavu and SDLX termbases

Please provide any additional relevant comments regarding terminology management at your company.

Centralization is work in progress and not complete. Local product teams still resistant to relinquishing control. Up to date terminology is still not on our external web site. Bilingual terminology is kept internal and is considered confidential which sometimes hurts our business partners.

Additions and alterations to the master database are sent by translators and are filtered by our terminologists. Terminology data exchange is currently done via FTP but will soon be available through a secure website.

Concerning item 5 above, please disregard the value entered. I had to enter a value to submit the form, but the real answer is "unkown".

it is seen as unnecessary.

It's very important

We are currently looking for a more global approach and also looking into multi-lingual terminology management

The value in # 5 is bogus. I haven't a clue how many hours to into terminology management.

We do not have special terminology staff, our editors are responsible for this, normally they do this before the start of the new project and during the production of a project.

English terminology extraction tool is very beneficial for us if it extracts appropriate compund terms and is operated properly in information development departments. Terminology glossary (definition) and its consistency in English source are essential to perform good localization

drawback: it's hard for our freelancers and some in-house translators to decide which terminology is significant and which isn't.

English terminology extraction tool is very beneficial for us if it extracts appropriate compund terms and is operated properly in information development departments. Terminology glossary (definition) and its consitency in English source are essential to perform good localization.

Tools make assumptions about how terminology will be used. Multiple fields for context, grammar etc. can be useful - but sometimes, all that is wanted is an easy-to-use list of source+target pairs.

Efficient terminology management is absolutely crucial in the language business because it grants quality, consistency, efficient communication, corporate language (CI), transparency, etc.

needs coordination between various users of localization services

Use of Extraction Tools : TermFinder XTS and interest for Web@ssistant and TermChecker

The POSSIBLE inconsistencies did not yet show up. We are going to look at tools rather as a help at the moment of translation, to enforce the present yet small terminology collections.

Excel spreadsheet glossaries can be imported into Multiterm, but often translators find it easier to work off the excel sheet. Our main problem is the lack of a reliable extraction tool.

Terminology management for Corporate Language means quality and cost management.

Access tables are used by translation dept. only.

Your questionnaire is tailored to the needs of LISA members, which is perfectly understandable. I work for defense companies with only a very limited understanding of GILT/term. management methods ...

Theory would be to work on all terminology aspects ahead of translation work, ie before translation starts. This would be valid if: > translation volumes were small enough for one person to have time to go through all files and collect the new terminology > overall project time would allow for such a work before. In reality, we rely on the translators to gather the new terminology and transmit it. Then, there is a huge work of consistency review, which is performed after the translation is finished, before delivery. In some extreme cases, terminology will be worked on after delivery (for projects where the time frame is less than one week, with no time allowed for a deep review process). Terminology is a process which needs time to be performed thoroughly and efficiently. If really new terms appear, one needs times to make the necessary research to get the the accurate translation (that is, telling questions to specialists of the peculiar field, getting answers from the client, etc). In past years, clients were having terminology departments to which vendors were addressing all questions. Answers then came from the customer. Nowadays, the terminology process has slipped towards the vendors' side, and unluckily enough, has been accompanied by a more or less total disgengagement on the customers's side. That is, when we, as subcontractors, step on a new term/concept, quite specific, we generally are unable to get a proper answer in the requested language. We can always get back to the developers to know what is is about, and hence have definitions, contexts, semantics in the source language, but we always miss the same in the target language as nobody seems to be interested in providing/validating the translated terminology. >> This is very confusing for the translators >> This does not aim to a better quality.

have been trying for years to have a consortium amongst development, documentation and marketing to improve not only EN but all languages we localized for, as well as improved customer satisfaction since different definitions were given across products, which was confusing internally so must have been for customers as well

We also work helping the Ford Group with terminology as consultants

Half of the company is interested in consistent terminology - the other is not. As long as the company management does not press for corporate identity, terminology management will be futile for the uninterested half of the company...even in terms of money.

As things stand, the most effective exchange of knowledge seems to be through translation memories. The effectiveness of terminology tools so far available is demonstrated by the lack of restricted or generally published terminology databases. There are three generally useful "dictionaries" on the Web, a few more specialised glossaries and none that can be interfaced with / imported into CAT software.