Glossary of terms
The words transglot uses, defined in one place.
Accounts and people
Account: who pays. An account holds the plan, billing, the usage allowance and one or more workspaces, and its plan applies to every workspace in it. See Workspaces and projects.
Billing member: a person who manages an account's plan, payment and invoices.
Owner: a person who manages an account and holds every permission in every workspace of it, including those no workspace role can hold, such as single sign-on and deleting a workspace.
Project access: access to one project instead of a whole workspace, optionally limited to some languages. See Grant access to one project.
Role: what a member can do in a workspace. The built-in roles are Admin, Developer, Reviewer and Translator; a workspace can add custom roles. See Roles and what each one can do.
Seat: a member of a workspace. How many seats an account has depends on its plan. See Your plan and seats.
Workspace: where your team works. A workspace holds members and their roles, projects, integrations and security settings, and belongs to one account.
Content
Key: the name your code asks for, such as checkout.title. A key holds one source string and one translation per target language, plus a description, an optional maximum length and tags. See Keys and strings.
Locale: a language, optionally with a region or script, named with a BCP-47 tag such as de, pt-BR or zh-Hans. See Languages and locales.
Placeholder: a part of a string your code fills in at runtime, such as {name}, {{count}}, %s or :name. transglot keeps placeholders intact in every translation.
Plural forms: the separate versions of a plural string, one per plural category the language uses, such as one and other in English. See Plural forms.
Project: one set of keys translated into a set of languages, typically one app, site or codebase. A project has its own languages, settings, glossary, voice and delivery keys.
Source language: the language your strings are written in. Each project has exactly one, and everything is translated from it.
Source string: the text of a key in the source language. It arrives by push, upload or integration and is read-only in the console.
Target language: a language you translate into and ship. A project can have any number.
Translation
Assignment: a language handed to a translator or vendor as tracked work, with a due date and a brief. Assignees see it under My assignments and submit it for review when done. See Assign a language to a translator.
Auto-translate: the project setting that translates new and changed source strings as they arrive. On by default. See AI translation settings.
Batch: one translation run. A batch has a progress figure while it runs and can be cancelled; the CLI prints its number as Batch: #<id>.
Draft: a translation Glossa wrote that nobody has read yet. See Translation states.
Glossa: the transglot translation engine. Glossa Flux is the fast default model that drafts; Glossa Deep is the quality model. See AI translation.
Needs checking: a translation someone flagged, or that a quality check found a problem with.
Quality mode: the project setting that uses Glossa Deep for every target language. Team and above.
Stale: a translation whose source string changed after it was written.
Translation memory: past translations transglot reuses. An exact match is reused at no cost; a similar match is offered as a suggestion and never written automatically. See Translation memory.
Quality
Brand voice: how your product sounds in every language: formality, warmth, rules and examples, set on the project's Voice page. See Brand voice.
Confidence routing: the Route AI translations by confidence setting. When on, confident AI translations that pass the automatic checks can skip review and the rest are flagged. Off by default, Team and above.
Glossary: a project's list of terms with the wording each language must use, or that must not be translated or must never appear. Glossary terms are matched against source text and enforced during translation and during quality checks. See The glossary.
MQM: Multidimensional Quality Metrics, the industry-standard set of categories transglot uses to group quality findings.
Quality check: the automatic checks (placeholders, plural forms, length and glossary) on every plan, and the AI review that scores translations on Team and above. See Quality checks.
Quality score: a 0-100 rating that transglot produces for a translation, alongside a list of specific findings, each with a severity. See What does the quality score mean?
Scorecard: the per-language summary of quality scores, grouped by MQM category, that you can print or export. See The per-language scorecard.
Self-heal: retranslating machine translations that fail review, either as a suggestion for a reviewer or written in directly. Team and above. See Self-heal a translation.
Delivery and developers
CDN: the service that serves your published translations to your app at runtime. See The CDN.
CDN key: a read-only key your app uses to fetch published translations from the CDN. Safe to use in client-side code. See Connect your app to the CDN.
CLI: the transglot command line tool. init sets a repository up; push and pull move strings and translations. See The command line tool.
Deploy token: a secret, project-scoped token for the CLI, the GitHub Action and the API. Shown once when created. See Deploy tokens.
In-context editor: an overlay that lets reviewers edit translations on your own running site. Starter and above. See The in-context editor.
Publish: turning a language's current translations into a new, immutable version on the CDN. See Publish a locale.
Publishable key: a key that is safe to embed in client-side code, used to load the in-context editor in your app. See Publishable keys.
Releases: the project screen where you publish languages and see what is live. See The Releases screen.
transglot.json: the configuration file the CLI reads, naming the files to push and pull. See Configuration.
Webhook: an HTTP request transglot sends to your endpoint when something happens in a project. See Webhooks.
Usage and billing
Spend cap: the most an account can be charged for usage beyond its allowance in a cycle. See Usage-based billing.
Usage-based overage: the account setting that lets translation continue past the plan's allowance, charged per word up to the spend cap. Off by default.
Welcome words: a one-time grant of words for new accounts on the Free plan. See Create your account.
Words: the unit of usage: source words, counted once for each target language they are translated into. See Words and usage.