A Keep as is rule stops one term from being translated. The original text appears unchanged on every translated page, in every language you have enabled.
Use it when a word is a name rather than a word: your brand, a product line, a person, a technical term your industry uses in English everywhere.
The names that most need a rule are the ones that are also ordinary words. A company called Ember, Compass, or Anchor will be translated, because nothing in the sentence tells the translator it is a company. A name like Zalando or Spotify usually survives on its own, because there is nothing to translate it into.
Add the rule
- Open the project's Glossary screen and click Add Rule.
- Leave What to do on Keep as is.
- Leave Match on Exact term.
- Type the term into Term, exactly as it appears on your pages.
- Leave Language on Any language, unless you only want the rule in one language.
- Click Create Rule.
The rule takes effect on the next translation request. Nothing needs clearing for a term that stands alone as its own string, such as a button label or a heading.
What it does to a page
The term is returned exactly as written. Casing, punctuation, and spacing inside the term are preserved, because the original text is used rather than a translation of it.
rule: Keep as is, "Ember"
without the rule Welcome to Ember -> Bienvenue chez Braise
with the rule Welcome to Ember -> Bienvenue chez Ember
The surrounding sentence is still translated. Only the term is held back.
Casing
Case sensitive is on by default, so Ember matches Ember and not ember or EMBER.
Turn it off when your term appears in several casings and all of them should be protected. A common example is an acronym that some pages write in lower case:
Case sensitive ON "API" protects API, but not api or Api
Case sensitive OFF "API" protects API, api, Api, and aPi
Turning it off widens the rule, so check it does not catch an ordinary word. A case-insensitive rule for IT would also protect the word “it”.
Terms that are more than one word
A term can contain spaces. Ember Coffee Roasters works as a single Exact term rule and matches that phrase wherever it appears.
The phrase must appear as written, in that order, with words separated by whitespace. A line break or a doubled space between the words is fine, because spacing differences are tolerated.
What it does not do
It does not protect a term that is part of a longer word. A rule for Ember protects Ember but not Embers or EmberOne, because the rule matches whole words rather than fragments. See Pattern matching for the boundary rules in detail.
It does not change translations you already have. A rule matching a whole string applies immediately, ahead of anything stored. A rule matching a term inside a longer sentence leaves the stored translation of that sentence alone. See How rules are applied.
It does not apply to text that is excluded from translation. If the term sits inside an element you have excluded, no glossary rule reaches it. See What Universally translates.
Protecting a family of terms
One rule per name is fine for a handful of brands. It stops being practical for product codes, order references, or hashtags, where thousands of values share one shape.
For those, use Pattern instead of Exact term: a single rule like STK{n:3} covers every three-digit code beginning with STK. See Pattern matching.