An AI translation reads naturally, but a notification now displays a blank where the filename should be. The words may be correct while the template is broken: a variable name was translated along with the sentence.
A placeholder marks a value that software inserts later. ICU MessageFormat, for example, uses arguments in braces. Other systems use different syntax, so identify the actual format before asking for a translation.
Tell the tool what must stay unchanged
Take this invented message: “{name}, your file {file} is ready.” A French version could be: “{name}, votre fichier {file} est prêt.” The two variable names and their braces stay the same, while the surrounding words change.
Provide the whole message, its purpose and the protected placeholders. For this simple example, require each placeholder exactly once. Do not impose that rule on every template: follow the application’s rules for repeated variables, plural forms and optional sections. Let the translator change word order where the language requires it.
Check structure and reading separately
Compare the expected placeholder names and counts with the translated string. A spelling checker cannot establish that the application will recognise them. Then preview the result through the actual template system using harmless sample values, such as Nora and draft.pdf.
Try a longer filename too. Read the completed sentence and inspect line wrapping on a narrow screen. If the message includes plural rules or formatting instructions, use the project’s template validation rather than a simple text comparison alone. Keep the original and reviewed translation together; correct variable spelling is necessary, but it does not prove that the sentence makes sense.