Resolve conflicting localization guidance
Find the requirements that disagree, settle their intended scope, and test a change that preserves both legitimate uses.
A glossary can require an unchanged product name while a general rule says to translate every English word. Both cannot govern that name at once. Adding a more emphatic instruction leaves the underlying decision unresolved.
Resolve the meaning and scope of the requirements before changing how strongly they are worded. This produces guidance the team can explain and test, instead of asking the model to choose between contradictory demands.
Reconstruct the guidance for the affected request #
Keep the source and target revisions, locale pair, localization engine, and content context together. Read the attached terms, rules, and voice, including their actual locale scopes. Where available, inspect request context to establish what reached that run.
Separate three kinds of statement. “The target uses informal address” is an observation. “This notice requires formal address” is a scoped requirement. “The model ignored the rule” is a causal conclusion that needs evidence about selection and competing guidance.
Describe the disagreement concretely #
An illustrative record could include:
| Requirement | Intended scope | Potential conflict |
|---|---|---|
| Keep “Workspace” as the product name. | Labels naming the product's project area. | A rule says to translate every English word. |
| Translate every English word. | General copy in the target locale. | The instruction lacks an exception for protected names. |
| Use conversational address. | Ordinary customer-facing explanations. | The same voice also reaches formal legal notices. |
Record the owner of each requirement and the other localization engines or content groups using its resource. First confirm the conflict is real. A physical workspace may not invoke the product entry at all; missing context may require clarification rather than a glossary change.
Settle the intended behavior with the responsible owner #
For the example, the product name can remain unchanged only when it names the software area, and the general translation instruction can exclude protected names. Formal notices can retain their required register while conversational wording remains appropriate elsewhere.
Edit the contradictory instruction or its scope directly. Keep the accepted reason, covered examples, exclusions, and owner with the guidance. Term boundaries and testable voice rules develop those distinctions.
Do not confuse a parser's precedence for protected keys with a semantic decision about tone or meaning. Structural merge rules cannot decide which register the legal notice should use. Likewise, a more-specific translation rule does not automatically cancel a matching broad rule.
Make and verify the authorized change #
Propose the exact term, rule, or voice edit and identify its shared consumers. Investigation alone does not authorize mutation. If using a suggestion, inspect its target and locale before applying it.
Keep the previous guidance for comparison and recovery, then confirm the saved record and attachments. Existing accepted output does not change with the configuration. Decide separately which content needs new translation or review.
Test the cases that distinguish the resolution #
Use authorized examples of the product name, the ordinary physical meaning, a legal notice, and casual help. Compare old and new guidance with the same source, locales, models, and other relevant conditions. Record actual outputs before describing the comparison as executed.
Judge each result against the accepted scope: the product name remains where required, the physical term keeps its own meaning, and the two audiences receive the agreed register. One successful example cannot establish all four.
If a failure persists, verify that the changed resource was attached and selected before making its wording stronger. The resolution is useful when the owner can explain its scope and representative outputs support it; the remaining task is to identify earlier content that still needs attention.