How to use the Localization Placeholder Checker.
Placeholder checks should compare identifiers and structural syntax, not just visible sentences. A missing variable can break the interface even when the translated prose reads naturally.
Make the workflow fit your task.
Identify the source message format and extract placeholder identifiers and structural requirements. Compare the target for missing, extra or changed placeholders, including repeated occurrences when relevant. Preserve syntax while allowing the language's natural word order.
- What you provide
- Source and translated strings.
- What you get
- Missing, altered or duplicated placeholders.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Source: Hello, {name}. You have {count} messages. Translation: Bonjour, {name}. Vous avez des messages.Completed example
Preserved placeholder: {name}.
Missing placeholder: {count}.
Return the string for correction and validate the restored variable with the application's message format.Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Must translated placeholders appear in the same order as the source?
Named placeholders often can move naturally, but positional formats may have stricter rules. Follow the application's message syntax.
Why does a translation still fail after the missing variable is restored?
Braces, escaping or nested message branches may also be malformed. Parse the full string in the target runtime.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑