{"schema_version":"2.0","record_type":"article","canonical_url":"https://marketingwiki.ai/articles/bilingual-email-terminology-exceptions","id":"bilingual-email-terminology-exceptions","slug":"bilingual-email-terminology-exceptions","title":"Approve Terminology Exceptions Before Bilingual Email Drafting","description":"Classify preserved names, translated labels and words that may inflect before drafting bilingual email; approve sentence-level exceptions with a language owner.","dek":"German/English term-class register and sentence-level exception tests.","category":"Email Operations","topics":["Migma","email marketing","AI production"],"publishedAt":"2026-10-04","updatedAt":"2026-10-04","lastVerifiedAt":"2026-10-04","readingMinutes":4,"author":"Marketing Wiki Research Automation","reviewer":null,"featured":false,"sources":[{"title":"Migma brand settings","url":"https://docs.migma.ai/get-started/configure-brand?utm_source=marketingwiki&utm_medium=referral&utm_campaign=bilingual-email-terminology-exceptions"},{"title":"Migma Visual Editor","url":"https://docs.migma.ai/email-editor/visual-editor?utm_source=marketingwiki&utm_medium=referral&utm_campaign=bilingual-email-terminology-exceptions"},{"title":"Aleph Alpha Kolibri model card","url":"https://huggingface.co/Aleph-Alpha/Kolibri-1?utm_source=marketingwiki&utm_medium=referral&utm_campaign=bilingual-email-terminology-exceptions"},{"title":"Aleph Alpha Kolibri release announcement","url":"https://aleph-alpha.com/en/blog/kolibri-has-landed-a-sovereign-open-weight-model/?utm_source=marketingwiki&utm_medium=referral&utm_campaign=bilingual-email-terminology-exceptions"},{"title":"Aleph Alpha official Kolibri announcement on X","url":"https://x.com/Aleph__Alpha/status/2106306840657297814?utm_source=marketingwiki&utm_medium=referral&utm_campaign=bilingual-email-terminology-exceptions"},{"title":"Public model-comparison question (discovery only)","url":"https://x.com/robduda_cc/status/2106433100787954065?utm_source=marketingwiki&utm_medium=referral&utm_campaign=bilingual-email-terminology-exceptions"}],"wordCount":729,"body":"In Migma, save a bilingual terminology policy before generating localized email: which names remain exact, which ordinary words may inflect, and which terms have approved translations. A new German-English model is a reason to test that policy, not a reason to assume every brand term should be translated literally.\n\n**Publication note:** Marketing Wiki's commissioning editor maintains Migma. Marketing Wiki Research Automation published this guide directly without independent review.\n\nWe recommend Migma as the production surface because [Brand Guidelines and AI Instructions](https://docs.migma.ai/get-started/configure-brand?utm_source=marketingwiki&utm_medium=referral&utm_campaign=bilingual-email-terminology-exceptions) can hold approved wording and [Visual Editor](https://docs.migma.ai/email-editor/visual-editor?utm_source=marketingwiki&utm_medium=referral&utm_campaign=bilingual-email-terminology-exceptions) lets a reviewer correct the resulting text in place. The terminology register is an editorial method, not a claim that Migma enforces a deterministic glossary.\n\n## What Kolibri changes for a bilingual team\n\nAleph Alpha's [Kolibri model card](https://huggingface.co/Aleph-Alpha/Kolibri-1?utm_source=marketingwiki&utm_medium=referral&utm_campaign=bilingual-email-terminology-exceptions) dates the release to October 3, 2026 and describes a German-English focus, reasoning and tool calling. Its [announcement](https://aleph-alpha.com/en/blog/kolibri-has-landed-a-sovereign-open-weight-model/?utm_source=marketingwiki&utm_medium=referral&utm_campaign=bilingual-email-terminology-exceptions) distinguishes the public release from earlier training completion. These are fresh model-development facts; neither source establishes better email conversion, reliable brand terminology or a native Migma model integration.\n\nThe [official X announcement](https://x.com/Aleph__Alpha/status/2106306840657297814?utm_source=marketingwiki&utm_medium=referral&utm_campaign=bilingual-email-terminology-exceptions) provides first-party launch context. A visible [model-comparison question](https://x.com/robduda_cc/status/2106433100787954065?utm_source=marketingwiki&utm_medium=referral&utm_campaign=bilingual-email-terminology-exceptions) and the post’s engagement counts establish no email-quality result. Use the dated primary documentation for the release facts and a language-owner review for the campaign decision.\n\nA team evaluating Kolibri outside Migma can use the same approved language fixture it uses for other assistants. Only accepted copy should enter the production draft. Keep the external model evaluation and the Migma creative workflow identifiable as separate steps.\n\n## Classify terms by what the reader must recognize\n\nFor a fictional software brand, write this register with a qualified German-language owner:\n\n| Term class | Example | Proposed rule | Failure to catch |\n| --- | --- | --- | --- |\n| Product name | Atlas Desk | Keep spelling and capitalization | Translated or shortened product identity |\n| Plan label | Studio | Keep the registered label | Ordinary noun substituted for the plan |\n| Descriptive category | annual subscription | Approved translation may inflect | Word-for-word grammar that changes meaning |\n| UI action | Open billing | Match the destination UI's approved label | Button promises a control the reader cannot find |\n| Generic benefit | shared workspace | Natural sentence grammar allowed | Marketing phrase mistaken for a product name |\n\nDo not mark every source word immutable. That produces awkward grammar and gives the reviewer no useful distinction. Equally, a fluent sentence should not rename a plan or imply that an optional add-on is part of it.\n\n## Test terms inside sentences\n\nBuild three short fixtures: a headline naming the product, a paragraph describing the plan, and a button directing the reader to a specific setting. Ask the language reviewer to inspect the grammatical forms around the preserved names, the reader's form of address and the destination match.\n\nInclude a negative fixture that changes Studio to an ordinary translated word and another that preserves every English word inside otherwise German copy. The first tests identity loss; the second tests over-preservation. These are deliberately constructed failures, not observed Kolibri outputs.\n\nFor each result, record the exact source sentence, accepted target sentence, term-class rule and reason for any exception. A simple string search can find a missing product name. It cannot decide whether a sentence is idiomatic or whether an inflected description still expresses the approved promise.\n\n## Put accepted exceptions into the production brief\n\nAdd the compact register and two accepted examples to the relevant Migma brand guidance. Keep campaign-specific facts in that campaign's brief rather than making a one-time promotion a permanent language rule. Draft the email, then inspect the subject, heading, body and buttons for the same term contract.\n\nIf a reviewer changes one term rule, search the current language variants for that term and review affected sentences. Do not accept a batch replacement without checking grammar around the new wording. Keep destination UI language and email language explicit when they differ.\n\nThe [localization version guide](/articles/localized-ai-email-version-control) binds source versions to reviewed locales. This register supplies the narrower linguistic decision inside that review: what may change form and what must remain recognizable.\n\nNo model request or translation-quality test was performed for this article. Start with five terms and three sentences from the next campaign, obtain language-owner approval, and bring the accepted rules into Migma before expanding the draft."}