Why a sentence should remain a sentence
An interface may need to display a person's name, a number and an action in one message. Building that message by joining small English fragments can make a natural translation difficult. Other languages may require a different order or different surrounding wording.
Our practical recommendation is to treat the message as a complete translation unit while keeping its variables structured. The translator needs to understand what each variable represents and which combinations may appear.
An illustrative message
Consider a message about files waiting for review. The interface must work when the count is zero, one or several. A translation cannot safely be designed by adding a single “plural suffix” to an English word.
Our suggested design exercise is to list the message's variables, intended meanings and selectable situations before translation. Give translators realistic examples, then test the rendered outcomes in each target language. Include empty names, long names and counts that exercise different variants.
This exercise is original editorial guidance. It deliberately avoids presenting unvalidated code as a compliant implementation.
What this does not solve alone
A message format does not supply an approved translation, decide the tone or guarantee a good layout. It also does not guarantee support in the framework already used by a product. Runtime capabilities, extraction tools and translation-editor support must be checked together.
Version labels should be explicit. Do not assume that an older message syntax, a library with a similar name and the current Unicode specification are interchangeable.
Relationship to LISA and AI
MessageFormat is a Unicode development. Its connection to this collection is the practical interoperability problem: language-aware messages need to survive movement through a production workflow.
For AI-generated translations, our recommendation is to validate syntax and variable preservation independently. Then review each meaningful branch for language quality. A model can produce fluent wording while deleting a branch or changing a placeholder.
Source record and related reading
UTS #35 Part 9 and Unicode MessageFormat introduction. No claim is made about universal implementation support.