Terminology Control
Glossary / Protected Terminology
Control how important words, phrases, brand names, product names, and technical terms are handled during translation.
The Glossary helps keep terminology consistent across pages, posts, WooCommerce products, Elementor layouts, Gutenberg content, and Cloud Assist translations.
What the Glossary can do
You can add glossary rules to tell REEID Translate how specific terms should be handled. The two main rule types are Keep as-is and Translate as.
Rule type 01
1. Keep as-is
Use Keep as-is when a word or phrase must remain unchanged in every translation.
Good examples:
REEID Translate Pro
WooCommerce
Elementor
Gutenberg
Cloud Assist
BYOK
Classic EditorExample result:
Source:
Translate WordPress pages with Elementor and Gutenberg.
Arabic translation:
ترجم صفحات WordPress باستخدام Elementor وGutenberg.The protected terms stay exactly as written.
Rule type 02
2. Translate as
Use Translate as when a source term must always be translated into a specific target term.
Example:
Source term:
AI-powered translation plugin
Translate as:
translation plugin for real websitesThis tells the translator to use your preferred wording instead of choosing its own translation.
Language targeting
3. Target language control
Glossary rules can be applied to all languages or to one specific language, such as Arabic, Danish, or Chinese.
Use All languages for:
Brand names or terms that should behave the same everywhere.
Use a specific language for:
Preferred wording that changes from language to language.
Recommended use cases
The Glossary is best for names, technical terms, short product phrases, legal wording, and industry-specific terminology.
Protect names
- Brand names
- Product names
- Plugin names
- Feature names
Control terminology
- Technical terms
- Legal terms
- Compliance wording
- Industry-specific language
Guide wording
- Preferred translations
- Short marketing phrases
- Words that should not be translated
- Words that must use your chosen translation
Best practices
Use short, exact glossary terms whenever possible. Shorter rules are easier to match and usually produce more natural translations.
Better:
Elementor
Gutenberg
Cloud Assist
BYOK
WooCommerceAvoid when possible:
Very long sentence fragments
Phrases crossing formatting tags
Whole paragraphs as glossary termsIf you protect a long English phrase with Keep as-is, that full phrase will remain English inside the translated output. This is correct behavior, but it may not read naturally.
Keep as-is:
Translate WordPress pages, posts, WooCommerce products, Elementor layouts, Gutenberg content,Result may look like:
ترجم ... Translate WordPress pages, posts, WooCommerce products, Elementor layouts, Gutenberg content, ...Important limitation
Glossary rules are text-based. For best results, the source phrase should not cross formatting or HTML boundaries.
For example, this page content:
<strong>REEID Translate Pro</strong> is an AI-powered WordPress translation pluginis visually seen as:
REEID Translate Pro is an AI-powered WordPress translation pluginBut internally, the phrase is split by HTML formatting. A glossary rule for the full sentence may not match. Use a shorter rule that does not cross the formatting boundary.
Better rule:
Translate as:
is an AI-powered WordPress translation plugin
→ translation plugin for real websitesOr protect the name only:
Keep as-is:
REEID Translate ProWhen to clear cache
Cloud Assist may reuse previous translations for speed. If you recently changed glossary rules and old wording still appears, clear the Cloud Assist cache for that page or product and translate again.
Practical workflow
- Add glossary rows before translating.
- Use Keep as-is for names and technical terms.
- Use Translate as for preferred wording.
- Keep rules short and specific.
- Translate the page, post, Elementor page, or WooCommerce product.
- Review the translated output.
- If old wording appears, clear Cloud Assist cache and retranslate.
Current glossary behavior
REEID Translate Pro currently supports glossary enforcement for:
- Gutenberg pages and posts
- Elementor pages
- WooCommerce inline product translations
- Cloud Assist translations
- Cached Cloud Assist translations
The Glossary is intended as a terminology control tool. It is not a full CAT-tool termbase or translation memory system with style-preserving segment locks.