Glossary and brands to keep
The Terms section of a profile holds three lists.
Glossary
The words that must be translated one agreed way, every time. A finding names the term, the list it came from and the translation that was expected.
Brands and terms to keep
Also called do-not-translate or DNT: the words that must stay exactly as they are. Brand names, product names, programme names, UI labels. A term here that was translated or left out is a finding. The matcher tolerates suffixes (so a Turkish possessive after a product name is not a hit) and keeps the term's case.
Brand written differently
A term that is in the target but in another form than the list is its own finding, Brand written differently, never a missing brand. The expected form always comes from the list and its allowed forms, never from the source: when the source writes "Mac OS" and the list says "macOS", a target "macOS" passes, and the source's "Mac OS" still counts as the listed term.
| The target writes | For the listed | Reported as |
|---|---|---|
| Iphone'u, IPhone'u, iphone'u | iPhone | Error: capital letters changed. The fix keeps the suffix: iPhone'u |
| İntune'a, LınkedIn | Intune, LinkedIn | Error: Turkish dotted or dotless I |
| Pay-Pal, i-Phone, FireTV | PayPal, iPhone, Fire TV | Error: name split or joined |
| IPHONE inside a normal sentence | iPhone | Warning: capitals inside a sentence |
| IPHONE'U SATIN AL | iPhone | Fine: the whole string is in capitals |
| EBay at the start of a sentence | eBay | Warning: capital at the start of a sentence |
| macOS | Mac OS | Warning: the target differs from the list, which may need macOS as an allowed form |
| wifi in Spanish, fit in Turkish | WiFi, Fit | Fine: a lower case word of the target language |
Another listed term of the same name (WiFi and Wi-Fi) and an allowed form are accepted. Letters inside a web address, an e-mail address, a placeholder or a key never count, and neither does a transliteration (айфон, アイフォーン), which stays with the missing check and its allowed forms.
Allow this form on the finding files the target's form as an allowed form of the term for this profile, so for this language only. Fine as is does not apply here: it never enforces anything.
How each term is written
Under the list, How each term is written sets a term's own options: Strict reports a lower case word of the language too, Off stops checking the form, Always lower case or Always capitals change the expected form, allow capitals and allow a capital at a sentence start accept those, and a language limit applies the term only in, or never in, the languages you name ("Stryker is kept in every language except Japanese"). A term with no options is checked as listed.
Fine as is
Words that may stay identical to the source without being flagged as untranslated: a product name, a code, a word the two languages share. A segment left identical to its source is a finding unless this list, or the brands list, explains it.
A client's term base as a term list
A client term base loads as one named term list under Brands and terms to keep. Pick the file, the language column that was read, the client's export date, a severity for the whole list and a scope: just this profile, the whole account, one division or one language. Every profile under that scope inherits it.
A row with one column is a do-not-translate entry; a row with a second column is a glossary entry. Each finding names the list, the file, the export date and the column it came from. Loading a list of the same name at the same scope replaces it, so a client's newer export goes in the same way.
From a report
On a segment kept identical to the source, a report offers Keep as brand and Fine as is. Each files a suggestion in the profile's Learn queue, where a PM or linguist approves it. The report answers "Sent to Learn for approval". Nothing changes a check until it is approved.
Which wins
A longer glossary entry outranks a shorter do-not-translate term inside it. If a term you are approving conflicts with the other list, or with something excluded higher up in the shared tiers, you are told before it applies.
Where the lists apply
A term taught at the account tier applies to every language pair under it. One client's terms never reach another client's checks: protected terms, glossary and AI guidance live inside the profile that owns them. Cascading only flows down the tiers you set up yourself.