Why terminology matters
If you’re still not convinced that properly developed and translated terminology is an absolute necessity, please consider the following:
Higher product usability for end users
This equally relates to both source and target terminology. Properly developed and well-documented source terminology that includes not only terms themselves, but also their definitions, usage context, history, etc., makes any product more consistent, easier and more pleasant to use and, the last but not the least, easier to translate.
If source terms are unclear, inconsistent or vaguely defined, it frustrates and misleads not only end-users of the original product version, but also translators and reviewers of localized versions. All of these people inevitably transmit their own confusion into even less clear and consistent translated versions. Decreased usability of localized products, in turn, increases end-user dissatisfaction and burdens call centers around the world.
Making properly translated, prepared and vetted target terms available to localizers at the start of a project ensures consistency across multiple areas, including technical terms, feature names, trademarks, and more.
Completing terminology work in advance reduces both the number of review cycles and terminology errors. The same applies to TMs; They become leaner and cleaner, more efficient, and minimize retranslation rates.
Cost and time savings
With properly prepared localized terminology, PMs don’t have to accommodate hundreds of content-related (and often similar) questions from translators, and localizers don’t need to duplicate their term research efforts.
Another important advantage is a dramatic improvement in change management. While changes in term translation are inevitable, with properly managed terminology these can be easily automated fully or partially, and take much less time and effort.
More accurate LQA results
Quality assurance results strongly depend on terminology consistency and correctness, and these can only be checked properly if properly localized terminology exists and is available to all parties involved, including translators and reviewers.
Logrus IT Terminology Solution Overview
Logrus IT developed a dedicated, independent terminology creation and management service a long time ago. The solution we offer builds on years of terminology management experience.
This solution covers the creation, development and maintenance of both source and target terminology. All terms are stored in a database with multiple fields, including term definitions, usage examples, context, and history. This lets us approach every term creation or change request properly and avoid creating a duplicate term or changing a single term multiple times.
We take extensive care to ensure our clients receive complete, correct, organized and documented terminology entries that not only fit into a particular project, but are in line with other products and can be used by client teams, other vendors and/or processes (e.g. MT). We also guarantee efficient project management that optimizes existing resources and minimizes disruption for PMs and teams.
Our approach is flexible. Depending on the client’s process and team organization, we can do the following:
- Provide source and target terminology services in conjunction or isolation
- Use the client’s existing terminology database or provide an in-house solution
- Fine-tune the solution to accommodate terminology creation, approval process, set of stakeholders used by the client, etc.
- We’re prepared to work in a variety of circumstances:
- Client has and/or creates and/or manages source terminology
- Client outsources source terminology creation/maintenance to Logrus IT or a third party
- Client has no terminology process and needs it to be built from scratch
We highly recommend combining source and target terminology creation and management, as it minimizes client-side PM involvement in the process and guarantees seamless interaction among all terminologists. For instance, a source term definition or usage example that causes questions will be immediately noticed and questioned by target terminologists. As a result, the issue is going to be resolved quickly and efficiently within the Logrus IT team and without client participation.
Source terminology development and maintenance
Source terminology is created upon request from client product teams. These tasks are trusted only to the most qualified experts, who have an average of 10+ years of terminology development experience. Logrus IT’s source terminologists have hands-on experience in multiple areas including:
- Operating systems
- Consumer electronics
- Mechanical and electrical engineering, and multiple other fields
All terms are created/maintained according to formal requirements
- Definitions, descriptions and usage details from product teams studied thoroughly
- All ancillary fields, like usage, part of speech, instructions, comments, etc. are filled in
- No deviations from terminology creation or entry standards
- All changes and modifications in the process are thoroughly documented
Target terminology development and maintenance
Target terminology is created based on a new or updated source term or on a request for target term update. Logrus IT works with a carefully selected network of terminologists for all 35+ major languages and most other languages. (New languages added every year.)
All of our target terminologists are experienced linguists with a minimum of 3-5 years of active practice. All terminologists go through a customized general terminology training as well as customer and/or product-specific training.
Terminology Process at Logrus IT
Continue to the following link to see the section dedicated to the terminology process: Logrus IT Terminology Process