Articulate Localization
Terminology and consistency. Why a glossary is essential before the first click.
This article explains the key terminology used in Articulate Localization so you can communicate clearly with reviewers, stakeholders, and technical teams.
It provides concise definitions of common terms like machine translation, human review, QA, update handling, and workflow governance that you will encounter across this series and in real localization projects.
This is Post 4 of 5 on our deep-dive series on Articulate Localization in Storyline and Rise. Click on the button to go back to the overview.
The core problem: no translation memory, no "learning" from previous translations
In traditional translation processes, a translation memory (TM) ensures that:
- Repetitions remain consistent
- previously approved formulations are reused
- Teams develop a consistent course language across multiple courses
Articulate Localization lacks this mechanism (in the form familiar to translation teams). The result:
- The same sentence may be translated differently in multiple places
- Recurring elements drift apart across multiple courses
- Consistency does not arise automatically, but only through review and guidelines
Practical example (typical):
A call to action such as “Start now” is rendered once as “Start now” and later as “Start now.” Neither is “wrong,” but together they appear disjointed and unprofessional.
Glossary in Articulate Localization:
Helpful, but only if it is implemented early on
What the glossary does well
Uploading a glossary before translation can save a lot of time and effort:
- Key technical terms
- Product names and UI terms
- defined translations for recurring terms
Ideally, this gives the review a clear guideline: “This is what we call it.”
Where it hurts in practice
The glossary does not automatically help retroactively if…
- Terms are added retrospectively
- a term is defined differently globally
- you only notice during the review that a specification is missing
Then there are usually only two options:
- Retranslate and check the corrections again
- Manually search for all occurrences and correct them
And if the incorrect term appears in 20 places, this is not a “minor fix,” but rather review work.
A glossary is not a miracle cure.
Context remains human.
Even with a perfect glossary, one problem remains: context.
Example:
You specify that “command” should always be translated as “Kommando” in the UI. However, there are passages where “command” is not meant as a UI term (“Your wish is my command.”). In this case, a literal application of terminology would be incorrect.
Machines cannot reliably differentiate between these two meanings. A glossary is a guideline, not an understanding of context. Therefore:
Glossary = consistency anchor. Review = context check.
Additional stumbling block:
Tone (formal/informal) is not automatically stable
Many teams choose a tone (formal/informal) when setting up and then expect consistency. In practice, this can vary:
- within a course
- or between courses
In German in particular, mixing “Sie” and “du” comes across as extremely unprofessional, because learners immediately notice that the style is not consistent.
Consequence: tone must be reviewed in the same way as terminology.
Glossary management:
Organize externally, otherwise it will become unmanageable.
Uploading a glossary is easy. Managing a glossary is the real work:
- Versioning (which version has been approved?)
- Responsibility (who decides on new terms?)
- Product/brand differences (multiple glossaries, different registers)
- Approval processes
When multiple teams and courses are involved, you need at least:
- A responsible role (terminology responsibility)
- a clean filing system
- clear rules on when a glossary may be changed
Otherwise, there is a high risk that the wrong version will be uploaded by mistake and you will only notice this once the course is already “live.”
Mini checklist:
Terminology and consistency before the first click
Before translating
• Create a glossary: key terms, UI terms, product names, taboos
• Define tone (formal/informal) and document it as a rule
• Define examples: preferred wording for recurring elements
In the review
• Systematically check terminology (search for critical terms)
• Check style and tone (formal/informal, “brand voice”)
• Make conscious decisions about contextual cases (where should terminology not be applied rigidly?)
Across multiple courses
• Maintain a glossary as a “single source of truth”
• Consciously standardize recurring texts (don’t “reinvent the wheel” every time)
• If consistency is important: plan for external support/TM workflows
Conclusion: Without a glossary, there is no consistency. Without consistency, there is no professional training.
Articulate Localization can speed things up.
But consistency can only be achieved if the terminology is defined before the first click and a review is planned as an integral part of the process.
Those who try to save money on the glossary or post-editing often end up with:
- more loops
- more internal workload
- and a result that is “translated” but not “release-ready.”
Related posts in this series
Introduction: Articulate Localization in a reality check 
Post 1: One-Click vs. reality
Post 2: Machine translation vs. human review
Post 3: Technical limitations (media mix, updates, layout, storyline) ↗
Post 5: Realistic cost planning (where the effort really lies)
Conclusion: A brief summary overview
FAQ
Frequently asked questions about terminology and consistency in Articulate Localization
Answers to the most frequently asked questions about our Articulate Localization service. We have compiled the most important information. If you have any further questions, please do not hesitate to contact us directly.
Is it enough to simply upload a glossary and then click "Translate"?
No. A glossary is very helpful for key terms, but it is no substitute for review. It cannot reliably resolve issues of context, style, or tone. A glossary is a guardrail, not autopilot.
We have subsequently expanded the glossary. Do the new terms automatically apply everywhere?
Not automatically retroactive. New or modified glossaries usually only affect future translations or new translation runs. Existing content must be checked specifically and, if necessary, corrected manually or retranslated.
Why is consistency more difficult in articulate localization than in traditional translation processes?
Because classic translation memory (TM) and typical QA aids (repetitions, terminology warnings, consistency checks) are not available in this form. This results in variability that can only be captured through review and specifications.
Can a glossary be "incorrect" even though the term has been translated correctly?
Yes. The classic problem is context: a term may need to be translated exactly in the UI, but require a different translation in continuous text or idiomatic sentences. Machines do not always apply glossaries in a context-sensitive manner. Therefore, context cases must be checked carefully.
How do we prevent "Sie/Du mixtures" or stylistic inconsistencies?
By defining tonality as a fixed rule and checking it consistently in the review. The formal/informal setting is helpful, but not guaranteed to be stable. Especially in German, a mix immediately stands out negatively.
We have several products/brands. Can we use multiple glossaries in parallel?
In practice, this requires clean external glossary management (versioning, storage, approval). Using the wrong glossary for a course leads to systematic errors and costly rework. Governance is more important than the tool itself.
What is the quickest practical check to see if our terminology is "drifting"?
Search the translated course specifically for your critical terms (product names, UI terms, process names) and check: Is a term always used consistently? If not, either stricter glossary rules are needed or a review that treats consistency as a separate test criterion.
When is it worthwhile to use an additional external TM/terminology workflow outside of Articulate?
As soon as you have multiple courses, recurring modules, or regular updates, consistent course language really counts. Then “checking everything again each time” quickly becomes more expensive than a process that systematically enables reuse.
15 minutes of clarity instead of project surprises
If you want to use Articulate Localization (or already do) and want to know whether One-Click really saves time in your setup, let’s take a quick look at it together:
- Course structure (Rise, Storyline, Blends)
- Media mix (UI, subtitles, optional audio)
- Languages, update frequency
- Review and approval process
TRANSLATION
“Made in Germany” from Baden-Württemberg stands for quality worldwide, and we are committed to upholding this reputation. A high-quality translation should be easy to read, easy to understand, and indistinguishable from an original text in the target language. That is our standard.
